Skip to content

Commit 848808f

Browse files
authored
pull base content,head:MicrosoftDocs:main,into:wwlpublishsync
2 parents 4b6d039 + 719367f commit 848808f

File tree

160 files changed

+938
-740
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

160 files changed

+938
-740
lines changed

.openpublishing.redirection.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -199,6 +199,10 @@
199199
"source_path_from_root": "/learn-pr/wwl-data-ai/deploy-paas-solutions-with-azure-sql/7-describe-sql-edge.yml",
200200
"redirect_url": "/training/modules/deploy-paas-solutions-with-azure-sql/"
201201
},
202+
{
203+
"source_path_from_root": "/learn-pr/wwl-data-ai/describe-performance-monitoring/6-describe-azure-sql-insights.yml",
204+
"redirect_url": "/training/modules/describe-performance-monitoring/"
205+
},
202206
{
203207
"source_path_from_root": "/learn-pr/wwl-data-ai/query-data-warehouse-microsoft-fabric/3-explore-visual-query-editor.yml",
204208
"redirect_url": "/training/modules/query-data-warehouse-microsoft-fabric/"

learn-pr/advocates/build-with-playwright/1-introduction.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Introduction
44
metadata:
55
title: Introduction
66
description: Introduction
7-
ms.date: 05/08/2024
7+
ms.date: 03/19/2025
88
ms.author: debbieobrien
99
author: debs-obrien
1010
ms.manager: jamont

learn-pr/advocates/build-with-playwright/2-introduction-to-playwright.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: What is Playwright?
44
metadata:
55
title: What is Playwright?
66
description: In this module, you learn about Playwright, a library that enables you to automate web browsers. You learn how to set up Playwright, create a new Playwright project, and write your first Playwright test.
7-
ms.date: 05/08/2024
7+
ms.date: 03/19/2025
88
ms.author: debbieobrien
99
author: debs-obrien
1010
ms.manager: jamont

learn-pr/advocates/build-with-playwright/3-set-up-playwright.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ uid: learn.build-with-playwright.set-up-playwright
33
title: "Exercise: Getting Started with Playwright"
44
metadata:
55
title: "Exercise: Getting Started with Playwright"
6-
description: Lets begin by installing Playwright, then we explore the tool and validate that we can run the example tests that come when installing Playwright.
7-
ms.date: 05/08/2024
6+
description: Let's begin by installing Playwright, then we explore the tool and validate that we can run the example tests that come when installing Playwright.
7+
ms.date: 03/19/2025
88
ms.author: debbieobrien
99
author: debs-obrien
1010
ms.manager: jamont

learn-pr/advocates/build-with-playwright/4-understand-test-configuration.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ uid: learn.build-with-playwright.understand-test-configuration
33
title: "Exercise: Deconstruct a Playwright Test"
44
metadata:
55
title: "Exercise: Deconstruct a Playwright Test"
6-
description: Lets now dive deeper into the Playwright Test Specification and Configuration. Lets open the project we created in the previous section in our favorite code editor and explore the files that Playwright installed. We're using Visual Studio Code for the workshop.
7-
ms.date: 05/08/2024
6+
description: Let's now dive deeper into the Playwright Test Specification and Configuration. Let's open the project we created in the previous section in our favorite code editor and explore the files that Playwright installed. We're using Visual Studio Code for the workshop.
7+
ms.date: 03/19/2025
88
ms.author: debbieobrien
99
author: debs-obrien
1010
ms.manager: jamont

learn-pr/advocates/build-with-playwright/5-understand-test-specification.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Understand Test Specification
44
metadata:
55
title: Understand Test Specification
66
description: The default test runs on the tests/example.spec.ts specification. Let's unpack that to see what it contains.
7-
ms.date: 05/08/2024
7+
ms.date: 03/19/2025
88
ms.author: debbieobrien
99
author: debs-obrien
1010
ms.manager: jamont

learn-pr/advocates/build-with-playwright/6-get-started-using-vs-code.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: "Exercise: Using Playwright in Visual Studio Code"
44
metadata:
55
title: "Exercise: Using Playwright in Visual Studio Code"
66
description: In the previous section, we walked through core concepts related to the Playwright Test Configuration and Playwright Test Specification - but we used the Playwright command line (CLI) for executing our tests and viewing reports. In this section, we'll use Visual Studio Code to run tests, debug tests, and record new tests.
7-
ms.date: 05/08/2024
7+
ms.date: 03/19/2025
88
ms.author: debbieobrien
99
author: debs-obrien
1010
ms.manager: jamont

learn-pr/advocates/build-with-playwright/7-knowledge-check.yml

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Knowledge check
44
metadata:
55
title: Knowledge check
66
description: Check your understanding so far.
7-
ms.date: 05/08/2024
7+
ms.date: 03/19/2025
88
ms.author: debbieobrien
99
author: debs-obrien
1010
ms.manager: jamont
@@ -17,45 +17,45 @@ quiz:
1717
questions:
1818
- content: Which of the following is a fixture in Playwright?
1919
choices:
20-
- content: page
20+
- content: "`page`"
2121
isCorrect: true
2222
explanation: "Correct: In Playwright a page is a built-in fixture which is passed into your tests to ensure test isolation."
23-
- content: click
23+
- content: "`click`"
2424
isCorrect: false
2525
explanation: "Incorrect: click is an action that represents a user clicking."
26-
- content: goto
26+
- content: "`goto`"
2727
isCorrect: false
2828
explanation: "Incorrect: goto is a method used for navigating to a URL."
29-
- content: expect
29+
- content: "`expect`"
3030
isCorrect: false
3131
explanation: "Incorrect: expect is a function used with a matcher to assert a condition."
3232

3333
- content: Which of the following groups related tests together in Playwright?
3434
choices:
35-
- content: getByRole
35+
- content: "`getByRole`"
3636
isCorrect: false
3737
explanation: "Incorrect: getByRole is a locator which is how you find elements on a page."
38-
- content: describe
38+
- content: "`describe`"
3939
isCorrect: true
4040
explanation: "Correct: Describe allows us to group Test Case objects logically in a file."
41-
- content: page
41+
- content: "`page`"
4242
isCorrect: false
4343
explanation: "Incorrect: In Playwright a page is a built-in fixture which is passed into your tests to ensure test isolation."
44-
- content: beforeEach
44+
- content: "`beforeEach`"
4545
isCorrect: false
4646
explanation: "Incorrect: beforeEach is a hook that can be applied to all tests within a group."
4747

4848
- content: Which of the following is a locator in Playwright?
4949
choices:
50-
- content: expect
50+
- content: "`expect`"
5151
isCorrect: false
5252
explanation: "Incorrect: expect is a function used with a matcher to assert a condition."
53-
- content: toBeVisible
53+
- content: "`toBeVisible`"
5454
isCorrect: false
5555
explanation: "Incorrect: toBeVisible is an assertion for validating outcomes of automated actions."
56-
- content: getByRole.
56+
- content: "`getByRole`"
5757
isCorrect: true
5858
explanation: "Correct: getByRole is a locator that is used to find an element on the page by its accessible role."
59-
- content: goto.
59+
- content: "`goto`"
6060
isCorrect: false
6161
explanation: "Incorrect: goto is a method used for navigating to a URL."

learn-pr/advocates/build-with-playwright/8-summary.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Summary
44
metadata:
55
title: Summary
66
description: Summary
7-
ms.date: 05/08/2024
7+
ms.date: 03/19/2025
88
ms.author: debbieobrien
99
author: debs-obrien
1010
ms.manager: jamont
Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,22 @@
1-
Thanks to CI/CD pipelines, modern web apps are deployed more frequently, often being pushed to production multiple times daily. Web apps are becoming more complex - with more dynamic content, more elements per page, and more complex user interactions. Web apps are accessed by more users, on a wider range of devices, and over more diverse networks.
1+
Thanks to CI/CD pipelines, modern web apps are deployed more frequently, often being pushed to production multiple times daily. Web apps are becoming more complex, with more dynamic content, more elements per page, and more complex user interactions. Web apps are accessed by more users, on a wider range of devices, and over more diverse networks.
22

3-
Delivering a reliable and consistent user experience in this environment is challenging. Testing becomes critical to ensure that the app is working as expected, and that new changes don't break existing functionality. Traditional Quality Assurance approaches that are relied on manual testers wouldn't scale due to the demands of these modern apps. We need automated testing approaches that can perform repetitive, time-consuming tests reliably and consistently.
3+
Delivering a reliable and consistent user experience in this environment is challenging. Testing becomes critical to ensure that the app is working as expected and that new changes don't break existing functionality. Traditional quality assurance approaches that rely on manual testers don't scale due to the demands of these modern apps. We need automated testing approaches that can perform repetitive, time-consuming tests reliably and consistently.
44

55
Test Automation is the process of using software tools and processes to execute testing strategies with minimal manual involvement and automated repeatable workflows. Test Automation frameworks provide tools, libraries, and rules for developers to execute automated testing plans. Popular options include Selenium, Cypress, and Playwright.
66

7-
## Learning Objectives
7+
## Learning objectives
88

9-
In this module, you will learn:
9+
In this module, you'll learn:
1010

11-
* How to use Playwright to test a sample web application.
11+
* How to use Playwright to test a sample web application.
1212
* How to run tests, view test reports, and understand the structure of a Playwright project.
1313
* How to use Visual Studio Code to run tests, debug tests, and record new tests.
14-
* How to create a new test suite, and how to refine your tests.
14+
* How to create a new test suite, and how to refine your tests.
1515

1616
## Prerequisites
1717

18-
To get started with Playwright,
18+
To get started with Playwright, you should have:
1919

20-
* Visual Studio Code installed
21-
* Latest version of node
22-
* Latest version of npm
20+
* [Visual Studio Code](https://code.visualstudio.com/) installed
21+
* [Latest version of node](https://nodejs.org/en/download/current)
22+
* [Latest version of npm](https://docs.npmjs.com/try-the-latest-stable-version-of-npm)

0 commit comments

Comments
 (0)