Hello to all PractiTesters!
Recently we performed another update of PractiTest with important additions to make your work better and more effective.
Let’s start with some additions to make your work clearer, specially when you are only getting started with the system.
We believe that each tester (or non-tester) working with PT should understand our methodology (and read the page at least once).
As part of our Testing Methodology you can see that:
- A Test Set is a collection of Test Instances
- An Instance is linked to a Test (in the Test Library), so that each Test can be linked to multiple Instances
- Each Instance can have multiple Test Runs (where the status of the Instance is the status of its last Test Run).
The Test Legend
To avoid confusion (“where am I right now?”), we added a Test Legend in all testing related entities, indicating the location in the application.
We believe that especially for new PractiTesters, this legend will help understand our methodology and the links between the different entities.
The standard Testing Scenario
- Each Test (in the Test Library) is defined only once, with all its relevant steps
- Test Set creation, and their respective Instances, are defined once in a while when there’s a reason to start running these tests ( e.g. a new version /release, new functionality, etc).
- Whenever a user goes to the Instance, and presses the Run button, a new Test Run is created, copying all the steps to the test run (so if the Test in the Library is changed later, the steps in the run will not change)
- If for any reason, an Instance needs to be re-run in a specific Test Set, the tester will create an additional Run and not overwrite the previous run. Ensuring all run history is saved.
Better Test Sets and Runs navigation
In addition to the above we decided to streamline the testing process, making the run button much more powerful, and skipping some screens when they’re not required:
- If the user starts a Run from the instance grid, and the Instance has no required fields or older runs, then it goes straight to the run window (with the steps). Enabling to start and testing right a way.
- In cases when there are required fields in the instance that are not filled, it will go to the instance window.
- And in the case there are older runs (that you want to review before starting your new Run!), it will go to the instance window, showing previous runs, enabling to go and check or update one of those test runs.
We are sure these changes will make your testing experience more productive. And we invite you to share with us additional ideas to make your work even more effective in the future.