Confirmed users
198
edits
B2G/QA/Automation/UI/Integration suite criteria: Difference between revisions
Jump to navigation
Jump to search
B2G/QA/Automation/UI/Integration suite criteria (view source)
Revision as of 16:26, 4 March 2015
, 4 March 2015Added Geo's comments.
No edit summary |
(Added Geo's comments.) |
||
| Line 1: | Line 1: | ||
In order to make a clearer distinction between the [https://wiki.mozilla.org/B2G/QA/Automation/UI/Strategy/Integration_vs_Acceptance#The_Solution Integration suite and the Acceptance one], here is a list which helps to define where a test belongs depending on its nature. | In order to make a clearer distinction between the [https://wiki.mozilla.org/B2G/QA/Automation/UI/Strategy/Integration_vs_Acceptance#The_Solution Integration suite and the Acceptance one], here is a list which helps to define where a test belongs depending on its nature. | ||
| Line 6: | Line 4: | ||
Should be in Integration suite rather than in the Acceptance one: | Should be in Integration suite rather than in the Acceptance one: | ||
* Tests | * Tests that don't represent a whole user story, such as boundary/edge cases, negative cases, and highly specific or unusual bug verifications. | ||
* | * Tests that perform small, isolated checks of the UI (such as a test that only verifies the sort order of a table) | ||
* Tests | * Tests that use mocks to simulate a portion of the system | ||
* Tests that verify something which is invisible for an end-user (example: "Is the gaia setting | * Tests that validate binding between the UI state and back end state | ||
* Tests that verify something which is invisible for an end-user (example: "Is the gaia setting 'ril.data.enabled' correctly set?"). An exception could be made for an Acceptance test if this verification is done during the setUp/tearDown phases. | |||
Should not be in Integration suite: | Should not be in Integration suite: | ||
| Line 16: | Line 14: | ||
* Tests that check a device specific issue. | * Tests that check a device specific issue. | ||
* Tests that check the behavior with an external service without being mocked (like a test which interacts with the actual Gmail). | * Tests that check the behavior with an external service without being mocked (like a test which interacts with the actual Gmail). | ||
* Tests that takes too long to be executed | * Tests that takes too long to be executed. | ||
= Firefox OS current specific considerations = | = Firefox OS current specific considerations = | ||