| |
71. What Are Different Categories Of Risks?
Date Posted: 06/27/2012
Ans:
Technology risks
Technology risks generally lead to failure of functionality and performance of the product. Some examples of technology risks are
Continuous changing requirements
Outdates or insufficient hardware exists for running new software products.
Early adoption of new technology
Resources risks
Human resources risks can involve staff changes and a lack of skilled resources. Some examples of resources risks are
Team turnover near the release date may affect the detailed testing of the project.
Failure to resolve the responsibilities may overlap responsibilities
No proper communication between team members.
Schedule risks
Schedule risks impact the project schedule and may lead to project failure if they are not addressed properly, some examples of schedule risks are
Failure to identify complex functionalities and time required to develop those functionalities
Unexpected project scope expectations
External risks
These are risks beyond the direct control of the project team caused by the external environmental or industry factors.
Some examples of external risks are
Potential regulatory changes
Potential economic changes
Potential company mergers
|
| |
| |
72. How Big Is Your Project?
Date Posted: 06/27/2012
Ans: here the interviewer was asking for the size of your project. Answer could be something like around 200 MB. If you answer 300 MB also interviewer cannot infer anything out of it. He asked this just to check whether your project is very small or considerably large.
|
| |
| |
73. What Is API Testing?
Date Posted: 06/27/2012
Ans: API testing is mostly used for the system which has a collection of API that needs to be tested. The system could be system software, application software or libraries. API testing is different from other testing types as GUI is rarely involved in API testing. Even if GUI is not involved in API testing, you still need to set up the initial environment, invoke API with the required set of parameters and then finally analyze the results.
|
| |
| |
74. What Are The Limitations Of Automation?
Date Posted: 06/27/2012
Ans: The various limitations of automation testing are:
We cannot automate everything. Ex: look and feel, multimedia, etc.
It is no useful for small projects since the cost of the tools for automation may cross the actual cost of the project.
Specialized skill is essential for planning automation Ex: Designing automation framework.
Highly skilled resources are required for developing test automation scripts.
|
| |
| |
75. You Have Good Logical Skills And You Are Suitable For Development Position We Have At Present. Are You Interested?
Date Posted: 06/27/2012
Ans: Thank you for the confidence you have showed in me and also for the opportunity given. I have spent enough time on testing and I am sure I am a good asset to the organization in the field of testing considering my interest and expertise.
|
| |
| |
76. I Want To Conduct The Complete Security Testing Of My Web Based Application. Do You Think You Can Handle This?
Date Posted: 06/27/2012
Ans: I have a very strong intension to learn new areas and I am sure security testing is one of the very challenging areas. Before I want to share my opinion, I want to understand more about the domain of the web based application. If it is a general web based application like chatting, social networking, emailing etc, I am ready to take up the challenges and complete the same successful to my level best. If it is a financial related application like banking application, I would suggest giving this responsibility to experienced security testers, who exclusively focus on security testing. I would be glad to participate with them to learn and contribute from my side.
|
| |
| |
77. You Have Tested The Application And It Is Released. The Customer Asks For Some Changes In The Projec
Date Posted: 06/27/2012
Ans: In this situation I will prefer to consult the customer and request him to extend the date of release for another 1 week, for thorough testing and fixing the defects that are found, so that a quality product can be released.
If the customer doesn’t agree I will prioritize and test major functionalities. In case there are critical defects found in major functionalities I would recommend to extend the release date, since releasing a quality product is also as important as releasing the product on time.
|
| |
| |
78. How Long Will The Maintenance Phase Will Be There?
Date Posted: 06/27/2012
Ans: Usually maintenance phase will be 8-10 times of the development duration. This means if project is developed for 1year, it will be maintained for 10 years approximately.
|
| |
| |
79. What Will You Ensure Before Raising The Bug?
Date Posted: 06/27/2012
Ans: I will closely test all the scenarios related to the area of the bug identified and consolidate the exact steps and test data required to produce this bug. I will also analyze the impact of this bug on product functionality, to determine the severity of the bug.
|
| |
| |
80. Your Manager Feels The V-model Is Vast And Unnecessary Because It Has Lots Of Documentation Involved.Do You Agree?
Date Posted: 06/27/2012
Ans: My manger is very experience and he will not come out with such opinion until there is a strong reason behind it. I agree with him incase project is small and water flow model is sufficient to develop this project. Incase project of large and has a frozen requirements, I would share my opinion with my manager stating that b-model has strong integration with each phase of development and it gives very early focus on the testing activities of the project. Hence the quality of product developed using v-model is always good.
|
| |
