1.Can u let me know the example of some defect that was identified in your project?
-Before that i found in payment option of menu items not showing recently updated payment.
-I also detected some specific windows are making delay in opening for intraday chart with smaller time frame.
2.What is severity?
A-Severity is the impact of defect on the customer business application.
2.1.High severity and high priority bug?
A-When a banking website is not showing the balance of an customer is an high priority and high severity bug.
2.2.High severity and low priority bug?
A-When we are generating the yearly statement of current year its showing error.
or Customer is not able to purchase product by using old browser.
2.3.Low severity and high priority bug?
A-Spelling mistake on home page
or Company logo is not displaying.
2.4 Different types of severity?
Critical-The defect affects critical functionality or critical data. It does not have a workaround. Example: Unsuccessful installation, complete failure of a feature.
Blocker-The defect affects major functionality or major data. It has a workaround but is not obvious and is difficult. Example: A feature is not functional from one module but the task is doable if 10 complicated indirect steps are followed in another module/s.
Minor: The defect affects minor functionality or non-critical data. It has an easy workaround. Example: A minor feature that is not functional in one module but the same task is easily doable from another module.
Trivial: The defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience. Example: Petty layout discrepancies, spelling/grammatical errors.
2.4.Low severity and low priority?
A-Terms and condition page is taking too much time to loading.
3.Who sets the severity in your project?
A-This is set by project manager or product manager.
4.What is priority?
A-Priority is the measure of urgency attached to fixing a defect.
4.1.Different types of priority?

  • Priority 1 – Critical (P1): This has to be fixed immediately within 24 hours. This generally occurs in cases when an entire functionality is blocked and no testing can proceed as a result of this. Or in certain other cases if there are significant memory leaks, then generally the defect is classified as a priority -1 meaning the program/ feature is unusable in the current state.
  • Priority 2 – High (P2): Once the critical defects have been fixed, a defect having this priority is the next candidate which has to be fixed for any test activity to match the “exit” criteria. Normally when a feature is not usable as it’s supposed to be, due to a program defect, or that a new code has to be written or sometimes even because some environmental problem has to be handled through the code, a defect may qualify for a priority 2.
  • Priority 3 – Medium (P3): A defect with this priority must be in contention to be fixed as it could also deal with functionality issues which is not as per expectation. Sometimes even cosmetic errors such as expecting the right error message during the failure could qualify to be a priority 3 defect.
  • Priority 4 – Low (P4): A defect with low priority indicates that there is definitely an issue, but it doesn’t have to be fixed to match the “exit” criteria. However this must be fixed before the GA is done. Typically, some typing errors or even cosmetic errors as discussed previously could be categorized in here. Sometimes defects with priority low are also opened to suggest some enhancements in the existing design or a request to implement a small feature to enhance user experience.

5.Who sets the priority in your project.
A-Developer and Project Manger set priority.
6.What is SDLC?
A- A framework to define each and every steps to be carried out during a software development is called as SDLC?
7.What are the different types of SDLC model?
A-Water Fall
Hybrid(Spiral & Prototype)
(V & Prototype)
8.What are the advantages and disadvantages of SDLC model?
-Formal Review at end of the each stage is very suitable for managerial control.
-Throughout the life cycle it followed by systematic documentation.
-The complete cycle goes thorough intermediate stages that can be reviewed  to verify weather project is going as per the client needs  and requirement.If not they can modify the project as per their requirement at very  initial stage of project.
-Major problem can not identified from end user prospective unless until the product is fully developed.
-Major challenged can not properly specified in side SRS document as user expected.
-User can not immediate verify the intermediate products and give review this product is suitable for his requirement or not?
-Another disadvantage of a program or software that follows the SDLC program is it encourages stiff implementation instead of creativity. There are requirements that must be met and that is all that developers complete.
-It is difficult to write the documentation part a lots of efforts required to maintain correctly the documentation.
9.Can you explain the V model and Agalie model?
A-V model is the enhance version of waterfall model.It allow us to verify and validate the project at each and every stages of development.
10.In your current project which model you having  followed?
While explaining use the word we.
A-We used to follows V and Spiral Model in our project.
11.Who decide this model should followed in your project.
A-Project manager and system analyst team used to decide which model should followed.
12.Why did you select this model for your project?
A-This model is best suitable for our our client,Also it best suites for the project where requirements are not complete and client is new to domain.
13.What is software testing?
A-It is the process by ensuring are we building the right product!
14.Why the software need to be tested?
A-Whether this software meets with the client requirement or not and also have we made done the procut right which meets the client expectation!
15.What are different types of software testing?
A-Black box testing
White Bot Testing
Grey Testing
16.What are different labels of software testing?
17.Why did you chose your carrier in software testing?
A-I like to handle risk,The testing process involve risk and also creativity thinking,So i decide to get into this filed.
18.What is white box testing?
A-The testing done by the developer during the development is known as white box testing.
19.Different types of white box testing?
A-1.Clear Box Testing
2.Open Box Testing
3.Logic Driven Testing
4.Path Driven Testing
5.Structural Testing
20.Who dose white box testing?
A-Developers do the white box testing.
21.Who did the white box testing in your current project?
A-Development team did the white-box testing.
22.When did they do the white box testing in current project?
23.How did they do white box testing in your current project?
A-Every Friday night they run the unit test suite on the new build and if the major of the test are passed then then they give the new build to the testing team on Monday morning.
24.What is black box testing?
We used to test the functionality of the software rather than looking the internal code structure is known as black box testing.
25.What is the difference between white box testing and black box testing?
a.White box focus on the internal structure of the code where as black box focus on functionality of the code form out side whether it meets the user requirement.
b.In white-box program logic is tested where in black box we do not concern about the logic.
c.White box is a structure and design based testing where as black box specification based testing.
26.What is functional testing?
A-Functional testing is the testing which is performed to verify that the software is functioning accordance with the design specification.During the functionality testing we check the  application functions,test inputs,menu functions,transaction functions,database updates etc.
27.Can u explain how you have done functional testing in your current project?
28.What is integration testing?
A-Testing the data flow between two different module or two different fetchers is known as integration testing.
29.Why do we do Integration Testing?
A-We do integration testing to check the interfaces are working correctly or not.
30.Different types of Integration Testing?
A-a.Incremental Integration Testing.
b.Non incremental integration testing.
31.When 1 module is build and other module is yet to build what will be the test approach?
A-We use a dummy module known as stubs or driver.
32.What are stubs and driver?
A-Stubs-When the child module is not yet developed replaced by a dummy module is known as stubs.
Driver-When we do integration testing,We use a dummy parent module instead of parent module is known as driver.
33.In your current project can you explain how you have done Integration Testing?
A-Ans should be starts with we have.
34.What is system testing?
35.What is difference between system testing and end to end testing?
36.Can u explain how you have done system testing in your current project?
37.Who is involved in the installation of the build in testing environment?
A-We had a dedicated team called release engineer or build engineer who was taking care of the code and setting of the testing environment wherein i have not involved in the  installation of the build in the testing environment in my project.
38.What is smoke testing?
A-We used to do smoke testing to ensure that whether the build is ready for testing or not.
39.When do we do smoke testing?
A-We used to do smoke test before any testing at first when a new build is lunched.
40.Why does the test engineer do smoke testing?
A-We used to do smoke test to ensure the current build is testable or not?
Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification.
41.What is the difference between smoke and sanity testing?


  • Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
  • A smoke test is scripted, either using a written set of tests or an automated test
  • A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
  • Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification).
  • Smoke testing is normal health check up to a build of an application before taking it to testing in depth.


  • A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
  • A sanity test is usually unscripted.
  • A Sanity test is used to determine a small section of the application is still working after a minor change.
  • Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
  • Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

42.Can u explain how how do you have done smoke testing in your current project?
43.What is ad-hoc testing?

A-The very term ad-hoc implies the lack of structure or something that is not methodical. When you talk about ad-hoc testing, it means that it is a form of black box or behavioral testing performed without any formal process in place.

The formal process here means having the documentation like requirement documents, test plan, test cases and proper test planning in terms of its schedule and order of performed tests. Also any actions performed during the testing are not typically documented.

44.Why we do the ad-hoc testing?
45.At which stage we do ad hoc testing?
46.Can u explain how you have done the ad-hoc testing in the current project?
47.What is release?
48.When to start system testing?
49.When to stop system testing?
a) When all the requirements are adequately executed successfully through test
b) Bug reporting rate reaches a particular limit
c) The test environment no more exists for conducting testing
d) The scheduled time for testing is over
e) The budget allocation for testing is over]
50.What is compatibility testing?
51.What are the defect was identified during the compatibility testing?
52.When we do compatibility testing?
53.Which platform have you done the compatibility testing?
54.How do you decide the platform?
55.What is functionality issue and compatibility issue?
56.What is exploratory testing?
57.When we  do the exploratory testing?
58.Have you ever done the exploratory testing in your current project?
59.Why do we do exploratory testing?
60.What are the drawbacks when we do the exploratory testing?
61.What is reliability testing?
62.What is usability testing?
63.What kind of application we do usability testing?
64.What are the different check point or checklist you might you might look when doing the reliability testing?
65.What is regression testing?
66.Different types of regression testing?
67.How do you find or identified the impact area in your project?
68.When we go for the fully regression testing?
69.Can you explain who how you have done the regression testing in your current project?
70.Drawbacks of regression testing?
71.When do we go for automation?
72.Explain STLC in detail?
73.What is difference between regression testing and retesting?
74.In your current project what is the process or approach you followed to test the project?
75.Difference between SDLC and STLC.
76.What is traceability matrix?
77.Can you write the traceability template that you have followed in your project?
78.Advantages of traceability matrix ?
79.Can you write the traceability template followed in project?
80.Advantages of traceability matrix?
81.What is retrospective meeting?
82.Who are the people who are involved in retrospective meeting?
84.What is test plan?
85.Who prepare test plan in your project?
86.What is the objective of preparing test plan in project?
87.What is the difference between test plan and test case?
88.What are context of test plan?
89.How will you define which feature are they are they going to test in your current project?
90.When to stop testing?
91.What are deliverable?
92.Can you explain the roles and responsibility in your current project?
93.What is defect life-cycle?
94.What is the difference between test approach and test methodology?
95.What is performance testing?
96.What are difference types of performance testing?
97.What is non functional testing?
98.What is the difference between functional and non functional testing?
99.What is test case?
100.Why do we write the test case?
101.Where do we write test case?
102.Can u explain the steps to write the test case?
103.Can u write a test case temple that you have been followed in your project?
104.Is testing constructive or destructive?
105.What is the difference between testing and quality?
106.Why does the software has a defect?
107.If you can not deliver a defect free of software what is use of testing?
108.What are the attribute of a good test engineer?
A-Good in observation
-Good in communication skill
-Should test the application from end user perspective.
109.What is big bang testing?
110.What is component testing?
111.What is positive testing?
112.What is -ve testing?
113.Can we conduct system testing directly by avoiding the functional and integration testing?
114.What are types of acceptance testing?
115.What is your involvement in acceptance testing?
116.Enplane test case design technique ?
117.How do u identify the smoke test?
118.After receiving the build what will you do?
119.Until smoke test pass what will the rest of the team will do?
120.Do you report the defect smoke testing is failed?
121.Who identifies the regression test suites?
122.What is difference between testing technique and testing types?
123.What is review?
124.Explain the review process that you have followed in your project?
125.How do you decide the review documentation?
126.What is code review?
127.What is difference between static and dynamic testing?
128.How you will receive the project requirement?
129.Is the testing team involved in the SRS preparation?
130.What is the difference between verification and validation?
131.After understanding the requirement what will you do?
132.Should you understand the whole project functionality or only the functionality assigned to you?
133.What is use cases?
134.What is user stories?
135.Explain the various test that was conducted in your project?
136.How many types of test plan are their?
137.Do you have any white box experience in your current project?
138.What are different categories of testing?
139.What are different categories of  black box design technique?
140.What are VBA?
141.What is EP?
142.Explain how do you test the following?
Mobile,Ac,Elevator,Water Bottle,Pen,Tv,Traffic Signal?
143.What are the different categories of white box testing?
144.What are the filed in the test case?
145.What a test scenario?
A-It is nothing but the functional scenarios for which the testing has to be conducted is also called as test condition.
146.What is most difficult part of test design?
147.How may test case you can write per day,& till now how many you have written?
148.What is the next procedure you follow after writing the test case?
149.How do you know that test case are completed or not?
150.How do u design the test case whose requirements are frequently changing?
151.I want to design the test case for a new domain in which you have not worked before do you think you can handle this?
152.Explain the scenario where you are not able to write the test case for given requirement?
153.What is the % of +ve and -ve  test have you written in your project?
A: +ve = 60%
-ve = 40%
154.How frequently the build is release and how do you know the build is ready for testing?
155.Whome do you _______________________
156.What will you do if the test case are failed?
157.In the module you check out are their are any issue or defect was they identifay after the realese?
158.What information do you provide with the defect?
159.Do you run the agression test for every defect fixed?
160.How you will you handle a developer who is not aggreing the defect you have reported is validate?
161.How do you handle the aggresive developer?
162.you are repening the defect fixed by developer how do ypou handle this situation?
163.Explain the hot technical discussion that you adding  development in your project?
164.Who take decission when to stop testing?
165.What is impact analysis?
166.What if we dont find solution for the critical defect will you stop it?
167.Who allocate the work in you r project?
168.Explain the various situation that you are faced during the testing?
169.How do you report your manager on dailly basic?
170.What is the difference between testing and debugging?
171.Which is a defect tracking tool you have includes in current project?
172.Write the defect report?
173.Write the defect report in you r project?
174.Which is important money or work?
A-Work is imporatant but in this age money also more importatnt.
175.What are key challanges of software testing?
A-Appalication should be stable.
-Understanding the requirment>
-Testing always iunder the time constraints.
-Which test to execute first.
-Testing the complete applaication.
-Domain knowledge and the business user perspective.
-Frequently changing the requirment.
-Reggression testing.
-Lack of skilled tester.
176.What is conformation testing?
A-It is also called as regresion testing.
177.What is exclusive testing?
A-It means that testing each and component in application with every possible number of input.
Note-Asper Principle of software testing principle exclusive testing is impossible,bcoz it require more time and which might delay in release application.
178. What is a test strategy?

A test strategy must address the risks and present a process that can reduce those
The two components of Test strategy are:
a) Test Factor: The risk of issue that needs to be addressed as a part of the test
strategy. Factors that are to be addressed in testing a specific application
system will form the test factor.
b) Test phase: The phase of the systems development life cycle in which testing
will occur.

Leave a Reply

Your email address will not be published. Required fields are marked *