31.What Will You Do When A Bug Turns Up During Testing?
When a bug shows up, we can follow the below steps.
- Run more tests to make sure that the problem has a clear description.
- Run a few more tests to ensure that the same problem doesn’t exist with different inputs.
- Once we are sure of the full scope of the bug, then we can add details and report it.
32.How Comes The Severity And Priority Relate To Each Other?
- Severity –Represents the gravity/depth of the bug.
- Priority –Specifies which bug should get fixed first.
- Severity –Describes the application point of view.
- Priority –Defines the user’s point of view.
33.What is risk-based testing?
Risk-based testing is the term used for an approach to creating Test Strategy that is based on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first.
34.Give an example of Low priority-Low severity, Low priority-High severity, High priority-Low severity, High priority-High severity defects.
- Low priority-Low severity– A spelling mistake in a page not frequently navigated by users.
- Low priority-High severity– Application crashing in some very corner case.
- High priority-Low severity – Slight change in logo color or spelling mistake in company name.
- High priority-High severity – Issue with login functionality.
35.What are the phases of a formal review ?
In contrast to informal reviews, formal reviews follow a formal process. A typical formal review process consists of six main steps:
- Review meeting
Weekend / Weekday Batch
36.When do we prepare RTM (Requirement traceability matrix), is it before test case designing or after test case designing?
The would be before. Requirements should already be traceable from Review activities since you should have traceability in the Test Plan already. This question also would depend on the organisation. If the organisation do test after development started then requirements must be already traceable to their source. To make life simpler use a tool to manage requirements.
37.What Are Different Types Of Severity?
The severity of a bug can be low, medium or high depending on the context.
- User Interface Defect – Low
- Boundary Related Defects – Medium
- Error Handling Defects – Medium
- Calculation Defects – High
- Misinterpreted Data – High
- Hardware Failures – High
- Compatibility Issues – High
- Control Flow Defects – High
- Load Conditions (Memory leakages under load testing) – High
38.What Should Be Done After A Bug Is Found?
After finding the bug the first step is bug to be locked in bug report. Then this bug needs to be communicated and assigned to developers that can fix it. After the bug is fixes by the developer, fixes should be re-tested, and determinations made regarding requirements for regression testing to check that fixes didn’t create problems elsewhere.
39.What Are The Advantages Of Waterfall Model?
The advantages of the waterfall model are:
•Simple to implement and required fewer amounts of resources.
•After every phase output is generate.
•Help in methods of analysis, design, coding, testing and maintenance.
•Preferred in projects where quality is more important than schedule and cost.
•Systematic and sequential model.
•Proper documentation of the projec
39.What Is Rapid Application Development Model (rad)?
The RAD model Rapid Application development (RAD) is incremental software development process models that focus on the development of the project in very short time. It is enhanced version of Waterfall model. It is proposed when requirements and solutions can be made independently system or software components, which is developed by different teams. After these smaller system components are developed, they are integrated to produce the large software system solution.
40.What Is Exploratory Testing?
Exploratory testing: means testing an application without a test plan and test script. In exploring testing test explore the application on the basis on his knowledge. The tester has no knowledge about the application previously. He explores the application like an end user and try to use it. While using the application his main motive is to find the bugs which are in the application.