Updates to testing from dry run

Author: GeekTrainer

content/guided-workshop/exercises/1-code-scanning.md

@@ -79,5 +79,5 @@ In this exercise, you enabled GitHub Advanced Security. You enabled Dependabot t
 ### Additional resources
 
 - [About GitHub Advanced Security](https://docs.github.com/en/get-started/learning-about-github/about-github-advanced-security)
-- [GitHub skills - Secure your repository's supply chain](https://github.com/skills/secure-repository-supply-chain)
-- [GitHub skills - Secure code game](https://github.com/skills/secure-code-game)
+- [GitHub Skills: Secure your repository's supply chain](https://github.com/skills/secure-repository-supply-chain)
+- [GitHub Skills: Secure code game](https://github.com/skills/secure-code-game)

content/guided-workshop/exercises/3-codespaces.md

@@ -104,4 +104,4 @@ Congratulations! You have now defined a custom development environment including
 - [GitHub Codespaces](https://github.com/features/codespaces)
 - [Getting started with GitHub Codespaces](https://docs.github.com/en/codespaces/overview)
 - [Defining dev containers](https://docs.github.com/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)
-- [Code with Codespaces](https://github.com/skills/code-with-codespaces)
+- [GitHub Skills: Code with Codespaces](https://github.com/skills/code-with-codespaces)

content/guided-workshop/exercises/4-testing.md

@@ -53,26 +53,24 @@ Let's create a workflow to implement testing.
     ```yml
     name: End-to-end tests
     on:
-        push:
-            branches: ["main"]
-        pull_request:
-            branches: ["main"]
+      push:
+        branches: ["main"]
+      pull_request:
+        branches: ["main"]
     jobs:
-        cypress-run:
-            runs-on: ubuntu-20.04
-            steps:
-                - name: Checkout
-                    uses: actions/checkout@v3
-                # Install NPM dependencies, cache them correctly
-                # and run all Cypress tests
-                - name: Cypress run
-                    uses: cypress-io/github-action@v5
-                    with:
-                        build: npm run build
-                        start: npm run start
-                        project: ./src
-                    env:
-                        MONGODB_URI: test
+      cypress-run:
+        runs-on: ubuntu-20.04
+        steps:
+          - name: Checkout
+            uses: actions/checkout@v3
+          - name: Cypress run
+            uses: cypress-io/github-action@v5
+            with:
+              build: npm run build
+              start: npm run start
+              project: ./src
+            env:
+              MONGODB_URI: test
     ```
 
     > **IMPORTANT:** YML is sensitive to tab/space levels. Ensure the tabbing is as displayed above.
@@ -102,27 +100,29 @@ Next is [Cypress](https://github.com/marketplace/actions/cypress-io), which will
 
 With the workflow created, let's push it to the repository. Typically you would create a [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) for any new code (which this is). To streamline the process, we're going to push straight to main as we'll be exploring pull requests and the [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow) in a later exercise. You'll start by obtaining the number of the [issue you created earlier](./2-issues.md), creating a commit for the new code, then pushing it to main.
 
-1. Open a terminal window in your codespace by pressing <kbd>Ctl</kbd> + <kbd>`</kbd>.
-1. List all issues for the repository by entering the following command in the terminal window and pressing <kbd>Enter</kbd> (or <kbd>Return</kbd> on a Mac):
+> **NOTE:** All commands are entered using the terminal window in the codespace.
+
+1. Use the open terminal window in your codespace, or open it (if necessary) by pressing <kbd>Ctl</kbd> + <kbd>`</kbd>.
+1. List all issues for the repository by entering the following command in the terminal window:
 
     ```bash
     gh issue list
     ```
 
 1. Note the issue number for the one titled **Implement testing**.
-1. Stage all files by entering the following command in the terminal window and pressing <kbd>Enter</kbd> (or <kbd>Return</kbd> on a Mac):
+1. Stage all files by entering the following command in the terminal window:
 
     ```bash
     git add .
     ```
 
-1. Commit all changes with a message by entering the following command in the terminal window and pressing <kbd>Enter</kbd> (or <kbd>Return</kbd> on a Mac), replacing **<ISSUE_NUMBER>** with the number for the **Implement testing** issue:
+1. Commit all changes with a message by entering the following command in the terminal window, replacing **<ISSUE_NUMBER>** with the number for the **Implement testing** issue:
 
     ```bash
     git commit -m "Resolves #<ISSUE_NUMBER>"
     ```
 
-1. Push all changes to the repository by entering the following command in the terminal window and pressing <kbd>Enter</kbd> (or <kbd>Return</kbd> on a Mac):
+1. Push all changes to the repository by entering the following command in the terminal window:
 
     ```bash
     git push
@@ -138,13 +138,24 @@ Pushing the workflow definition to the repository counts as a push to `main`, me
 
 1. Return to your repository.
 1. Select the **Actions** tab.
-1. Select the name of the action on the left side.
-1. Note the test running (and eventually failing). You can click the name of the action to see the individual steps, and the logs provided by those steps.
+1. Select **End-to-end tests** on the left side.
+1. Note the tests running on the right side with a message of **Resolves <ISSUE_NUMBER>**, matching the commit message you used (and eventually failing).
 
-## Summary and next steps
+    ![Screenshot of the workflow running](./images/4-workflow-run.png)
 
-Implementing continuous integration and continuous deployment is critical to successful DevOps. Automating these processes ensures consistency and reduces the workload required for developers and administrators. You have created a workflow to run tests on any new code for your codebase.
+1. When the test fails, select the name of the run (which should be similar to **Resolves <ISSUE_NUMBER>**). You will see the results of the test, which will be similar to the screenshot below:
 
-Let's turn our attention to [adding code to our project](./5-coding.md).
+    ![Screenshot of results](./images/4-workflow-run.png)
+
+You've now seen a workflow, and explore the details of a run!
+
+## Summary and next steps
+
+Congratulations! You've implemented automated testing, a standard part of continuous integration, which is critical to successful DevOps. Automating these processes ensures consistency and reduces the workload required for developers and administrators. You have created a workflow to run tests on any new code for your codebase. Let's turn our attention to [adding code to our project](./5-coding.md).
 
 ### Resources
+
+- [GitHub Actions](https://github.com/features/actions)
+- [GitHub Actions Marketplace](https://github.com/marketplace?type=actions)
+- [About continuous integration](https://docs.github.com/en/actions/automating-builds-and-tests/about-continuous-integration)
+- [GitHub Skills: Test with Actions](https://github.com/skills/test-with-actions)

content/guided-workshop/exercises/7-create-environment.md

@@ -114,8 +114,6 @@ Let's create variables for the name of the resource group and your prefix:
 
 You've now configured Azure and added secrets & variables to your repository. You're now ready to create the workflow! This workflow will run on-demand, and create the resources on Azure. This will both make it easier to create everything and ensure it's done correctly.
 
-Previously you created a workflow by using the **Actions** tab in your repository. While this works, it's not always ideal as you will often want better support from your editor. Since workflows are defined as [YML](https://en.wikipedia.org/wiki/YAML) files
-
 1. Return to your codespace.
 1. If the **Terminal** window isn't already open, open it by pressing <kbd>Ctl</kbd> - <kbd>`</kbd> on your keyboard.
 1. Switch to the `main` branch, pull any changes currently on the server to your codespace, and create a new branch by entering the following command in the terminal window and pressing <kbd>Enter</kbd> (or <kbd>Return</kbd> on a Mac):