You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Start your local development server (if testing against a local app).
98
+
99
+
2. Run the tests:
100
+
101
+
```bash
102
+
npx playwright test --config playwright-test.config.ts
103
+
```
104
+
105
+
This will execute your tests using Playwright with Tonkeeper integration
106
+
2
107
3
108
## QA
4
109
5
-
Write scenarios in folder [features](features) see [Gherkin Reference](https://cucumber.io/docs/gherkin/reference/)
110
+
Write scenarios in folder [features](features) see [Gherkin Reference](https://cucumber.io/docs/gherkin/reference/) and [Cucumber Anti-Patterns](https://www.thinkcode.se/blog/2016/06/22/cucumber-antipatterns)
6
111
7
112
## SE
8
113
@@ -15,7 +120,27 @@ npm install
15
120
npm run lint
16
121
npm run format
17
122
npx playwright install
123
+
pnpm exec playwright install
18
124
npm test
19
125
# or
20
126
npm run watch
21
127
```
128
+
129
+
# Techstack
130
+
131
+
-[Gherkin](https://cucumber.io/docs/gherkin/) — language used for describe acceptance scenarios
-[Node.js](https://nodejs.org/) — main platform for automation implementation
134
+
-[Playwright](https://playwright.dev/) + [BDD](https://vitalets.github.io/playwright-bdd/) — framework browser automation used for implementation steps uses in scenarios
0 commit comments