This article will be a simple introduction to the main components of the ATF. ATF is structured in a very simple and easy way to be used fast and from every tester without having programming skills. Every test is splinted into test cases and steps. Everything starts with defining the roles and the privileges for each user. There are two types of users: Test Admin and Test Designer. Tests can be used in suites and may be reused in different scenarios. Test cases are built in steps and each step must be arranging in proper way to be executed. Test templates example can be reuse in different tests: Incident Template (will include: Submit form, validations, workflow etc.) The user has possibility to check the execution in real time in Client Test Runner mode. Very nice feature of ATF is the ability to have screenshots and to use them in order to collect visual data to analyse the defects or failures.
BEFORE The new Automated Test Framework (ATF) has just released and it has been a long-awaited for many people. Now there is a tool to perform automated testing in ServiceNow. This product comes build in with Istanbul version.
ATF comes with two predefined roles: atf_test_admin with all permissions and atf_test_designer who can create tests in addition to other things. Personally from tester prespective i think two additional roles might be useful: atf_test_manager and atf_test_tester.
BEFORE YOU START:
ATF comes as a pre-activated plugin but in order to execute tests you might need two things:
1 – Role required: [atf_test_admin]
2- Activate test execution property
How to activate it?
1- Navigate to Automated Test Framework > Administration > Properties.
2 – Set the test execution property.
To enable test and test suite execution, check Enable test/test suite execution.
To disable test and test suite execution, uncheck Enable test/test suite execution.
3 – Click Save.
ATF comes with a nice feature like suits. Tests can be collected in suits and they can be performed as a single suite.
1. Test 1 runs and finishes
2. Test 2 runs and finishes
3. Test Suite B starts
4. Test 3 runs and finishes
5. Test 2 doesn’t run again, since it already ran in Test Suite A
6. Test Suite B finishes
7. Test Suite A finishes
CLIENT TEST RUNNER
This module opens Clint Test Runner window. This window, labeled as UI Test Runner, may also be opened from the Run Test dialog box. Without this window opened, UI tests won’t run.
TEST RUN QUEUE
This module shows list of Tests that are Waiting or Running. When running a Test Suite, this lists all Tests that are part of the Test Suite and its child Test Suites, if any. This list doesn’t show the execution order, limiting its usefulness. NOTE: Tests can’t be scheduled to run at a later time.
This module shows list of Test Templates. These are used to build Test Steps in a Test. One Test Template comes with the demo data. A Test Template contains a list of Test Step Configurations in a Glide List.