766
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 86: | Line 86: | ||
## The Bug number is correct. | ## The Bug number is correct. | ||
## The link is correct based on the environment (bugzilla.allizom.org for staging, bugzilla-dev.allizom.org for dev). | ## The link is correct based on the environment (bugzilla.allizom.org for staging, bugzilla-dev.allizom.org for dev). | ||
# | ## If the bug in Bugzilla is a public bug, the revision should also be public. | ||
# Visiting the bug on Bugzilla shows an <code>x-phabricator-request</code> attachment. | # Visiting the bug on Bugzilla shows an <code>x-phabricator-request</code> attachment. | ||
# Author received an email from <code>mozphab-dev@mozilla.com</code>. It has a title formatted as "[Differential] [Changed Policy] D{revision number}: {first line}." and a body with a text "phab-bot changed the visibility from "Administrators" to "Public (No Login Required)"." | # Author received an email from <code>mozphab-dev@mozilla.com</code>. It has a title formatted as "[Differential] [Changed Policy] D{revision number}: {first line}." and a body with a text "phab-bot changed the visibility from "Administrators" to "Public (No Login Required)"." | ||
| Line 121: | Line 121: | ||
# The diff and information of the revision are as expected. | # The diff and information of the revision are as expected. | ||
# 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 "Custom Policy" choice in the "View Policy" drop down. It should show the projects that align with the Bugzilla groups that the private bug is marked. Such as a bug private to core-security, should have the project name of bmo-core-security. | |||
# 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.". | ||
# The revision added the creator as a subscriber. | # The revision added the creator as a subscriber. | ||
| Line 146: | Line 148: | ||
====Results==== | ====Results==== | ||
# 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 "Custom Policy" choice in the "View Policy" drop down. It should show the projects that align with the Bugzilla groups that the private bug is marked. Such as a bug private to core-security, should have the project name of bmo-core-security assigned to the policy. | |||
# 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. | ||
# The revision is visible to the user who made it. | # The revision is visible to the user who made it. | ||