Further edits

Author: gitName

learn-pr/azure-devops/run-functional-tests-azure-pipelines/5-write-ui-tests.yml

@@ -1,8 +1,8 @@
 ### YamlMime:ModuleUnit
 uid: learn.azdo.run-functional-tests-azure-pipelines.5-write-ui-tests
-title: Exercise - Write the UI tests
+title: Write the UI tests
 metadata:
-  title: Exercise - Write the UI tests
+  title: Write the UI tests
   description: Map manual testing steps to automated test cases by using Selenium.
   ms.date: 05/07/2025
   author: steved0x

learn-pr/azure-devops/run-functional-tests-azure-pipelines/includes/5-write-ui-tests.md

@@ -65,7 +65,7 @@ This diagram shows the `IWebDriver` interface and a few of the classes that impl
 
 The diagram shows three of the methods that `IWebDriver` provides: `Navigate`, `FindElement`, and `Close`.
 
-The three classes shown here, `ChromeDriver`, `FirefoxDriver`, and `EdgeDriver`, each implement `IWebDriver` and its methods. There are other classes, such as `SafariDriver`, that also implement `IWebDriver`. Each driver class can control the web browser that it represents.
+The three classes shown here—`ChromeDriver`, `FirefoxDriver`, and `EdgeDriver`—each implement `IWebDriver` and its methods. There are other classes, such as `SafariDriver`, that also implement `IWebDriver`. Each driver class can control the web browser that it represents.
 
 Andy adds a member variable named `driver` to the `HomePageTest` class, like this code:
 
@@ -224,7 +224,7 @@ private void ClickElement(IWebElement element)
 
 ### Define the test method
 
-**Andy:** Now, we're ready to define the test method. Based on the manual tests that we ran earlier, let's call this method `ClickLinkById_ShouldDisplayModalById`. It's a good practice to give test methods descriptive names that define precisely what the test accomplishes. Here, we want to click a link defined by its `id` attribute. Then we want to verify that the proper modal window appears, also by using its `id` attribute.
+**Andy:** Now, we're ready to define the test method. Based on the manual tests that we ran earlier, let's call this method `ClickLinkById_ShouldDisplayModalById`. It's a good practice to give test methods descriptive names that define precisely what the test accomplishes. Here, we want to select a link defined by its `id` attribute. Then we want to verify that the proper modal window appears, also by using its `id` attribute.
 
 Andy adds starter code for the test method:
 
@@ -238,7 +238,7 @@ public void ClickLinkById_ShouldDisplayModalById(string linkId, string modalId)
 
 **Amita:** I can handle this part. We want to:
 
-1. Locate the link by its `id` attribute and then click the link.
+1. Locate the link by its `id` attribute and select the link.
 1. Locate the resulting modal.
 1. Close the modal.
 1. Verify that the modal was displayed successfully.
@@ -283,15 +283,15 @@ public void ClickLinkById_ShouldDisplayModalById(string linkId, string modalId)
 }
 ```
 
-**Amita:** The coding looks great so far. But how do we connect this test to the `id` attributes that we collected earlier?
+**Amita:** The coding looks great so far, but how do we connect this test to the `id` attributes that we collected earlier?
 
 **Andy:** Great question. We'll handle that next.
 
 ### Define test case data
 
 **Andy:** In NUnit, you can provide data to your tests in a few ways. Here, we use the `TestCase` attribute. This attribute takes arguments that it later passes back to the test method when it runs. We can have multiple `TestCase` attributes that each test a different feature of our app. Each `TestCase` attribute produces a test case that's included in the report that appears at the end of a pipeline run.
 
-Andy adds these `TestCase` attributes to the test method. These attributes describe the **Download game** button, one of the game screens, and the top player on the leaderboard. Each attribute specifies two `id` attributes: one for the link to click and one for the corresponding modal window.
+Andy adds these `TestCase` attributes to the test method. These attributes describe the **Download game** button, one of the game screens, and the top player on the leaderboard. Each attribute specifies two `id` attributes: one for the link to select and one for the corresponding modal window.
 
 ```cs
 // Download game
@@ -306,7 +306,7 @@ public void ClickLinkById_ShouldDisplayModalById(string linkId, string modalId)
 ...
 ```
 
-**Andy:** For each `TestCase` attribute, the first parameter is the `id` attribute for the link to click on. The second parameter is the `id` attribute for the modal window that we expect to appear. You can see how these parameters correspond to the two-string arguments in our test method.
+**Andy:** For each `TestCase` attribute, the first parameter is the `id` attribute for the link to select. The second parameter is the `id` attribute for the modal window that we expect to appear. You can see how these parameters correspond to the two-string arguments in our test method.
 
 **Amita:** I do see that. With some practice, I think I can add my own tests. When can we see these tests running in our pipeline?
 

learn-pr/azure-devops/run-functional-tests-azure-pipelines/includes/6-run-ui-tests.md

@@ -89,11 +89,13 @@ To run the tests locally:
 
 1. In Visual Studio Code, go to the integrated terminal and open a new terminal window.
 1. Run the following commands in the new terminal window.
+
     ```dotnetcli
     dotnet build --configuration Release
     dotnet run --configuration Release --no-build --project Tailspin.SpaceGame.Web
     ```
-1. Make a note of the local website link, in this example it is `http://localhost:5000`.
+
+1. Make a note of the local website link; in this example, it's `http://localhost:5000`.
 1. Switch back to the terminal window where you set the environment variables in the previous step, and ensure that you're in your project's root directory. Here's an example:
 
     ```bash

learn-pr/azure-devops/run-functional-tests-azure-pipelines/includes/8-summary.md

@@ -27,8 +27,8 @@ You have set up UI tests that run on Windows. But you can also run your tests on
 
 If you're interested in testing UI by using Selenium, check out these resources to help you go further:
 
-* [SeleniumHQ.org](https://www.seleniumhq.org?azure-portal=true)
-* [Selenium IDE](https://www.seleniumhq.org/selenium-ide?azure-portal=true)
+* [SeleniumHQ.org](https://www.selenium.dev/?azure-portal=true)
+* [Selenium IDE](https://www.selenium.dev/selenium-ide/?azure-portal=true)
 * [UI test with Selenium](/azure/devops/pipelines/test/continuous-test-selenium?azure-portal=true)
 * [UI testing considerations](/azure/devops/pipelines/test/ui-testing-considerations?azure-portal=true&tabs=mstest)
 * [Use WebDriver to automate Microsoft Edge](/microsoft-edge/webdriver-chromium?azure-portal=true)

learn-pr/azure-devops/run-functional-tests-azure-pipelines/includes/code/6-azure-pipelines.yml

@@ -3,7 +3,7 @@ trigger:
 
 variables:
   buildConfiguration: 'Release'
-  dotnetSdkVersion: '6.x'
+  dotnetSdkVersion: '8.x'
 
 stages:
 - stage: 'Build'
@@ -18,7 +18,7 @@ stages:
 
     variables:
       wwwrootDir: 'Tailspin.SpaceGame.Web/wwwroot'
-      dotnetSdkVersion: '6.x'
+      dotnetSdkVersion: '8.x'
 
     steps:
     - task: UseDotNet@2