• info@helpingtesters.com
  • helpingtesters

SUBSCRIBE TO OUR NEWSLATER





Testing without Requirements

December 15, 2017
testing without requirements, no requirements to test, challenges when there is no requirement to test

Testing is an art which is followed to improve the product quality. Every Software is developed and tested based on the requirement. But the task becomes more challenging when the testers have to perform the testing without requirements. The STLC process has helped the tester performing the testing in a very fluent and sophisticated manner, But Have we ever thought of the situation if there is no Requirement available for the project? Then How to continue with the testing process? What exactly to be tested? What type of testing to be done? and so on.

All this general question arise in the mind of the tester. In this article, we are going to discuss some important points regarding the testing process when there is no Requirement Specification available for testing.

Challenges faced while performing testing without Requirements

  • It is a challenging job creating the test design, test plan and test cases of the project without the requirement document and thus makes a tough job to know the testing scope.
  • It creates a problem in the project where there are continuous releases as the old released information is not documented. Thus creating an understanding gap that how the existing functionality of the previous release behaves with the new ones.
  • Tester is also not aware of the OS specification, Browser compatibility or Device support which is in-scope of the project.
  • When we are testing the requirement, then we have the view that exactly how the application will look after completion, but in this cases, we can have only the initial level approach.
  • In this case, there is no scope to update the document and hence create a lot of problem to the tester exactly what to be followed.
  • For this type of scenario, the managers and developers are the only source of information, which can be misunderstood or get frequent changes affecting the system and make it unstable and difficult to test.
  • There is a greater chance of testing Incomplete development task as the developer does not have any document to follow.
  • Lack of testing process which is generally followed while performing the testing.
  • There is a greater chance of defect Reopen as the requirement can be misunderstood from either end (developer and tester).
  • It is better to divide the task into small modules and understand each of them thoroughly. And then perform testing of each of the modules to maximize the test coverage.

So, the very next thing which arises in my mind is “ How are we going to test such projects with no requirement”. So, here are some of the points which should be followed in general while testing without requirements in any of the projects.

  • Communication between the team plays a very important role. As we all know that communication is the key to success, so there should be continuous communication and discussion with the developers, stalk holder, team leads and manager in very steps while performing the testing.
  • There should be proper documentation of what to be tested and detailed about the flow. This will not only help to understand the testing approach but will also making the testing easier.
  • As there is no formal document, we need to perform smoke or random testing of the application and report whatever we feel is wrong and get it fixed by the developer.
  • We should emphasize more on the document provided by the developers or the project managers and can prepare the test cases. Once done we can get it reviewed by the developer or manager. This will not only confirm our understanding regarding the project functionality or requirement but will also help in testing.
  • The testing should be performed from a user perspective. Thinking how the end user will use the application and try to find the loopholes.
  • In case of any confusion, try to make it clear as soon as possible. Involve the whole team including the developer, manager, business analyst, etc.
  • We should give more emphasis on the basic functionalities and features like- Application launch, Browser dependencies, Label, and text are spelled correctly, Page redirection and the link works fine, a Proper error message displayed and field validation, Controls like-menu, toolbar button should work properly, UI alignment and many more.
  • We should have the detailed knowledge of the technical modules developed by the developer.For this type of scenario, we need experience testers who can think out of the box and can tackle this type of projects.
  • If any older/existing version of the software exists, then it should be followed thoroughly by performing the testing. Or else Exploratory testing to be followed by the testers.

Last but not the list, Testing without Requirements is really a challenging job for the tester as well as for the development team. There should be at least some basic requirement for all project based on which it should be built. If not so, then there should at least be a Business requirement document for understanding the business requirement.

I have been in software testing for a decade. Maintaining HelpingTesters.com website to make a common platform to share my knowledge with everyone or where others can share to help out other testers. If you are willing to help than let me know at info@HelpingTesters.com

About the author

HelpingTestersTeam administrator

I have been in software testing for a decade. Maintaining HelpingTesters.com website to make a common platform to share my knowledge with everyone or where others can share to help out other testers. If you are willing to help than let me know at info@HelpingTesters.com

Leave a Reply

Your email address will not be published.