Let’s pause and look at the fields that make up a test case.
Test case Id and Test case description are the generic ones.
The other fields can be explained as follows:
- Precondition: State of the AUT (the state in which the AUT needs to be for us to get started).
- Input: Data entry steps. For these steps, it is important to note what kind of input info is required – Test data.
- Validation point/trigger/action: Why is the validation taking place? (Button, toggle, or link access clicks). In order to avoid data entry with nothing to look for, make sure a test case has at least one validation point. Additionally, avoid putting too many validation points into a single test case to guarantee that we have adequate modularity. The ideal number is one per test scenario.)
- Output: Expected result.
- Postcondition: In order to make the test case more incisive and instructive, this extra information is included for the tester’s benefit. This comprises a description of what occurs or what the AUT should do after completing each test case step.
See Also => Sample Test Case Template
Live Project Sample Test Cases (Download)
Let’s get started and develop a few test cases for our live project now that we have sufficient background knowledge to begin the process.
We have developed a few sample test cases for the OrangeHRM account module based on the previously described procedure.These need to provide you with a precise format for test cases as well as guidance on how to write them.
=> Download Sample Test Cases Document for our Live Project here.
Note: There are few images referred to sample test cases XLS document. If you are viewing this on the older MS Office version, you may face compatibility issues.
Test Cases Writing/Optimization Methods
Consider a scenario where a certain page contains tens of fields or intricate business logic that is implemented there. We testers have certain test case optimization techniques to ensure that we maximize the test case creation process in such circumstances.
Enlisted below are the links that are provided for more information on these methods.
- Error Guessing – This is a straightforward technique that depends on the tester’s instincts.Let’s take an example where a page has a date field. The criteria will indicate that this field must accept a valid date. As far as the numbers are concerned, a tester can try entering “Feb 30” as the date; however, February is a month that never has 30 days, so this is an invalid input.
Using the above techniques and following the general test case creation process, we create a set of test cases that would effectively test the application on hand.
Few Important Points To Be Noted
- The test cases we create are not only the point of reference for the QA phase but also to the UAT.
- Internally test cases are Peer-reviewed within the team.
- When a certain situation is not addressed by a test case – the rule of thumb is, it is not going to get tested. So, this is a good place to check whether the test suite we created achieves the 100% test coverage goal or not. To do so, a traceability matrix can be created. Check out all there is to know about the Traceability matrix here.
- Tools – Test management tools like QC, qTest help us with the test case creation activity. For an example of how test cases can be dealt with using Quality Center, check out this Quality Center tutorial.
- Test cases can be created using automation technologies; in this instance, they are known as Scripts for tests.
Pro Tip: Please perform a spell and grammar check on each and every document we create. We are the quality representatives for IT projects – and it doesn’t reflect positively on us if our deliverables themselves are of inferior quality.
That brings us to the finish of another interesting segment.
Conclusion
The test preparation phase will typically come to an end and the test execution phase will commence with the conclusion of the test creation process/test design phase (STLC) and the completion of the code phase (SDLC).
YOU MAY BE INTERESTED IN
The Art of Software Testing: Beyond the Basics
Automation testing course in Pune
