"Are you planning to do testing without requirements? Is it possible to test software without requirements?
I can say, it’s pretty rare in QA testing services, but the situation can arise where we are expected to review without being given a functional specification document.
We will be unable to follow the standard testing practices without the testing documents.
Find below the real-time scenario for such a situation:
- A platform upgrade is required, with slight or no changes to the functionality. In such cases, requirements documentation is mostly ignored. Because for a reference, a system already exists.
Below are some of the challenges that you might face while testing the software without requirements:
- Difficult to prepare test cases.
- Not easy to train members
- Unable to track testing progress for a big team
But Don’t worry! these challenges cannot prevent testing from happening.
As part of the requirement gathering phase, the focus must be on identifying what to test?
Here’s what can be done before starting your test:
1. Know your team – It’s a good practice to be aware of the developers, business analysts, product owners, project managers, graphic designers, test module leads, and all your peers involved in the testing. It is more required when we are missing documentation as it will help you to reach out to the right person at the time of need.
2. Explore Other Artefacts – Functional or Software Requirements Specifications is just one of the several documents prepared during the software development phase. The availability of design documents is equally helpful, so check out if wireframes or mockups are available. Other useful resources can be business requirements, use cases, process flows, or technical documents.
Here, the team and testers have an idea of the scope, making a list of all critical components helps in planning resources and total effort.
So now, we will discuss some techniques that testers can use in case they do not have any software requirements specification.
1. Checklist for all the functionality– A checklist of identified components will work as the testing scope document. You can utilize the same for work allocation and tracking within the team.
2. Use Experience-based testers – This is the most valuable step in this overall process. Their experience not only counts for the total experience in this field but what matters most is the domain experience. Their knowledge will help in identifying the gaps in the built system, also assist in mentoring other team members.
3. Perform Exploratory testing – This testing is the most suitable for this type of requirement. The knowledge and experience help to identify the conditions in which the system may not work as expected and more stress is given on those areas of testing.
So, finally, we got the conclusion that even though having no documents creates a challenge, it can also occasionally work as an advantage.