README
draft: true
E2E Test Cases
This directory stores the definitions of end-to-end test cases for Archipelo products. The tests are split in directories by product and then grouped together in 1 file based on the relevant area.
File Structure
Products
All E2E test cases definitions need to be documented in this directory. Each Archipelo product has its own directory (e.g. one_box, web_app or vs_code).
Products' Areas
All test cases are grouped within a specific area of the products. Each file under a product directory represents a specific area of the related product, like "Package Search page" or "Package Comparison page" in WebApp. Each area has a consecutive alphabet letter assigned to it (A, B, C etc.). All test cases related to specific area are defined within one Markdown file named using template <letter>_<area>.md, e.g. A_authorization.md.
Test Cases
Each test case has a correlated number, starting with "1" for the first test case in a specific area. Letter of the area and the number of the test cases together form a unique test case identifier within a specific product, e.g. A1, or B2. The identifier is used in the test script's title to clearly link the test with its definition.
Each test case needs to include:
- title
- unique identifier at the beginning of the title
- automation state
- preconditions - a set of conditions to be met before the test starts
- steps - a pairs of action and an expected result when the action is done
Example:
Test case B2 defined in docs/testing/e2e_test_cases/web_app/B_onboarding.md is implemented inside jsapps/tests/webapp/e2e/onboarding.spec.ts. The title of the test script starts with B2 linking it to the definition in Markdown file.
Note Use
e2e_template.mdfile as a template when defining new test cases.