Phabricator/TestPlan: Difference between revisions

Jump to navigation Jump to search
Identify which tests are likely Selenium candidates (spoiler: T1, T9, T10, and T13)
No edit summary
(Identify which tests are likely Selenium candidates (spoiler: T1, T9, T10, and T13))
Line 65: Line 65:


Please update this doc with new tests as features are added/changed and as holes in the plan are discovered.
Please update this doc with new tests as features are added/changed and as holes in the plan are discovered.
----


=== T1 - Signing up is successful ===
=== T1 - Signing up is successful ===
'''NOTE:''' Selenium test?


====Test Plan====
====Test Plan====
Line 81: Line 85:
# 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.
----


=== T2 - Creating a revision is successful ===
=== T2 - Creating a revision is successful ===
Line 102: Line 108:
# Visiting the bug on Bugzilla shows an entry for the new revision in the Phabricator Revisions section.
# Visiting the bug on Bugzilla shows an entry for the new revision in the Phabricator Revisions section.
# 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)"."
----


=== T3 - Updating a revision with an amended commit is successful ===
=== T3 - Updating a revision with an amended commit is successful ===
Line 117: Line 125:
## The Commits tab should have a single entry.
## The Commits tab should have a single entry.
# The bug id and other information remains unchanged.
# The bug id and other information remains unchanged.
----


=== T4 - Creating a secure revision is successful ===
=== T4 - Creating a secure revision is successful ===
Line 141: Line 151:
# The revision is NOT visible to the public without logging in.
# The revision is NOT visible to the public without logging in.
# The revision is NOT visible to logged in members without the correct permission.
# The revision is NOT visible to logged in members without the correct permission.
----


=== T5 - Adding a secure bug to an existing revision locks it down ===
=== T5 - Adding a secure bug to an existing revision locks it down ===
Line 169: Line 181:
# Visiting the bug on Bugzilla shows an entry for the new revision in the Phabricator Revisions section.
# Visiting the bug on Bugzilla shows an entry for the new revision in the Phabricator Revisions section.
# The reviewer received an email from the author with a text "The content for this message can only be transmitted over a secure channel." and a link to Phabricator.
# The reviewer received an email from the author with a text "The content for this message can only be transmitted over a secure channel." and a link to Phabricator.
----


=== T6 - Creating a revision checks the bug id ===
=== T6 - Creating a revision checks the bug id ===
Line 182: Line 196:
# Entering the id of a bug of a secure revision that the user does not have access to fails.
# Entering the id of a bug of a secure revision that the user does not have access to fails.
# Entering a valid bug id is successful.
# Entering a valid bug id is successful.
----


=== T7 - Creating multiple revisions with the same bug id is successful ===
=== T7 - Creating multiple revisions with the same bug id is successful ===
Line 193: Line 209:
# Both revisions are created successfully.
# Both revisions are created successfully.
# Visiting the bug on Bugzilla shows 2 corresponding entries for the revisions in the Phabricator Revisions section.
# Visiting the bug on Bugzilla shows 2 corresponding entries for the revisions in the Phabricator Revisions section.
----


=== T8 - Requesting and leaving a review on a revision is successful ===
=== T8 - Requesting and leaving a review on a revision is successful ===
Line 209: Line 227:
# 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 - Abandoning a revision obsoletes the attachment ===
=== T9 - Abandoning a revision obsoletes the attachment ===
'''NOTE:''' Selenium test?


====Test Plan====
====Test Plan====
Line 218: Line 240:
# The bug shows the revision as 'Abandoned' in the Phabricator Revisions list of the bug.
# The bug shows the revision as 'Abandoned' in the Phabricator Revisions list of the bug.
# The bug history shows the attachment is being set to obsolete.
# The bug history shows the attachment is being set to obsolete.
----


=== T10 - Reclaiming a revision unobsoletes the attachment ===
=== T10 - Reclaiming a revision unobsoletes the attachment ===
'''NOTE:''' Selenium test?


====Test Plan====
====Test Plan====
Line 226: Line 252:
====Results====
====Results====
# The bug's Phabricator attachment is unobsoleted and the revision is not abandoned any longer in the Phabricator revisions list.
# The bug's Phabricator attachment is unobsoleted and the revision is not abandoned any longer in the Phabricator revisions list.
----


=== T11 - 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 ===
Line 238: Line 266:


     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).
----


=== T12 - Patching Diff created from git repository ===
=== T12 - Patching Diff created from git repository ===
Line 249: Line 279:
====Results====
====Results====
# Code is sucessfully patched using the Diff.
# Code is sucessfully patched using the Diff.
----


=== T13 - 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 ===
'''NOTE:''' Selenium test?


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
33

edits

Navigation menu