Mark Ng
QA Lead, British Columbia Institute of Technology
This session is an introduction to our Test Automation process that I have helped set up for our Web and Banner ITS Solution Delivery development teams:
- What is QA (Quality Assurance)?
- What is test automation, and why should software development teams use it? (e.g., speed up deployments, minimize manual testing time, minimize human error that results from long manual testing times, etc.)
- The Katalon Studio Enterprise tool that we use to create our automation tests.
- Why did I choose an Enterprise testing tool vs. the creation of in-house test automation infrastructure? (e.g., centralized application with all required test automation plugins and libraries already included, can use record and play or create test scripts.)
- Tracking the health of our application through test automation results using Jenkins, a web view of all of our test automation job execution status.
- Explanation of the type of automation test suites (e.g., smoke vs. regression test suites, etc.) and their purpose.
- The setup of scheduling our test suites that run daily/overnight, on demand, and per code commits made by the development team.
- What types of tests should be automated?
- Looking to the future of automation tests.