Manual Interview

1. What is meant by Priority and severity? 

Ans: Severity defines the seriousness of defect and priority define how early the defect should be fixed.

Severity: 
a. This is assigned by the Test Engineer
b. This is to say how badly the deviation that is occurring is affecting the other modules of the build or release. 

Priority: 

1. This is assigned by the Developer. 

2. This is to say how soon the bug as to be fixed in the main code, so that it pass the basic requirement. Ex: The code is to generate some values with some valid input conditions. The priority will be assigned so based on the following conditions: a. It is not accepting any value b. It is accepting value but output is in non-defined format (say Unicode Characters).

2. Give me some example for low severity and high priority defect? 

Ans: 

a. If the company name is misspelled in the home page of the website,then the priority is high and severity is low to fix it. Beacuse wrong company name doesn't impact the functionality of the application hence the severity is low and but the same defect should be fixed as early as possible since we are loosing company's brand value hence the priority is high.

b. Suppose in one banking application there is one module ATM Facility. In that ATM facility when ever we are depositing/withdrawing money it is not showing any conformation message but actually at the back end it is happening properly without any mistake means only missing of message, in this case as it is happening properly so there is nothing wrong with the application but as end user is not getting any conformation message so he/she will be Confuse for this. So we can consider this issue as HIGH Priority but LOW Severity defects…

2. Give me some example for high severity and low priority defect? 

Ans: Suppose we have banking application which calculate Yearly, Monthly and Weekly interest. But we have error in Yearly calculation then we can say it as HIGH SEVERIRTY and LOW priority because we can fix it in next week also no problem.

3. Difference between Test Strategy vs Test Plan

Test Plan	Test Strategy
Defined at project level	Defined at organizational level
Contains plans for all test related activities	It is high level documents that capture the approach in testing
Test plan can change frequently	Test strategy does not change that often
Test plan is about specification	Narrates a general approach and vision of the company
Derived from product specifications, use cases and SRS	Derived from BRS
For small companies strategy is a part of test plan	For big organization test strategy is defined separately and test plan is derived from it
Test plan is carried out by a testing manager or lead that describes how to test, when to test, who will test and what to test	A test strategy is carried out by the project manager. It says what type of technique to follow and which module to test
Components of Test plan include- Test plan id, features to be tested, test techniques, testing tasks, features pass or fail criteria, test deliverables, responsibilities, and schedule, etc.	Scope, overall approach, tools, reporting method, environment metrics etc . It is a set of guidelines that explains test design and determines how testing needs to be done