This is the subsequent lesson in our ‘online Software Testing training on a real-world project’ succession. If you’re new to our platform, you might want to go through the introductory tutorial: Full Software Testing Training on a Real-World Project.
In this tutorial, we delve into an all-inclusive study of how to perform an SRS evaluation, the steps we must initiate before embarking on this journey, factors we should be aware of in this process, and much more. Let’s dive into the specifics.
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 )
Stage of Design in Software Development Life Cycle:
The subsequent stage in the SDLC is the ‘Design’ phase, during which the functional stipulations are converted into technical details. This process encompasses the development, design, environment, and data teams. A Technical Design Document (TDD) is generally the outcome of this step.
Both the conception of the TDD and the kickoff of the QA team’s involvement in the QA facet of the project, which includes reviewing the SRS document and discerning the test goal, utilize the SRS document as a basis.
Table of Contents:
What Does an SRS Review Entail?
The SRS is a paperwork constructed by the development team in partnership with Business Analysts and environment/data teams. Once finalized, it is concurrently presented to the QA team through a meeting in which an exhaustive walkthrough is conducted.
For an established application, a formal get-together might not be required. We could independently scrutinize the document, given adequate information.
The SRS review comprises of perusing the functional requirements specification document and comprehending the essence of the prospective application.
The format might fluctuate, as the emphasis is on substance over form.
Different teams adopt different strategies, some prefer bullet points, others incorporate use cases or sample snapshots. Some may supply comprehensive explanations in paragraphs.
Prerequisites to Software Requirements Specification Review
Step #1) Verify that you have the latest version of the cited document, the SRS, as such documents frequently undergo multiple revisions.
Step #2) Outline protocols for the anticipated outcomes of the inspection from each team player. Identify the deliverables, which typically compose the identification of test scenarios. These scenarios are concise indicators of what requires testing for a particular functionality.
Step #3) Formulate guidelines for presenting these deliverables, which might include the template to use.
Step #4) Decide if team members will probe the whole document or distribute it amongst themselves. Recommending that everyone reviews the complete document will minimize knowledge concentration among particular team individuals.
For large-scale ventures with SRS documents spanning hundreds of pages, it is practical to assign parts to individual team delegates.
Step #5) SRS review equally aids in identifying any specific prerequisites required for software testing.
Step #6) Consequently, queries can be raised and addressed regarding the struggle in understanding specific functionality, additional details that require incorporating into the requirements, or identified discrepancies in the SRS.
Is a Template Necessary for Test Scenarios?
What is the need for using a template for test scenarios? Why can’t we just make a list?
Creating a list can suffice. However, software projects demand collaboration.
Suppose we have a team of four. Each member examines a designated module of the software requirements specification. Member A makes a list on paper, Member B uses an Excel spreadsheet, Member C uses a notepad, and Member D uses a Word document. How can all these contribution consolidations be achieved at the end of the day?
In addition, how can we set a standard and decide what is right or what is wrong without outlining the guidelines?
A template provides guidelines and a uniform format for consistency across the entire team.
Is there a way to create a template for QA Test Scenarios?
Templates need not be intricate or rigid.
They simply facilitate the creation of beneficial testing documents. Here is an elementary illustration:
The template header includes basic project details, the current document, and the referenced document.
The table enables the creation of Test Scenarios with the subsequent columns:
Column #1) Test Scenario ID
Each test scenario should be uniquely identifiable. Allocate an ID to each test scenario according to specific criteria. For example, “TS_MI_MIM_01” represents a Test Scenario for the My Info Module (MI) subsection including My Info Module (MIM) with a serial number of 01.
Column #2) Requirement
Link each test scenario with the corresponding section or page number in the SRS document for a clear source of the requirement.
Column #3) Test Scenario description
A succinct statement indicating what part needs testing, also denoted as the test objective.
Column #4) Importance
Highlight the significance of each functionality for the application undergoing testing. Use terms such as high, medium, or low, or a points system. Define this field’s values beforehand.
Column #5) No. of Test cases
Estimate the tally of test cases linked with each test scenario. For instance, testing the login operation may involve valid username and password, valid username and invalid password, and invalid username and valid password, causing a count of three test cases.
Important: Personalize the template as needed, adding or removing fields to fit your team’s needs.
For instance, you can include a “Reviewed by” field in the header or omit the creation date. In the table, you can include a “Created by” field to assign responsibility for a test scenario or omit the “No. of Test cases” column. Tweak the template to best serve your team’s needs.
Now let’s examine our Orange HRM SRS Document and generate the Test Scenarios
Section 1 elucidates the document’s purpose but does not consist of testable requirements.
Section 2.1: Project Summary – Audience – equally does not comprise testable requirements.
Section 2.2: Hardware and Hosting – While this section discusses the hosting of the Orange HRM site, its relevance for testers may vary. Having a similar testing environment to the actual environment is crucial, but it is not a testable prerequisite. It can be noted as a prerequisite for testing.
Section 3: This portion outlines a login screen and required account specifics to access the site. These are testable requirements and should be encapsulated in our Test Scenarios.
Please refer to the document of test scenarios where scenarios for several parts of the SRS have been incorporated. For practice, you could add the remaining scenarios in the same way. Alternatively, you can proceed directly to section 4 of the document.
Section 4: Aesthetic/HTML Requirements and Guidelines – This section stipulates that certain requirements may not be decipherable to the test team during the SRS review, but should still be noted as testable requirements. The particulars of how to test them and whether specific arrangements or assistance are required may not be known at this stage, but their inclusion in the testing scope is essential to prevent oversight.
Sample Test Scenarios for OrangeHRM Application: (click to enlarge image)
=> For additional information, please download and refer to the Test Scenarios document.
Crucial Considerations Regarding SRS Review
#1) Make sure to address all available information.
#2) Implement a feasibility study to confirm the accuracy and testability of requirements.
#3) Unless there are separate specialized test teams for performance/security, consider all non-functional requirements.
#4) Distinguish that not all information is pertinent to testers and concentrate on relevant facts.
#5) The allocated importance and the number of test cases don’t have to be exact and can be approximations or left blank.
In conclusion, an SRS review culminates in:
- A series of Test Scenarios
- Review Results – Errors found in the Document/Requirement during a static review of the SRS document
- A register of Questions for clarification
- An initial comprehension of the necessary test environment
- Detection of the testing scope and estimation of the test cases count, which determines the required time for documentation and execution.
Key points to remember:
#1) Test scenarios are not meant for external delivery and are primarily for in-house QA consumption. They are the stepping stone towards attaining 100% test coverage. Once the test scenarios are complete, they undergo a coworkers’ review and then are combined.
For more insights on how QA documents are reviewed, refer to the post: A Breakdown of How to Conduct Test Documentation Reviews in 6 Straightforward Steps.
#2) Test management utilities like HP ALM or qTest can be deployed to create test scenarios. However, manually creating test scenarios is often more handy in the beginning stages. Simple Excel spreadsheets are sufficient for this aim.
In the next lesson in this series, we will craft test cases and further plunge into the test design phase. Before that, we will cover test planning and its contribution in the overall QA project. Continue this journey with us for optimal outcomes.
QA Training Day 3: How to construct an SRS document from scratch.
We encourage you to ask questions and share your thoughts. We greatly value your feedback!