In this automation best practices workshop you will learn the latest and greatest tools and techniques to drastically improve your testing!

We will focus on a holistic approach of testing front-end and back-end, web and APIs, functional testing, component testing, and many other things in between 😁

✅What is an automated atomic test

✅How to code automated atomic tests

✅How to login without a UI using a HTML web forms

✅How to login without a UI using JWT

✅How to write a component test

✅How to add a test id to our web app

✅How to correctly test a link and a tab

✅How to replace e2e tests with component tests

✅visual e2e tests

✅visual cross-browser tests

✅CICD with Github Actions

1. ReactJS
2. Cypress
3. WebdriverIO
4. React testing library
5. Jest
6. Screener visual E2E testing
7. Sauce Labs
8. Github Actions

• Automated atomic tests
• Login testing
• Full coverage testing
• Visual E2E testing
• CICD

• Use NVM for this installation by following instructions
• It should be just a single command to run in our terminal
• !Don't forget to restart your terminal!
• After installation, confirm install was correct by running nvm and seeing an output
• Intall Node 14 with nvm install 14

Here's what the output would look like:

Downloading and installing node v14.16.1...
Downloading https://nodejs.org/dist/v14.16.1/node-v14.16.1-darwin-x64.tar.xz...
######################################################################### 100.0%
Computing checksum with shasum -a 256
Checksums matched!
Now using node v14.16.1 (npm v6.14.12)
Creating default alias: default -> 14 (-> v14.16.1)

• Confirm node installation with node --version and seeing v14.16.1 or similar
• Confirm NVM is set to 14 for default by running the following commands:

nvm list #will show all versions
nvm use 14 #to use 14
nvm alias default 14.16.x #to set it to the default

1. Sign up for a free Github account
2. Fork this respository

• Make sure you are logged into Github
• click the Fork in the upper right of the Github.

3. Clone your fork of the repository to your machine. Must have Git installed

git clone URL_OF_YOUR_FORK

4. Navigate to the directory of where you cloned your repo

cd YOUR_FORK_DIR/automation-best-practices

cd my-react-app
npm install
npm run start

Expected Output:

Your output should look similar to this

Compiled successfully!

You can now view my-react-app in the browser.

  Local:            http://localhost:3000
  On Your Network:  http://172.20.10.2:3000

Note that the development build is not optimized.
To create a production build, use npm run build.

1. Copy your Sauce Labs username and accessKey in the User Settings section of the Sauce Labs Dashboard.

2. Open a Terminal window (command prompt for Windows) and set your Sauce Labs Environment variables:

   Mac OSX:

   $ export SAUCE_USERNAME="username"
   $ export SAUCE_ACCESS_KEY="accessKey"
   

   Windows:

   > set SAUCE_USERNAME="username"
   > set SAUCE_ACCESS_KEY="accessKey"
   

   To set an environment variables permanently in Windows, you must append it to the PATH variable.

   Go to Control Panel > System > Windows version > Advanced System Settings > Environment Variables > System Variables > Edit > New

   Then set the "Name" and "Value" for each variable

3. Test the environment variables

   Mac OSX:

   $ echo $SAUCE_USERNAME
   $ echo $SAUCE_ACCESS_KEY
   

   WARNING FOR UNIX USERS!: If you have problems setting your environment variables, run the following commands in your terminal:

   $ launchctl setenv SAUCE_USERNAME $SAUCE_USERNAME
   $ launchctl setenv SAUCE_ACCESS_KEY $SAUCE_ACCESS_KEY
   

   Windows:

   > echo %SAUCE_USERNAME%
   > echo %SAUCE_ACCESS_KEY%
   

💡 this is a tip

🏋️‍♀️ this is an exercise for you to do

❓ this is a question for us to think and talk about. Try not to scroll beyond this question before we discuss