WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Commit a3c9f85

Browse files
authored
Merge pull request #9 from auto-qa-hub/YuliiaKuzmenko-patch-1
Update TEST_PLAN.md
2 parents 920846a + 8b56923 commit a3c9f85

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

TEST_PLAN.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Link for SauceDemo web application - https://www.saucedemo.com
55

66
## 1.1 Objective
77

8-
The purpose of this test plan is to define the scope, approach, resources, and schedule for the automation of the SauceDemo web application using Playwright with TypeScript. The objective is to ensure functional correctness, performance efficiency, and reliability of critical workflows through automated tests.
8+
This test plan defines the scope, approach, resources, and schedule for automating the SauceDemo web application using Playwright with TypeScript. The objective is to ensure the functional correctness, performance efficiency, and reliability of critical workflows through automated tests.
99

1010
## 1.2 Scope
1111

@@ -25,7 +25,7 @@ The purpose of this test plan is to define the scope, approach, resources, and s
2525

2626
- Implement Page Object Model (POM) for maintainability
2727

28-
- Execute tests in headless and headed mode for debugging
28+
- Execute tests in the headless and headed mode for debugging
2929

3030
- Use CI/CD integration for test execution on each deployment
3131

@@ -89,15 +89,15 @@ The purpose of this test plan is to define the scope, approach, resources, and s
8989

9090
## 5.1 Test Execution Strategy
9191

92-
- Execute tests locally before pushing to local branch
93-
- Create pull request
92+
- Execute tests locally before pushing them to the local branch
93+
- Create a pull request
9494
- Run automated tests on every code commit via CI/CD
9595
- Push to the main branch changes (if all tests are passed)
9696

9797
## 5.2 Test Execution Schedule
9898

9999
- Every pull request creation
100-
- After merging chnage sto the main
100+
- After merging change to the main
101101

102102
# 6. Risks & Mitigation
103103

@@ -128,6 +128,6 @@ The purpose of this test plan is to define the scope, approach, resources, and s
128128
- Playwright HTML Reports
129129
- Allure Reports for detailed analysis
130130

131-
# 9. Conclusion
131+
# 8. Conclusion
132132

133-
This test plan serves as a roadmap for effectively automating the SauceDemo website using Playwright and TypeScript. By following structured testing strategies, defect management, and risk mitigation, we aim to ensure the quality and reliability of the application while streamlining the testing process.
133+
This test plan is a roadmap for effectively automating the SauceDemo website using Playwright and TypeScript. By following structured testing strategies, defect management, and risk mitigation, we aim to ensure the quality and reliability of the application while streamlining the testing process.

0 commit comments

Comments
 (0)