Phabricator/TestPlan: Difference between revisions

Jump to navigation Jump to search
Remove test cases involving r+s in BMO
(Rewording a few things to make the instructions more clear.)
(Remove test cases involving r+s in BMO)
Line 201: Line 201:
====Results====
====Results====
# The Phabricator attachment on Bugzilla is present.
# The Phabricator attachment on Bugzilla is present.
# The Phabricator attachment on the bug should have no r+ flags.
# Reviewer received an email from author with a text "{author} added a reviewer: {reviewer}"
# Reviewer received an email from author with a text "{author} added a reviewer: {reviewer}"
# Author received an email from reviewer with a text "{reviewer} accepted this revision."
# Author received an email from reviewer with a text "{reviewer} accepted this revision."
# Author received an email from reviewer with a text "{reviewer} requested changes to this revision."
# Author received an email from reviewer with a text "{reviewer} requested changes to this revision."


=== T9 - Resigning as a reviewer removes r+ ===
=== T9 - Abandoning a revision obsoletes the attachment ===
 
====Test Plan====
# Ensure that you have 2 Phabricator accounts that log in via Bugzilla ready to go.
# Create a commit, run <code>arc diff .^</code>.
# Input the title, summary, test plan, and bug id of a public bug.
# For the "Reviewers" field enter the Phabricator username of the other account.
# Log into Phabricator as the reviewer account.
# Add the "Accept Revision" action at the bottom. Submit.
# Add the "Resign as Reviewer" action at the bottom. Submit.
 
====Results====
# The Phabricator attachment on Bugzilla is present.
# The Phabricator attachment on the bug should have no r+ flags.
# Author received an email from the reviewer with a text "{reviewer} resigned from this revision."
 
=== T10 - Plan Changes does not clear previous r+s ===
 
====Test Plan====
# Ensure that you have 2 Phabricator accounts that log in via Bugzilla ready to go.
# Create a commit, run <code>arc diff .^</code>.
# Input the title, summary, test plan, and bug id of a public bug.
# For the "Reviewers" field enter the Phabricator user name of the other account.
# Log into Phabricator as the reviewer account.
# Add the "Accept Revision" action at the bottom.
# Log into Phabricator as the revision author account.
# Add the "Plan Changes" action at the bottom. Submit.
 
====Results====
# The Phabricator attachment on Bugzilla is present.
# The Phabricator attachment in Bugzilla still has any previous r+ flags.
# Reviewer received an email from the author with a text "{author} planned changes to this revision."
 
=== T11 - Abandoning a revision obsoletes the attachment ===


====Test Plan====
====Test Plan====
Line 251: Line 217:
# The bug has one obsolete attachment listed, linking to the created revision.
# The bug has one obsolete attachment listed, linking to the created revision.


=== T12 - Reclaiming a revision unobsoletes the attachment ===
=== T10 - Reclaiming a revision unobsoletes the attachment ===


====Test Plan====
====Test Plan====
Line 259: Line 225:
# The bug's Phabricator attachment is unobsoleted.
# The bug's Phabricator attachment is unobsoleted.


=== T13 - Creating a Diff from local git repository to remote Mercurial repository is not allowed ===
=== T11 - Creating a Diff from local git repository to remote Mercurial repository is not allowed ===


====Test Plan====
====Test Plan====
Line 271: Line 237:
     ERR-CONDUIT-CORE: Local VCS (git) is different from the remote repository VCS (hg).
     ERR-CONDUIT-CORE: Local VCS (git) is different from the remote repository VCS (hg).


=== T14 - Patching Diff created from git repository ===
=== T12 - Patching Diff created from git repository ===


====Test Plan====
====Test Plan====
Line 282: Line 248:
# Code is sucessfully patched using the Diff.
# Code is sucessfully patched using the Diff.


=== T15 - Verify the private revisions deliver emails that does not contain any sensitive content ===
=== T13 - Verify the private revisions deliver emails that does not contain any sensitive content ===


Your Bugzilla user must belong to a security group, e.g. core-security.
Your Bugzilla user must belong to a security group, e.g. core-security.
Confirmed users
1,927

edits

Navigation menu