Unit 1.6 Getting Your Tests Ready for Automation & Automation Intro
Overview
Decision Tables & State Transition Diagrams
New Technologies
Intro to Automation
Decision Tables & State Transition Diagrams
Decision Tables
Decision tables are used to attempt to check all possible combinations of user inputs and their outcomes.
Conditions are usually indicated by True(T) or False(F) or Yes(Y), No(N).
Other conditions can be added like Checkout(CO) or Error(E).
It’s a visual approach where the inputs and their corresponding behavior are put into table form.
These tables have 3 sections:
Conditions
Actions
Rules
State Transition Diagrams
State Transition Diagrams are used to see what changes happen with the input conditions that cause the state of the project to change.
There are four parts to a State Transition diagram:
State that the project might be in
Transitions from one state to another
Events that create a transition
Actions that result because of that transition
State Transition Diagram
New Technologies
Manual testing is great, but sometimes you want your processes to be faster or even automated.
Things like our regression testing or confirmation testing can take up a lot of our time when done manually.
Adding automation to our testing can help us be more accurate and efficient.
We will be going over a few different technologies that can help make our work process better and are just really cool.
Next unit we will be going over:
APIs using Postman
Load and Stress using JMeter
Unit Testing using Typescript, Selenium, Node and Jest
Git and Github
Intro to Automation
Automation can help us turn our test cases into something that our machine does for us.
We use the elements of web pages and manipulate those containers in order to have our machine run our tests.
This helps us a ton when it comes to regression testing which can be very time consuming.
Instead of spending up to 48 total hours retesting all of our old tests we can automate those tests so that they are finishing in seconds.