@@ -10,17 +10,17 @@ It will also cover basic Playwright API calls.
1010Before we can automate interactions using Playwright's API, we must first understand how Playwright interacts with browsers.
1111There are three main layers to automation: * browsers* , * browser contexts* , and * pages* :
1212
13- 1 . A [ browser] ( https://playwright.dev/python/docs/browsers/ )
13+ 1 . A [ browser] ( https://playwright.dev/python/docs/browsers )
1414 is a single instance of a web browser.
1515 Playwright will automatically launch a browser instance specified by code or by inputs.
1616 Typically, this is either the Chromium, Firefox, or WebKit instance installed via ` playwright install ` ,
1717 but it may also be other browsers installed on your local machine.
18- 2 . A [ browser context] ( https://playwright.dev/python/docs/browser-contexts/ )
18+ 2 . A [ browser context] ( https://playwright.dev/python/docs/browser-contexts )
1919 is an isolated incognito-alike session within a browser instance.
2020 They are fast and cheap to create.
2121 One browser may have multiple browser contexts.
2222 The recommended practice is for all tests to share one browser instance but for each test to have its own browser context.
23- 3 . A [ page] ( https://playwright.dev/python/docs/pages/ )
23+ 3 . A [ page] ( https://playwright.dev/python/docs/pages )
2424 is a single tab or window within a browser context.
2525 A browser context may have multiple pages.
2626 Typically, an individual test should interact with only one page.
0 commit comments