Our Head of AQA, Taras Oleksyn, recently sat with WebsitePlanet.com to talk about creating a perfect automation testing strategy for a website, evaluating the success of an automation testing project, and everything in between.
Automated testing can benefit a website testing project a lot, allowing teams to test more in less time and with better outcomes. However, every successful automation project starts with in-depth planning — ideally, with a test strategy.
Last week, TestFort’s Taras Oleksyn shared his thoughts on the role of automation in website testing, how to create a good strategy, practical automation project management tips, and more, in a new interview.
Check out the interview to get the full scoop and take a look at the highlights below.
On the Importance of Automation Website Testing
Taras Oleksyn, Head of Automation Department, TestFort
“With the right approach, automation can become an invaluable solution for achieving and maintaining website quality. It improves the accuracy of testing, allows teams to achieve higher test coverage, provides convenient performance monitoring options, and helps speed up release cycles, supporting CI/CD practices.”
On Test Strategy vs. Test Plan Comparison
Taras Oleksyn, Head of Automation Department, TestFort
“An automation testing strategy should not be confused with a test plan. The major difference between the two is who both documents are aimed at: a test strategy is designed for stakeholders, project managers, and senior management, while a test plan is created for the benefit of the testing team and operational staff.”
On Choosing Which Test Cases to
Taras Oleksyn, Head of Automation Department, TestFort
“Automating 100% of functional test cases and 50% of the remaining test cases will provide a better outcome and use the company’s resources better than an attempt to automate 100% of all test cases.”
On Which Testing Methodology to Use
Taras Oleksyn, Head of Automation Department, TestFort
“My two favorite automation testing methodologies are keyword-driven testing, where the whole process is based on keywords and uses simplified syntaxis for designing test scripts, and behavior-driven testing, which utilizes the Gherkin format of “given → when → then” for test scripts.”
For more insights on how to run a test automation project and evaluate the results, go over to WebsitePlanet’s blog.