diff --git a/.github/workflows/test.yaml b/.github/workflows/test.yaml
index b886c014..3a269727 100644
--- a/.github/workflows/test.yaml
+++ b/.github/workflows/test.yaml
@@ -35,10 +35,12 @@ jobs:
playwrightVersion: ${{ fromJson(needs.get-playwright-versions.outputs.versions) }}
cucumberVersion: ['9']
include:
- # there were breaking changes in cucumber 10.1 -> test on both 10.0 and 10
+ # there were breaking changes in cucumber 10.x -> test on 10.0 and 10.1
- playwrightVersion: '1.37'
cucumberVersion: '10.0'
- playwrightVersion: '1.38'
+ cucumberVersion: '10.1'
+ - playwrightVersion: '1.39'
cucumberVersion: '10'
steps:
- uses: actions/checkout@v3
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8ea615b4..2197e52b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,7 +1,10 @@
# Changelog
+## 5.7.1
+* support Cucumber 10.2
+
## 5.7.0
-* suppport Cucumber 10.1, [#80](https://github.com/vitalets/playwright-bdd/issues/80)
+* support Cucumber 10.1, [#80](https://github.com/vitalets/playwright-bdd/issues/80)
## 5.6.0
* support component tests, [#57](https://github.com/vitalets/playwright-bdd/issues/57)
diff --git a/docs/ide-integration.md b/docs/ide-integration.md
index 4233b71e..5c98503b 100644
--- a/docs/ide-integration.md
+++ b/docs/ide-integration.md
@@ -9,8 +9,8 @@ Playwright-bdd provides support for all Playwright IDE integrations, because gen
* [Cucumber autocomplete extension](https://marketplace.visualstudio.com/items?itemName=alexkrechik.cucumberautocomplete) works as usual:
-## Intellij Idea / Aqua
+## IntelliJ IDE / Aqua
Built-in Playwright support works as usual:
-> You may need to set path to Playwright executable in [Run Configuration Template](https://www.jetbrains.com/help/idea/run-debug-configuration.html#change-template) to avoid popup window before every test run
\ No newline at end of file
+> You may need to set path to Playwright executable in [Run Configuration Template](https://www.jetbrains.com/help/idea/run-debug-configuration.html#change-template) to avoid popup window before every test run
diff --git a/docs/index.md b/docs/index.md
index 238011a9..7e83d7d7 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -56,7 +56,7 @@ test.describe('Playwright site', () => {
```
### Phase 2: Run tests
-CLI commmand `npx playwright test` runs generated test files with Playwright runner.
+CLI command `npx playwright test` runs generated test files with Playwright runner.
Playwright-bdd makes Playwright API available in step definitions (`page`, `browser`, etc):
```js
@@ -73,4 +73,4 @@ Then('I see in title {string}', async ({ page }, text) => {
});
```
-Proceed to [installation guide](installation.md) to try it in action!
\ No newline at end of file
+Proceed to [installation guide](installation.md) to try it in action!
diff --git a/docs/installation.md b/docs/installation.md
index bd63cbe9..69ee9774 100644
--- a/docs/installation.md
+++ b/docs/installation.md
@@ -8,7 +8,7 @@ npm i -D playwright-bdd
This package uses `@playwright/test` and `@cucumber/cucumber` as a peer dependencies.
For brand new projects they will be installed automatically with `playwright-bdd`.
-For existing projects you may need to update them to the latest verions:
+For existing projects you may need to update them to the latest versions:
```
npm i -D @playwright/test @cucumber/cucumber
@@ -18,4 +18,4 @@ After installing/updating Playwright you need to [install browsers](https://play
```
npx playwright install
-```
\ No newline at end of file
+```
diff --git a/docs/writing-features.md b/docs/writing-features.md
index 988602e8..0c19e864 100644
--- a/docs/writing-features.md
+++ b/docs/writing-features.md
@@ -60,7 +60,7 @@ It can be not reliable for reporters that keep track of test history, because on
There are 3 ways to set consistent title for examples.
#### 1. Use scenario name as a template
-You can add column names like `` to the scenario name. In that case sceanrio name will be used as a title template for generated examples. E.g.:
+You can add column names like `` to the scenario name. In that case scenario name will be used as a title template for generated examples. E.g.:
```gherkin
Feature: Localization
@@ -194,7 +194,7 @@ Strictly use only the following step definitions:
{steps list from bddgen export}
```
-> Feel free to imporve that template and share the results
+> Feel free to improve that template and share the results
Filled prompt for Todo app:
```
diff --git a/docs/writing-steps.md b/docs/writing-steps.md
index af070a30..ecc1803c 100644
--- a/docs/writing-steps.md
+++ b/docs/writing-steps.md
@@ -4,7 +4,7 @@ There are two ways of writing step definitions:
2. **Cucumber-style** - recommended for migrating existing CucumberJS projects to Playwright runner
## Playwright-style
-Playwright-style allows you to write step definitions like a regular playwright tests.
+Playwright-style allows you to write step definitions like regular Playwright tests.
You get all benefits of [built-in fixtures](https://playwright.dev/docs/test-fixtures#built-in-fixtures) as well as [custom fixtures](https://playwright.dev/docs/test-fixtures#with-fixtures).
Playwright-style highlights:
@@ -306,7 +306,7 @@ When('I open todo page', async function () {
```
For **TypeScript** you can pass `typeof test` as a second generic parameter to `BddWorld`
-to get propper typing:
+to get proper typing:
```ts
type MyWorld = BddWorld