If there is no input document like SRS (System Requirement Specification) / BRD (Business Requirement Document) for testing a software, QA can have discussion with business analyst to identify the flow and major functionalities of the system.
As a tester, we can clarify the things with Business Analyst/Design Analyst/ Developer.
Also we can overcome this challenge, if there is any references like screen shots of the interfaces (which are going to develop) or wire frames, flow chart, Database structure and/or design documents.
Further previous experience of testing will work for overcome this challenge.
Exploratory testing is the best technique to overcome this problem. Exploratory testing means exploring, finding out about the software, what it does, what it doesn’t, what works, what doesn’t work. In this testing, it is constantly making decisions about what to test next and where to spent more time.
So, to overcome the challenges, testers can try above solutions.
If SRS or BRD is not available QAs can talk to the developers or business analyst to
- Get clarify things.
- Get a confirmation
- Clear the doubts
If there are any references like
- Screen shots
- Previous version of the application
- Wireframes
You can use them as testing references.
SMOKE testing is another best option. We identify the functionality and basic and major bugs from that.
Exploratory testing is also a good option. We can find what software does, and does not. The testers have make decisions on what to test next and where to spend more time.
If none of them work we can just test the application from our previous experience.
Comments
Post a Comment