Dynamic application environments can make the task of predicting results difficult or even impossible before the test is executed. In this seminar, the participant will learn how to use INI files to capture and compare expected results to design tests that are more flexible and easier to maintain.
While it is good practice to design automated tests to be independent, it is not always expeditious. There are situations where the data state of a test environment is difficult to manage or where the ‘state-full’ nature of a transaction requires components to be built one upon another. In these cases, a system of managing test dependencies is required.
In this presentation, you will learn how to implement a mechanism for building a system that manages test dependencies using the built-in test identifier and an .ini file that records the test status of each test. Each of the described components can be requested by emailing Zeenyx Support after the presentation.
Test data is an important component to building manual and automated tests with AscentialTest. In this session, we will explore all of the different ways that test data can be stored and accessed to promote both efficiency and re-usability.
The ‘start’ and ‘finish’ phases are essential components of an automated testing project.
Many applications contain entities that must be unique. A common example is a customer or member identifier like email address.
Learn how to avoid the domino effect in test automation when test failures occur:
What are the golden rules for test design?
What is the base state of a target application?
How to create an App State?
How to use ‘On Finish’ to implement a recovery mechanism?