QA testing professionals will come across various scenarios in day to day life, some of them can be tough to cope up with, while some issues can be handled with years of expertise. Software quality assurance and testing are very critical in nature and requires eye to detail.
Let us take a scenario, where there is no Functional Spec or documents related to the system is available. Further to add misery, you come to know that the developer who wrote the code is no longer working with the company, but you have the system and need to test.
Well, sometimes QA testing experts face such situations when they need to perform “Testing in the Dark” means there is no Functional Spec or document related to the application. But testing without information of the requirements is same like placing the cart before the horse. In such cases performing exploratory testing is one of the best process to go further. While performing exploratory testing tester should understand the application by spending some time, carry out a detailed study of the application, poke the areas which they think are more sensitive and bug prone and then make out a list of features and functionalities that are critical and note down the possible testable scenarios.
Whenever such condition occurs, the testers should do the best to manage the entire testing process efficiently and effectively. Personal experience and instinct plays a very important role to find issues as well as to hit the application hard. One should also use their prior Knowledge gained from previous projects and also follow metrics from previous similar projects which could be beneficial. There are also other techniques like black box testing, Blind testing, Adhoc testing and error guessing. One can take help of experienced person in that domain.
Testing of a system which do not contain any specifications or documents, you would only observe what a developer want you to observe and not from the customer perspective.
In such case, prior to system testing, first of all we should ask few questions to ourselves.
1) What type of testing is required on the system-unit /functional /performance /regression etc.
2) Is it new project or coming for maintenance?
3) Is the application is on Staging or Production?
4) Is there any domain expert available?
5) Is there is any business expert available?
6) Is any end user available?
7) Are there any known high risk areas?
8) Is manual or automation testing is required for testing?
All these questions would help us to identify the main key areas of testing and ignorable areas of testing. Once you get to know the key areas then you can start with following testing approach.
Being a Software quality assurance and testing professional, the first step would be to understand the application, to understand its functionality and outcomes. So what we should try is “Focused Exploratory testing”- to identify every section in the application or system and identify the functionality of the application.
One of the best option we have Smoke Testing to make sure that there is no blocking issue in the system and since it only to certify the piece or build.
“Monkey testing “would also be helpful, as it is all about Adhoc testing or negative testing, to identify the break point of the application and threshold limit of the application.
Well, sometimes QA testing experts face such situations when they need to perform “Testing in the Dark” means there is no Functional Spec or document related to the application. Software quality assurance and testing are very critical in nature and requires eye to detail.
Knowledge Sharing Team at QA InfoTech is responsible for research on new tools & technologies for effective software quality assurance and testing services across all industry verticals. QA InfoTech (an ISO 9001:2008 & CMMI III certified) is one of the leading Outsourced Software Testing Companies with five testing “Centers of Excellence” in the United States and India. It offers end to end QA testing services.