637
edits
Phabricator/TestPlan: Difference between revisions
Jump to navigation
Jump to search
no edit summary
DaveLawrence (talk | contribs) No edit summary |
DaveLawrence (talk | contribs) No edit summary |
||
| Line 89: | Line 89: | ||
#* To create bugs directly and bypass triaging, go to https://bugzilla.allizom.org/enter_bug.cgi?product=Firefox&format=__default__ (staging) or https://bugzilla-dev.allizom.org/enter_bug.cgi?product=Firefox&format=__default__ (dev) | #* To create bugs directly and bypass triaging, go to https://bugzilla.allizom.org/enter_bug.cgi?product=Firefox&format=__default__ (staging) or https://bugzilla-dev.allizom.org/enter_bug.cgi?product=Firefox&format=__default__ (dev) | ||
# Using the repo listed in the "Getting Started" section above that matches the environment you are testing, make some change to a file. | # Using the repo listed in the "Getting Started" section above that matches the environment you are testing, make some change to a file. | ||
# Run <code>hg commit -A -m 'Bug <bugid>: New changes</code> | # Run <code>hg commit -A -m 'Bug <bugid>: New changes'</code> | ||
# Run <code>moz-phab</code> | # Run <code>moz-phab</code> | ||
| Line 124: | Line 124: | ||
====Test Plan==== | ====Test Plan==== | ||
# Go to bugzilla and create a security bug: | # Go to bugzilla and create a security bug: | ||
# | # Click "Edit Bug", open the "Security" panel, and check one of the security-sensitive boxes, e.g. "Security-Sensitive Core Bug". | ||
# Run <code>hg commit -A -m 'Bug <bugid>: Private changes</code> | # Run <code>hg commit -A -m 'Bug <bugid>: Private changes'</code> | ||
# Run <code>moz-phab</code>. | # Run <code>moz-phab</code>. | ||
| Line 132: | Line 132: | ||
# The revision has a "Custom Policy" attached to it. | # The revision has a "Custom Policy" attached to it. | ||
# Click "Edit Revision" and then click on the "Visible To" drop down, and select the "Custom Policy" choice. | # Click "Edit Revision" and then click on the "Visible To" drop down, and select the "Custom Policy" choice. | ||
# | # It should read "Allow members of projects", followed by the names of projects corresponding to all Bugzilla groups the private bug is categorized under. For example, a bug private to core-security, should have the project name "bmo-core-security". | ||
# The revision has a "secure-revision" project tag added. | # The revision has a "secure-revision" project tag added. | ||
# The revision has a warning titled "This is a secure revision.". | # The revision has a warning titled "This is a secure revision.". | ||
| Line 148: | Line 148: | ||
====Test Plan==== | ====Test Plan==== | ||
# Go to bugzilla and create a public bug: | # Go to bugzilla and create a public bug: | ||
# Run <code>hg commit -A -m 'Bug <bugid>: Public changes</code> | # Run <code>hg commit -A -m 'Bug <bugid>: Public changes'</code> | ||
# Run <code>moz-phab</code>. | # Run <code>moz-phab</code>. | ||
# Check if revision is available for public. | # Check if revision is available for public. | ||
# Go to bugzilla and create a security bug: | # Go to bugzilla and create a security bug: | ||
# | # Click "Edit Bug", open the "Security" panel, and check one of the security-sensitive boxes, e.g. "Security-Sensitive Core Bug". | ||
# Edit the revision created above, and set the Bugzilla Bug ID field to the ID of the newly created private bug. | # Edit the revision created above, and set the Bugzilla Bug ID field to the ID of the newly created private bug. | ||
# Add the second, unprivileged Bugzilla user to the bug's CC list. | # Add the second, unprivileged Bugzilla user to the bug's CC list. | ||
| Line 159: | Line 159: | ||
# The revision has a "Custom Policy" attached to it. | # The revision has a "Custom Policy" attached to it. | ||
# Click "Edit Revision" and then click on the "Visible To" drop down, and select the "Custom Policy" choice. | # Click "Edit Revision" and then click on the "Visible To" drop down, and select the "Custom Policy" choice. | ||
# | # It should read "Allow members of projects", followed by the names of projects corresponding to all Bugzilla groups the private bug is categorized under. For example, a bug private to core-security, should have the project name "bmo-core-security". | ||
# The revision has a "secure-revision" project tag added. | # The revision has a "secure-revision" project tag added. | ||
# The revision has the creator and the second Bugzilla user as subscribers. | # The revision has the creator and the second Bugzilla user as subscribers. | ||
| Line 174: | Line 174: | ||
====Test Plan==== | ====Test Plan==== | ||
# Enter the bug id as specified for each expected result below. | # Enter the bug id as specified for each expected result below. | ||
# Run <code>hg commit -A -m 'Bug <bugid>: Public changes</code> | # Run <code>hg commit -A -m 'Bug <bugid>: Public changes'</code> | ||
# Run <code>moz-phab</code>. | # Run <code>moz-phab</code>. | ||
| Line 186: | Line 186: | ||
====Test Plan==== | ====Test Plan==== | ||
# Run <code>hg commit -A -m 'Bug <bugid>: Public changes</code> | # Run <code>hg commit -A -m 'Bug <bugid>: Public changes'</code> | ||
# Run <code>moz-phab</code>. | # Run <code>moz-phab</code>. | ||
# Create a different comment using same bug id but different title. | # Create a different comment using same bug id but different title. | ||
| Line 198: | Line 198: | ||
====Test Plan==== | ====Test Plan==== | ||
# Ensure that you have 2 Phabricator accounts that log in via Bugzilla ready to go. | # Ensure that you have 2 Phabricator accounts that log in via Bugzilla ready to go. | ||
# Create a commit with other account as reviewer using <code>hg commit -m | # Create a commit with other account as reviewer using <code>hg commit -m 'Bug <bugid>: New changes r?<reviewer>'</code. | ||
# Run <code>moz-phab</code>. | # Run <code>moz-phab</code>. | ||
# Log into Phabricator as the reviewer account. | # Log into Phabricator as the reviewer account. | ||