When you want to hire software tester, it’s necessary to check his understanding of IT testing services. The knowledge of testing artifacts should be examined first because it shows the level of being a professional.
Let’s study or revise main testing artifacts that every tester must know.
5 Testing Artifacts
- Test plan.
- Test case.
- Test script or test suite.
- Defects description.
- Test report.
Test Plan
There are at least two generally accepted understanding of that document:
- The document describes who, what, when and how will be tested.
- Document describing all the necessary tests to validate your application.
When we are speaking about test plan, we mean the first item in the above-mentioned list.
Test Case
Test case – is the description of initial requirements, input data, users actions and expected results. It’s a good practice to write test cases on the basis of Use cases. The test case is like the smallest particle of an atom for the under-mentioned documents (test case as well as like an atom can be split into conditions, input data, results).
Name Variations
- Atomic test;
- Test version;
- Test option;
- Test Case.
Test Scripts or Test Suite
These are test cases that were grouped on the basis of some feature (for example, tested functionality). They can be as dependent on the sequence of execution (Test script)) and independent (Test suite). Most commonly allocated are sets: a set of test scripts for smoke-test and acceptance plan testing.
What about smoke-test, it’s a document that includes the set of particular cases, which cover the main functionality of the object or system. Its aim to assure that key program functions work correctly. Good practice – to accept the build in testing based on passing Smoke-test.
Add Comment