Managing and running tests is the core of your testing process. It is important that your tests are properly organized and defined, in order to perform your job in the most effective and efficient way.
Although you can use PractiTest as a stand-alone bug tracking tool, or as a requirement repository, the extra added value of PractiTest’s Application Life Management (ALM) comes from putting all pieces together. For example, PractiTest can automatically show you which requirements are not covered by tests, or what customer features are more or less stable than others; it can allow your developers to see the exact tests where the bugs were detected, and be able to manage all your Development Life Cycle in one place.
Test Case Creation and Management
The Test Library module is where your tests are created and stored. There are two types of test cases that can be created in the Test Library: Scripted - regular test cases where users predefine steps and Exploratory - without predefined steps where users add annotations "on the fly". These tests can later be run as part of your Test Sets. The grid shows your tests based on the view or folder of your choice. Each Test has its own meta-data, as defined by its system fields and custom fields; you can customize your tests by adding as many fields as your product and process require.
A test is usually comprised of several steps. The steps describe in detail which validation checks you need to perform on your application or system.
To enter steps to your tests, go to the Steps tab and add your steps one by one. Each Test Step has the following fields:
Name, Description and Expected results. In addition, you can add file or link attachments to each step.
Step Attachments , Test Attachments, and Step Run Attachments
Attachments can be added to specific steps, but also to the test in general, to be viewed later in the test’s ‘Attachments’ tab. In the test’s general attachment tab you may put attachments that are relevant for the whole test and not just a specific step (for example, system configuration document for the test).
A step of a Test Run (ie. step-run), shows the Test Library’s Step fields and attachments, and it may have its own attachments. The difference between the attachments of a Test Library Step and a Step Run, is that Library step attachments, may have screen shot of how things SHOULD appear, while the Step run attachments, can show a log of the run, or a screen shot of how things looks while running the test.
After saving a test, you can always go back and add, delete or re-order steps. PractiTest even allows you to modify your steps as you run your tests.
Managing your Test Library
The Test grid is initially displayed with the default view, showing all your tests and some default fields in the columns. As part of your views, you can fully configure which tests to display, and which fields the grid will show. Other than viewing and editing single tests, you can also perform actions from the test grid itself, such as editing, cloning and deletion of multiple tests at one time.
How do I run my tests?
Before you can run a test, you need to add it as part of a Test Set. Test sets use copies of the tests you have in the library – called test instances. This way, you can make changes to a single test-instance without altering the original test (If, for example, you delete a step in a test instance, your original test in the Test Library will stay intact). Each test can be added to as many test-cases as needed.
When viewing a test in the Test Library you can open the instances tab in order to see exactly where it’s being used.
For information on creating Test Sets and running tests, go to Test Sets & Runs section.
The Traceability tab
Under the Traceability tab, you can see which requirements this test is covering, as well as the issues that were found using this test.