Skip to content

E2E Automation Strategy Flow

Jump to bottom
Sean Moore edited this page Mar 24, 2021 · 1 revision

E2E Automation Strategy ↑

1. Test Creation ↑ 

A. Planning: assign the scope of work for the sprint
B. Write the E2E scripts per functionality test cases + visual regression
C. Create the PR in fundamental-ngx, get QA and Dev approvals.
D. Merge to main.

2. Main Flow ↑ 

A. When a developer creates a PR, E2E scripts run in travis CI.(scripts run on Mac and Windows machines, IE, Firefox, Edge, Safari, Chrome browsers). Dev checks the test logs (travis CI log / allure reporter) if failed.
     O1. If the test scripts fail due because the developer is introducing code which breaks existing components, developer fixes the bug introduced by their code in the current PR (without merging bugs to main). Then repeat step 2.A.
     O2. If the tests scripts fail because the developer is introduces changes that cause visual regression to fail, dev needs to analyze screenshots to check if everything is as expected and make the appropriate updates. Then repeat step 2.A.
     O3. If tests fail because a test script needs updating (no issue with the actual components), dev pings QA to fix test in their PR and QA updates the test cases and pushes them to the dev’s PR (~1D turnaround). Then repeat step 2.A.
B. If the PR passes, then PR is merged to main.
C. Before release to production, QA run E2E tests on main. QA checks the logs (allure report) if failed.
     O1. If the test scripts fail because the scripts need updating (no issues with the components), QA creates tasks to fix test script.
        a. QA updates tests.
        b. Goes to step 1.C.
     O2. If the test scripts fail because of issues with components (bugs), QA raises issues on github
        a. Bug triage & Dev fixes bug & creates PR. 
        b. Goes to step 2.A.
D. Release to production
Clone this wiki locally