1. Who will change the status of bug?
As soon as tester finds a bug he logs the bug as new status and assigns to developer. Developer working on that bug changes the status as open. When developers feels its not required fixing at that moment he changes the status as differed. If he completed working on that he changes the status as close and assigns the report to tester. Tester retests the bug and confirms the status as close. We come across many more statuses such as duplicate, not reproducible, to be fixed, critical, blocked, need clarification. We can use the status according to the bug.
2. Is it possible to have a defect with high severity and low priority or vice verse?
When the development team prepared the modules and they sent it for testing and after doing some part of testing then a bug raised in the first module its severity is minor and at the same time in the second module a bug raised and its severity is major. We come to know by the next day the client is coming for inspection and he wanted to get the first module prepared. So at this time less severity bug gets high priority and high severity bug gets low priority.
3. What is defect life cycle in manual testing?
Defect Life Cycle: Defect detection
Reproduce the defects
Assign the bug to the developer
Bug fixing
Bug resolution
Regression
4. What is difference between bug resolution meeting and bug review committee? Who are the participants in bug resolution meeting and bug review committee?
Bug Resolution meeting: It is conducted in presence of test lead and developers where developer gives his comment whether to correct the bug at this time or later and test leader accepts or rejects developer comments and even they decide what methods should be chosen correct the error so that in regression test no bug should be reported and it should not effect other application.
Bug Review committee: It is often conducted by test lead, project managers in the presence of client, where they decide as to what errors should be considered as bugs and what severity level it should be treated as.
5. How to give bug title and bug description for ODD devision?
Assumption: ODD number devision fails
Bug Title: ODD number fails
Bug Description: Open calculated window
Enter an ODD number
Click divide by [/] button
Enter another Odd number
Enter or click equal button in calculated window
Observe the result
Expected results:
Quotient displayed is correct
Actual result
Quotient displayed is incorrect.
6. What is build interval period?
In some companies builds are delivered from development team to the testing team to starts the system testing. For example a new product ABC is being released to the testing team so the development team will deliver a build to the testing team. Now testing will do the testing and then will release the product to the client. now there is a new version of product coming up with the name ABC1 and is being released to the testing team so this will be the second build and time between these two builds will be called as build interval.
7. What is difference between End to end testing and system testing?
End to End testing : This is the macro end of testing. This testing mimics the real life situations by interacting with real time data, network and hardware etc.
System Testing: this is the process of testing end to end business functionalities of the application(system) based on client business requirements.
In the system testing we are taking sample test data only, where as in the end to end testing we are taking real time data(for a sample) and interacting with network and hardware.,
8. How would you say that a bug is 100% fixed?
In quality world we cannot say bug is 100% fixed or 50% fixed. If the bug is fixed then in new version we do regression testing to make sure that bug fix doesn’t have any impact on old functionality.
9. How to post a bug?
Bugs are posted with the tools these tools are known as bug tracking tools. Custom designed tools, build specific for companies bug format, accepts the details of the issue from the testers as follows
1. Bug Id(tool generates the ID)
2. Bug description
3. Steps to reproduce the bug
4. Software and hardware environment
5. Status (New, reopen ….)
6. version Id of the build
7. Assign to
8. Severity
9. Priority
10. tester name and data execution
Test engineers fills the above fields in the tools and the tool acts as a central repository and tracks the entire bug life cycles.
10. What are the different types of bugs we normally see in any of the project?
1. User interface defects
2. Boundary related defects
3. Error handling defects
4. calculation defects
5. improper service levels
6. Interpreting data defects
7. race condition(comparability and inter system defects)
8. Load conditions (Memory leakages under load)
9. hardware failures
10. Source bugs
