XenoGuard Documentation

Preparing Your First Automated Test

Once you have a clear understanding which testing framework is the right one for you, you can start preparing your first automated test.

Depending on the complexity of your use case, the steps may vary. We have selected the most universal ones and arranged them in chronological order:

Goals and Priorities

At a high level, the goal is to ensure that a piece of software or a system works correctly. But, depending on the situation, this can mean different things.

For instance, if you launch a completely new application, you have to test every single feature. Nonetheless, your resources may be insufficient for this, or you may have a tough deadline. In this case, you can prioritize what should be tested first and what can be checked later. Two approaches to such prioritization are possible:

  1. You can divide your users into different groups ranging from those who will use your application very often (power users) and who will use it only occasionally (all the others). Then, you can find out which features are most important for each group and set your testing priorities accordingly. 
  2. Within the same approach and in case you have a lot of features, you can ask your stakeholders and/or users to divide all features into must-have, should-have, and nice-to-have categories. Invite them to think about features that are critical and those that are not.  

You will learn from the history of XenoGuard that testing is used to ensure that an application not only stands a routine workload but can also handle error and stress conditions. For instance, that an application won't get stuck if a user enters information that does not pass its validation rules, such as ZIP code instead of a phone number, etc.

Besides, as already mentioned, the user interface must produce expected results. The last goal is generally referred to as bug detection

Another important goal is to ensure that all buttons work and that the application won't hang if a user clicks them too quickly. This is a part of the bigger usability testing that also includes manual testing to evaluate the convenience of the GUI. 

Time Plan

Once you have set your priorities, it's time to put them into your calendar. The timeline must remain realistic.

Responsibilities

Planning and distribution of responsibilities may overlap since you need to inform all involved and receive from them a confirmation that they have free capacities. 

Testing Scenario

After you know exactly what to test, how much time you have, and how many human resources you can engage, you can start with the testing scenario. A testing scenario is often considered as a high-level action plan that outlines the functionality to test. It needs to be broken down into test cases.

Test Cases

A test case is the last preparation step before you actually can start building testing scripts with XenoGuard. A test case describes in the highest detail which features must be tested and how, for instance, the sequence of the buttons to be clicked on, fields to be filled with the data, what kind of data, etc. 

One testing scenario can have more than one test case. 

Testing Scripts 

A testing script is a programmed implementation of a test case or any part of it. A script is a sequence of commands with parameters, variables, loops, and conditions. [ADD LINKS to Glossary later]

However, a script is not necessarily written in a programming language. As this is the case with XenoGuard, you can create a script with a drag-and-drop, low- or no-code tool that does not require any developer knowledge.


All these steps are tool-agnostic. In the next section, we will explain why you should create your testing scripts with XenoGuard, how XenoGuard helps you to integrate different approaches to test automation, as well as test automation best practices.