Generating Test Cases from the SRS Document (Sample Test Cases for Live Project DOWNLOAD) – Day 4 of Software Testing QA Training
Let’s take a quick look back at where we’re at – we’re advancing through the Training for Software Testing short course focusing on a live project named OrangeHRM.
Recommended IPTV Service Providers
- IPTVGREAT – Rating 4.8/5 ( 600+ Reviews )
- IPTVRESALE – Rating 5/5 ( 200+ Reviews )
- IPTVGANG – Rating 4.7/5 ( 1200+ Reviews )
- IPTVUNLOCK – Rating 5/5 ( 65 Reviews )
- IPTVFOLLOW -Rating 5/5 ( 48 Reviews )
- IPTVTOPS – Rating 5/5 ( 43 Reviews )
In this complimentary online QA training sequence, we’ve gone through the following:
- Analyzed the SRS document
- Pinpointed Test Scenarios/Test Scope
- Recorded the Test Plan
Now, it’s time to delve into the core section – the test cases.
As discussed in the previous write-up: The QA team constructs the test cases during the Code phase of the SDLC. In simpler terms, while the Development team is building the software system, the testing team constructs the test cases to be employed for system testing once it’s complete, that is, post the coding phase.
Consequently, in this article, we will aim to comprehend what test cases constitute, the process of creating them, and also construct a few sample test cases for our current live project.
Let’s get the ball rolling straight away.
The Learning Outcomes:
Basics Of Creating Test Cases
#1) If Test Scenarios delineate “What is to be tested” about the AUT (Application Under Test) – the test cases explain “The method of testing a requirement”.
For Instance, if the test scenario is “Validating the Admin login functionality” – This would generate 3 test cases (or conditions) – Successful Login, Unsuccessful Login upon incorrect username entry, Unsuccessful Login when incorrect password is input. Each test case will contain guidelines to establish whether a specific test condition is fulfilled or not.
#2) The inputs required to produce a test case documentation comprise the FRD (Functional Requirements Document), test scenarios generated in the aforementioned step, and other ancillary documents.
#3) The test case documentation is a vital deliverable produced by the QA team and is circulated among Business Analysts, Project Managers, and other teams to get their inputs.
#4) The workload is apportioned among the team members, with every member assigned to construct test cases specific to each module or a segment of it.
#5) Similar to test scenarios, a unanimous format must be settled upon at the outset of test case documentation. Various formats such as MS Excel and MS Word can be used for formulating test cases.
#6) The MS Word template usually appears like this:
#7) The Excel template might resemble the following:
#8) Observing the above two templates, we can see that the components that constitute a test case are constant across both, the sole difference being the layout.
Therefore, provided each kind of information to be included in a test is represented by a field, the template format is irrelevant. However, the preferred format might vary from individual to individual, and MS Excel is commonly chosen due to its versatility and features.
Elements In Test Cases
Let’s take a moment to understand the components of a test case.
Test case Id and Test case description are the universal components.
The other components can be explained as follows:
- Precondition: The starting state of the AUT (Application Under Test) prior to the commencement of the test case.
- Input: The procedures for data input. For these procedures, it’s crucial to specify what kind of input is required – Test data.
- Validation point/trigger/action: What prompts the validation? (for instance, button or toggle click, link access). It’s important to have a minimum of one validation point per test case to confirm that the test case is not solely about data input. Furthermore, to maintain modularity, attempt to refrain from merging too many validation points into one test case (ideally, 1 validation point per test case).
- Output: The expected result or the outcome.
- Postcondition: This provides the tester with additional information making the test case more insightful and elaborate. It discloses what happens or what can be anticipated from the AUT once all the steps of the test case are executed.
Also See => Sample Test Case Format
Download Live Project Sample Test Cases
Having gathered sufficient introductory data to kickstart the construction of test cases, let’s go ahead and construct a few samples for our Live Project.
Aligning with the framework detailed above, we have formulated some sample test cases for the module of the OrangeHRM account. These will furnish you with the concise test case format and also provide some insights on how to go about constructing test cases.
=> Download the Sample Test Cases Document for our Live Project here.
Note: The sample test cases document comprises multiple images. If you use an outdated MS Office version, you might encounter compatibility issues.
Following are the names of the images referred to in the XLS files:
View Pic 1
View Pic 2
View Pic 3
And voila, that wraps it up.
Techniques For Optimizing Test Case Development
Now, let’s address a situation where a particular page contains numerous fields or involves intricate business logic. In order to streamline the test case creation in such scenarios, testers utilize multiple methods for test case optimization.
The links to learn additional information on these techniques are the following:
- Boundary Value Analysis
- Equivalence Partitioning
- Guesswork Errors – This technique relies on a tester’s intuition. For Instance, if there’s a date field on a page. The specifications mandate that a valid date should be accepted by this field. A tester can attempt entering “Feb 30” as a date – although numerically it appears as a seemingly valid input, February never consists of 30 days, hence, it’s an invalid input.
- Transition Diagrams for State
- Decision Tables
Applying the above techniques and adhering to the standard test case creation process, we can produce a set of test cases that effectively scrutinize the application.
Some Critical Points Worth Noting
- The test cases we construct serve as a source of reference not just for the QA phase but also for the User Acceptance Testing (UAT) phase.
- Within the team, test cases are peer-reviewed.
- Any scenario not included in a test case simply isn’t going to be tested. Hence, it’s vital to verify if the test suite we developed provides complete test coverage. This verification can be done by formulating a traceability matrix. Know all about the traceability matrix here.
- Test delivery tools like QC and qTest can assist test case creation. Observe this QC seminar to learn how test cases can be administered using Quality Center.
- Test cases can also be developed utilizing automation tools, where they are commonly known as test scripts.
That wraps up another engrossing segment.
The completion of the test case creation/test design process signifies the conclusion of the test preparation phase and the onset of the Test execution phase.
The next article in this Software Testing Course – In the succeeding article, we’ll talk about and comprehend Test Execution, its encompassing elements, and the expectations from the QA team during this phase.
We wish you’re keeping up with the series. For the sake of simplicity, we have formulated only a handful of test cases in the examples. However, optimal results are achieved when comprehensive testing is performed, implying the creation of additional test cases. Thus, don’t confine your work and formulate as many test cases as you can.
If there are any questions or remarks, feel free to voice them out below. Wishing you successful testing!