Confirmed users
1,927
edits
Phabricator/TestPlan: Difference between revisions
Jump to navigation
Jump to search
→Test Plan: update a couple test cases
(→Test Plan: update notes) |
(→Test Plan: update a couple test cases) |
||
| Line 46: | Line 46: | ||
====Results==== | ====Results==== | ||
* | * After logging into Phabricator, on the "Create a New Account" page, | ||
- Username should be prefilled with the irc nick | - Username should be prefilled with the irc nick, | ||
- Real Name is correct and does not contain [] | - Real Name is correct and does not contain [] or any other extraneous characters. | ||
* Clicking register approval completes account creation without error. | * Clicking register approval completes account creation without error. | ||
* The account works as expected. | * The account works as expected. | ||
[EDGE CASE] Currently when you revoke the "MozPhab" API key on BMO, there | [EDGE CASE] Currently when you revoke the "MozPhab" API key on BMO, there is no way to create a new one for Phabricator to use. | ||
is no way to create a new one for Phabricator to use. | |||
=== Creating a revision is successful === | === Creating a revision is successful === | ||
====Test Plan==== | ====Test Plan==== | ||
* Make sure you have arc properly setup on your machine and have run | * Make sure you have arc properly setup on your machine and have run <code>arc install-certificate</code> using the Phabricator user you wish to test with as documented above. | ||
* Go to BMO and create a new bug as the Bugzilla user that the Phabricator account is connected to. (Or use an existing public bug). | |||
* Go to BMO and create a new bug as the Bugzilla user that the Phabricator | ** To create bugs directly and bypass triaging, go to: | ||
http://bmo.test/enter_bug.cgi?product=Firefox&format=__default__ | http://bmo.test/enter_bug.cgi?product=Firefox&format=__default__ | ||
* Using the repo listed in the | * Using the repo listed in the "Getting Started" section above that matches the environment you are testing, make some change to a file. | ||
* Run | * Run <code>hg commit -A -m 'commit1: New changes</code> | ||
* Run | * Run <code>arc diff .^</code> | ||
* Input something for the title, summary, test plan, and the correct bug id. | * Input something for the title, summary, test plan, and the correct bug id. | ||
* Save and exit the file. | * Save and exit the file. | ||
====Results==== | ====Results==== | ||
* arc diff only submitted the 1 newly created commit. | * <code>arc diff</code> only submitted the 1 newly created commit. | ||
* Visit Phabricator and there should be a new revision with the title. | * Visit Phabricator and there should be a new revision with the title. | ||
* The revision should contain the correct diff of the changes that were made | * The revision should contain the correct diff of the changes that were made. | ||
* The "Bugzilla Bug ID" is correct. | * The "Bugzilla Bug ID" 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). | |||
** Note: If the bug id is short (like 3, 92, etc, which is common on local test environments) the link will not work but that is fine because it only works on very long bug ids which match what new bugs on production bmo will be using. | |||
* Visiting the bug on bugzilla shows an <code>x-phabricator-request</code> attachment. | |||
* Visiting the bug on bugzilla shows an x-phabricator-request attachment. | |||
=== Updating a revision is successful === | === Updating a revision is successful === | ||