Aspire Systems Interview Question
Testing / Quality AssurancesCountry: India
Interview Type: In-Person
How to test ? You mean black box testing ? then we can't do it without any clarity. If unit testing or any error based on form submission we can find out.
Hello Sageer
you are right . If we dont have any functional requirement then how can we test any application .. In this case we simply consult with the business analyst or any concerned person who is working in that application. So that we have the Idea about the Application.
Sometimes you may get the situation like you don't have enough time to test the application and you even dont have the requirement document . Then at that time you have to discuss with the persons who are working on that application.
Thanks a lot
Aditya
- In case of no requirements/ details available about the application, we can start analyzing the application functionalities and has to to ensure the correct functionality based on the domain.
-As any application is developed on certain domain, we can ensure the correctness of the functionalities based on the domain knowledge.
For example, in banking domain any banking application should follow the basic banking transactions......
I will also do the same as
- In case of no requirements/ details available about the application, we can start analyzing the application functionalities and has to to ensure the correct functionality based on the domain.
-As any application is developed on certain domain, we can ensure the correctness of the functionalities based on the domain knowledge.
I think best way to approach testing in such cases is first to know what is it that has to be tested, someone asking to certify whole application to a new comer is difficult. Then once you know which part of the application has to be certified focus on that area, if you can get hold of some experienced in that are then consult him. Get SVN / perforce / source code link go through to get an a idea of flow.
Finally most important part is since you don't know about application and you are signing off on it, you should attach all the scenarios tested along with certification communication.
If there is no Requirement document OR
Requirement is there but not understandable OR
There is no time to read the Requirement document .....
In all these condition's i will do EXPLORATORY TESTING.That is knowing and testing the applications.we should Explore the application,try to understand the application and based on understanding come with scenarios and then write the test case......
TO UNDERSTAND THE APPLICATION I WILL DO FOLLOWING THINGS......
I will put my previous domain knowledge.
If i get a chance,i will talk to costumer.
I will talk to BA and DEV.
while testing such application where there is no requirement document possible approaches are as follows.
1) Ask Dev team for demo for application flow or general overview of application.
2) Test the golden path( major flow of the application)
3) Perform Adhoc testing to become aware of application flow or integrations.
4) Note down the observations while testing while scenario and consult dev team to check the observations.
In this case, I went to the Business Analyst and some times to developers to find out how exactly the functionalities work, how to navigate from one page to another page and so on. After getting a clear vision, I write test cases based on the conversation (which is a step by step procedure to test an application) and get ready for testing.
- Aditya June 09, 2012