1. What is testing?

Testing is a process of executing the program with the intent of finding errors.
Testing the application against satisfied the user requirements or not.
2. Types of testing?
Manual and automation testing.
3. Testing techniques?
Block box and white box testing.
4. Levels of testing?
Unit, Integration, System and User acceptance testing.
5. What is block box testing?
Testing based on external view of application.
Tests are based on requirements and functionality.
The testers simply giving the input to the system and check the outputs.
6. Block box testing techniques?
Boundary Value Analysis: To find whether the application is accepting the expected range of values
and rejecting the out of values.
7. White box testing?
Testing based on internal logic of the program.
Testing is focused on how the operations performed inside program.
8. What is Verification?
Checks whether we are building the right system / right product.
Verification strategies contains
1. Requirement review, 2. Design review, 3. Code walkthrough, 4. Code inspection.
9. What is Validation?
Checks whether we are building the system right / product right.
Validation strategies contains
Unit testing, Integration testing, system testing, performance testing, user acceptance testing,
installation testing, alpha testing and beta testing.
10. What is Quality Assurance?
QA is a planed and systematic set of activities.
QC is staff function, which will monitoring and measuring the strength of development process is
called QA.
QA is necessary to provide adequate confidence to their products and services will confirm to specified
requirements and meet user needs.
QA is the responsibility for entire team.
QA is a Defect Prevention and it is a process oriented.
11. What is Quality Control?
QC is the team or department, which will check or validate the software after development is finished.
QC is the part of QA.
QC is the responsibility of the tester.
QC is a Defect detection and correction, it is a process oriented.
12. What is Sanity Testing?
An initial testing, effort to accept the build. (with out comparing the test cases).
Are used only to validate the higher functionality.
13. What is Smoke testing?
To test the major requirements / essential functionalities.
When time period is shot for testing.
14. What is Unit Testing?
Testing each and every micro field of an application is called unit testing.
The basic input and output are tested, along with their functionality.
Based on LLD, Unit test plan (UTP) and unit test case (UTC) are prepared and reviewed.
15. What is integration testing?
Interface between the modules is tested which includes internal and external interface.
16. What is system testing?
The entire application is tested is called system testing.
17. What is User acceptance testing?
Performed by the client at their place with their requirements.
18. What is Regression testing?
Regression test will make sure that on e fix does not create some other problem in their
program/other interface. So a set of related test cases repeated again. To make sure that nothing else
is affected buy fix.
Whenever a new build has come regression testing should be done.
19. What is Retesting?
To check whether the bug is fixed or not.

PRABU M | Mobile: +91 9884206824 | Email: [email protected] Page 1

 20. What is Ad-hoc testing?
Ad-hoc testing is the testing without using the test plan, test case or test procedures. It’s not
organized, not repeatable, and can’t be tracked.
21. What is Alpha testing?
Alpha testing is a testing of an application, when the development is nearing completion. This is done
at developer’s side.
22. What is Beta testing?
The product is provided to a limited set of audience, who ultimately going to use the product. Thus the
product faces a real time test this is known as beta testing.
23. What is SDLC?
The process of developing new software from its initial conception to its public release is the SDLC and
it involves in 5 stages of:
I. Requirement and Analysis phase,
2. Design phase,
3. Coding phase,
4. Testing phase and
5. Implementation and Maintenance phase.
24. What is water fall model?
In this model, when one phase will complete we go to another phase. Requirement is clear.
1. Requirement Analysis
2. Design
3. Coding
4. Testing
5. Implementation and maintenance
Advantage: Testing phase is separately.
Disadvantage: Moving back to previous is not possible and Time losing.
24. What is V model?
V model is a combination of verification and validation model.
In this model the development phase and testing phase takes simultaneously.
Advantage: Immediate rectification of errors is possible and Time consumption.
Disadvantage: This model does not provide a clear path for problems, which occur during the testing
phase.
25. What is Test Strategy?
Test Strategy describes the general approach and objectives of the test activities.
26. What is Test Plan?
Test Plan is a document.
A test plan is a useful way to think through the efforts needed to validate the acceptability of software
product.
The completed document will help people outside the test group understand the “why” and “how” of
product validation.
Contents of Test Plan
1. Purpose
2. Scope
3. Test Approach
4. Entry Criteria
5. Task / Responsibilities
6. Exit Criteria
7. Schedules / Milestones
8. Hardware and Software Requirements
9. Risks and Mitigation Plans
10. Tools to be used
11. Deliverables
12. References
13. Annexure
14. Sign-Off
27. What is Test Case?
Test case is a set of statements, it contains
1. Test Case Id
2. Navigation/Description
3. Input – Field / Value
4. Expected Result
5. Actual Result
6. Pass/Fail
7. Remarks

PRABU M | Mobile: +91 9884206824 | Email: [email protected] Page 2

 28. What is Bug and Life cycle?
Error+Fault=Bug or Defect
Life Cycle: Open, fixed, closed, rested, rejected, reopen.
29. Bug Tracking templates?
1. Bug Id
2. Test Case Id
3. Bug Description
4. Repeatable - Yes / No
5. Type (GUI, DB…)
6. Severity
7. Priority
8. Status
9. Reported By
10. Reported On
11. Fixed By
12. Fixed On
30. What is Severity?
Once we complete the testing, we have to find out how severe the bug is? Based on severity we will
fix the priority.
Critical -Installation failure, Exe problem, System hanging.
Major - Main module / any module is not operating in an application.
Minor - Name field accepts numeric and special characters.
Cosmetic - Spelling mistakes (in application, screen / output), font, and color.
31. What is Priority?
Is based on bugs, which one to be fixed first.
The priority level describes the time for resolution of the defect. The priority level would be classified
as follows
Immediate - Resolve the defect with immediate effect.
At The Earliest - Resolve the defect at the earliest, on priority at the second level.
Normal - Resolve the defect.
Later - Could be resolved at the later stages.
32. What is Test Metrics?
When defects are found it as to be documented to generate various statistics.
The defect found in various stages like SRS review, HLD review, LLD review, code review, test case
review etc. When defects are found the cause for the defect is analyzed.
The important ones are
Defect Leakage - When a particular defect is not detected and it is detected in subsequent stages,
rework will take more time.
Defect Age - Is the duration between the phase when the defect is introduced and when the defect is
identified and rectified (we must minimize the DA).
Defect Distribution - The percentage of number of defects found out in a particular phase to the
total number of defects found out in the development.
Defect Density - The total number of defects per kilo line of code (KLOC) (Lower the number higher
is the efficiency usually 1 bug per million line of code).
33. What is Performance testing?
The performance of the system is determined by using Load / Stress / Volume Testing.
Ensure that the product response time meet the user expectations, response time will be tested under
heavy stress / volume.
34. What is Load / Volume testing?
Load Testing: Testing the performance of the application with maximum number of users access the
system / application simultaneously. (Testing application under heavy load).
Volume Testing: To find weakness in the system with respect to its handling of large amounts of
data during short time period.
35. What is Stress testing?
To test the software with abnormal situation. Stress testing attempts to find the limits at which the
system will fail.
36. What is Traceability matrix?
Traceability matrix is mapping between the requirements and test cases.
It is used to identifying the missing test cases.
37. What is configuration management?
Configuration management is used to identifying, organizing and controlling modifications to the
software being built by a programming team. Since changes are inevitable in the software process, it
can occur at any time. To avoid confusion due to changes they coordinate software development by
configuration management. It is a tool to make changes simultaneously.

PRABU M | Mobile: +91 9884206824 | Email: [email protected] Page 3