blogs

How to deal with bad Requirements of Software being a Testing Engineer

How to deal with bad Requirements of Software being a Testing Engineer 16 May,2016

Being a Software Testing Engineer, we often meet a situation where the requirements are not good enough to complete the flow of any process.

Let me discuss a recent incident of my current project in which we are working on the last Sprint and we got a bug in notification module which was a requirement of the third last sprint.

The project is an application for booking taxi with administration support. The notification for the driver approval has to be sent to the client as well as administration of the app.

But currently it is sending notifications to client only and when testing team has submitted a bug ticket to development team then developer acknowledged this bug to the tester, with comment “it is as per client’s requirements”. But in current sprint the client is demanding for the notification to the administration.

So, in this situation we have to perform regression testing on the last three builds. This is an example of bad requirements of software product. In which there is blocker or may be a tweak in completing the flow of the process.

We have discussed an example of bad requirement; Let us now discuss how to handle bad requirements. The Software Development Life Cycle (SDLC) starts from requirement gathering and analysis of the requirements.

Now for a requirement it depends, how a client has asked for it, how the project leader got it, how the BA understood it, how a designer analyzed it, how a developer wrote code for it and how a tester receive it.

reporting-requirements

After gathering requirements, the very first thing to be done is requirement analysis. Before freezing all the requirements, client’s requirements have to analyze whether these requirements are feasible or not.

There technical feasibility and cost feasibility both should be consider while freezing the requirements. Based on these requirements BA should prepare use cases and wireframes to draw the flow of the process involved in the completion of the software product.

These documents should be sent to the client for approval; if client approves or asks for any change then these changes should be considered. The finally approved documents by client should be sent to development and QA team.

Quality analyst then analyzes the wireframes and docs approved by client.

If a QA gets a bad requirement then an immediate call (voice or video) should be made to the client in presence of BA to raise the alarm for that bad requirement.

A scrum meeting can also be made depending on the process what an organization is following. If client approves that requirement as final then requirements should be freeze and should be handled with extra care after receiving the Software builds.

There are kind of requirements which are specified by client to be changed later in the project, these requirement are counted as CRs and should be analyzed properly.

Above discussion on requirements (Good or bad) come to the conclusion that before freezing requirements a complete analysis is mandatory both by BA and QA team.

Based on these requirements wireframes, flow chart, use case, test cases and checklist should be prepared to filter out the bad requirements. Always remember, a bad or poorly analyzed requirement can block the road for a good Software Product.

Save

Rahul Gupta Rahul Gupta works as Senior Software test engineer at BugRaptors.He is responsible for Manual testing on Web and Mobile application. He is expertise in Real Estate, Travel, eCommerce domains with good leading and project driven skills.

Your comment has been posted successfully!!

Leave a Reply

Your email address will not be published. Required fields are marked *

Name field is required !

12345 Rating field is required !

Related Posts

Efficient ways to implement smoke tests to authenticate goal...
How to deal with bad Requirements of Software being a Testing Engineer

Assume you have the big idea for a new product or its feature. Prior to investing loads of money and time into it, you need to authenticate it. In oth...

Read More
Efficient ideas to explore the types of requirements for tes...
How to deal with bad Requirements of Software being a Testing Engineer

Whenever we test an application, the main point in mind is to verify the requirements. But, we normally find the client providing feedback, even if al...

Read More
Effective Ways Followed By QA To Speed Up The Software Relea...
How to deal with bad Requirements of Software being a Testing Engineer

Software testing is a process of improving the quality of developed software by finding bugs during the whole software application development phase. ...

Read More
Introduction to Testing in Production & Tips to do it the Ri...
How to deal with bad Requirements of Software being a Testing Engineer

Testing in production (TiP) can be described as the process of performing several types of software tests in a production environment where it is acce...

Read More

Popular Blogs

What Is ETL Testing & How To Enforce It In Data Warehouse?
What Is ETL Testing & How To Enforce It In Data Warehouse? Read More
How to test your Android App: Key Techniques to get you started
How to test your Android App: Key Techniques to get you started Read More
Boost your business using Test Automation
Boost your business using Test Automation Read More
3 Reasons Why to Invest Time and Money in Regression Testing!!
3 Reasons Why to Invest Time and Money in Regression Testing!! Read More
Measure Performance of the Application – Using Open Source Performance Testing Tools
Measure Performance of the Application – Using Open Source Performance Testing Tools Read More

Sign up FOR NEWSLETTER !

Is your application fully functional? Write us to know.
contact us