Commit 2480414

committed

Added part 6 to README

1 parent 843729a commit 2480414Copy full SHA for 2480414

File tree

1 file changed

+11

-3

lines changed

README.md

1 file changed

+11

-3

lines changed

`‎README.md‎`

Lines changed: 11 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -18,7 +18,7 @@ Playwright tests can set up much faster than traditional Web UI tests.`
`18`	`18`
`19`	`19`	`In this tutorial, we will build a [Python](https://www.python.org/)`
`20`	`20`	`test automation project from the ground up using Playwright.`
`21`		`-We will automate web search engine tests together step-by-step`
	`21`	`+We will automate web tests together step-by-step`
`22`	`22`	`using Playwright for interactions and pytest for execution.`
`23`	`23`	`We'll also explore Playwright tricks`
`24`	`24`	`like cross-browser testing, capturing videos, and even running tests in parallel!`
`@@ -37,8 +37,8 @@ Some of the nice features Playwright offers include:`
`37`	`37`	`* very fast execution times (compared to other browser automation tools)`
`38`	`38`	`* cross-browser and mobile emulation support`
`39`	`39`	`* automatic waiting`
`40`		`-* built-in API calls`
`41`	`40`	`* screenshots and video capture`
	`41`	`+* built-in API calls`
`42`	`42`
`43`	`43`	`Microsoft is actively developing Playwright,`
`44`	`44`	`so new features are coming all the time!`
`@@ -60,7 +60,7 @@ I also have given (or will be giving) this tutorial as a live workshop at the fo`
`60`	`60`
`61`	`61`	`## Outline`
`62`	`62`
`63`		`-This tutorial has five main parts, each with three sections:`
	`63`	`+This tutorial has six main parts, each with three sections:`
`64`	`64`
`65`	`65`	`1. Getting started`
`66`	`66`	`1. What is Playwright?`
`@@ -82,6 +82,10 @@ This tutorial has five main parts, each with three sections:`
`82`	`82`	`1. Testing different browsers`
`83`	`83`	`2. Capturing screenshots and videos`
`84`	`84`	`3. Running tests in parallel`
	`85`	`+6. Testing with APIs`
	`86`	`+ 1. API setup`
	`87`	`+ 2. Writing a pure API test`
	`88`	`+ 3. Writing a hybrid UI/API test`
`85`	`89`
`86`	`90`
`87`	`91`	`## Prerequisites`
`@@ -98,6 +102,9 @@ You should also have a decent Python editor like`
`98`	`102`	`[Visual Studio Code](https://code.visualstudio.com/docs/languages/python)`
`99`	`103`	`or [PyCharm](https://www.jetbrains.com/pycharm/).`
`100`	`104`
	`105`	`+If you wish to complete Part 6 ("Testing with APIs"),`
	`106`	`+then you will need a [GitHub](https://github.com/) account.`
	`107`	`+`
`101`	`108`
`102`	`109`	`## Example code branches`
`103`	`110`
`@@ -113,4 +120,5 @@ The branch names are:`
`113`	`120`	`\| Part 3 \| 3-assertions \|`
`114`	`121`	`\| Part 4 \| 4-page-objects \|`
`115`	`122`	`\| Part 5 \| 5-playwright-tricks \|`
	`123`	`+\| Part 6 \| 6-api-testing \|`
`116`	`124`	`\| Complete \| main \|`

0 commit comments

Comments

(0)

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit 2480414

File tree

1 file changed

1 file changed

`‎README.md‎`

0 commit comments