In this post we will discuss about my experience while attending Capgemini Interview for Manual testing. Also you can check out my previous posts on:
- Honeywell testing interview questions
-
-
1. What are the types of Priority and Severity?
"Priority" of a bug means how fast it has to be fixed. Most of the time "High Severity" bug are marked as “High Priority” bugs and also it should be resolved as early as possible.The Priority status of a bug is set by the tester to the developer mentioning the time frame to fix a defect. If priority of a bug is "high" then the development team has to fix it at the earliest.
"Severity" means how severe it is affecting the functionality of an application.It says how bad the bug is for the system. Severity type is defined by the tester based on the written testcases and functionality.Based on the seriousness of the bug severity is assigned to defect.
2. What is Log sheet and what are the components in it?
A log sheet is a defect report in which we are attaching server logs,behavior of the application,request and response of the remote server when the defect has occurred .A log sheet is a very useful document for the developers while replicating a defect for fixing.Log sheet also consists of lines of code according to the series of events that made the defect to occur.
3. Give some example for high severity and low priority defect?
The download Quarterly statement is not generating correctly from the website & user is already entered in quarter in last month. So we can say such bugs as High Severity, this is bugs occurring while generating quarterly report. We have time to fix the bug as report is generated at the end of the quarter so priority to fix the bug is Low.
System is crashing in the one of the corner scenario, it is impacting major functionality of system so the Severity of the defect is high but as it is corner scenario so many of the user not seeing this page we can mark it as Low Priority by project manager since many other important bugs are likely to fix before doing high priority bugs because high priority bugs are can be visible to client or end user first.
4. In an application currently in production, one module of code is being modified. Is it necessary to re-test the whole application or is it enough to just test functionality associated with that module?
Answer to this ,You will have to test the functionality of that module as well as the other modules. But you can differentiate on the stress to be given on the module to be tested.
Ex: If Module A is modified, Module B is depending on module A, and Module C is a general module independent of module A.So in this case you will test the module A in depth to all test cases. Then your next stress will be on module B. Wait now what about module C? You will have to test this module as well but may be with less stress because module C is not depend on module A but may be depend on module B. Again if you are a white box tester you probably know which modules will get affected and which modules should be tested. But as a black box tester you will need to do regression testing as well.
5. What are you going to do if there is no Functional Spec or any documents related to the system and developer who wrote the code does not work in the company anymore, but you have system and need to test?
In this case fist you will need to do the exploratory testing of the product. In this testing you will come to know the system and its basic workflow. In exploratory testing you can also find some ‘blocker’ bugs that cause system to be crash.After that you can able to write test cases for this.Also you can prepare a query sheet and ask all the queries to the BA and developers.
- Honeywell testing interview questions
-
-
1. What are the types of Priority and Severity?
"Priority" of a bug means how fast it has to be fixed. Most of the time "High Severity" bug are marked as “High Priority” bugs and also it should be resolved as early as possible.The Priority status of a bug is set by the tester to the developer mentioning the time frame to fix a defect. If priority of a bug is "high" then the development team has to fix it at the earliest.
"Severity" means how severe it is affecting the functionality of an application.It says how bad the bug is for the system. Severity type is defined by the tester based on the written testcases and functionality.Based on the seriousness of the bug severity is assigned to defect.
2. What is Log sheet and what are the components in it?
A log sheet is a defect report in which we are attaching server logs,behavior of the application,request and response of the remote server when the defect has occurred .A log sheet is a very useful document for the developers while replicating a defect for fixing.Log sheet also consists of lines of code according to the series of events that made the defect to occur.
3. Give some example for high severity and low priority defect?
The download Quarterly statement is not generating correctly from the website & user is already entered in quarter in last month. So we can say such bugs as High Severity, this is bugs occurring while generating quarterly report. We have time to fix the bug as report is generated at the end of the quarter so priority to fix the bug is Low.
System is crashing in the one of the corner scenario, it is impacting major functionality of system so the Severity of the defect is high but as it is corner scenario so many of the user not seeing this page we can mark it as Low Priority by project manager since many other important bugs are likely to fix before doing high priority bugs because high priority bugs are can be visible to client or end user first.
4. In an application currently in production, one module of code is being modified. Is it necessary to re-test the whole application or is it enough to just test functionality associated with that module?
Answer to this ,You will have to test the functionality of that module as well as the other modules. But you can differentiate on the stress to be given on the module to be tested.
Ex: If Module A is modified, Module B is depending on module A, and Module C is a general module independent of module A.So in this case you will test the module A in depth to all test cases. Then your next stress will be on module B. Wait now what about module C? You will have to test this module as well but may be with less stress because module C is not depend on module A but may be depend on module B. Again if you are a white box tester you probably know which modules will get affected and which modules should be tested. But as a black box tester you will need to do regression testing as well.
5. What are you going to do if there is no Functional Spec or any documents related to the system and developer who wrote the code does not work in the company anymore, but you have system and need to test?
In this case fist you will need to do the exploratory testing of the product. In this testing you will come to know the system and its basic workflow. In exploratory testing you can also find some ‘blocker’ bugs that cause system to be crash.After that you can able to write test cases for this.Also you can prepare a query sheet and ask all the queries to the BA and developers.
