Q1. What is verification?

A: Verification ensures the product is designed to deliver all functionality to the customer; it typically
involves reviews and meetings to evaluate documents, plans, code, requirements and specifications.
Q2. What is validation?
validation typically involves actual testing and takes place after verifications.
Q3. What is a walkthrough?
walkthrough is an informal meeting for evaluation. It's the process of inspecting software code by
following paths through the code. The purpose of code walkthroughs is to ensure the code fits the
purpose.
Q4. What is quality?
A: uality software is software that is reasonably bug!free, delivered on time and within budget, meets
requirements and e"pectations and is maintainable. uality depends on who the customer is. #ustomers
of a software development pro$ect include end!users, customer acceptance test engineers, testers.
Q5. What is software life cycle?
It includes phases like requirements analysis, functional design, internal design, documentation planning,
test planning, coding, document preparation, integration, testing, maintenance, updates, re!testing and
phase!out.
Q6. What is a test lan?
A: % software pro$ect test plan is a document that describes the ob$ectives, scope, approach and focus of
a software testing process.
Q!. What is a test case?
A: % test case is a document that describes an input, action, or event and its e"pected result, in order to
determine if a feature of an application is working correctly. % test case should contain particulars such as
a...
Test case identifier;
Test case name;
&b$ective;
Test conditions'setup;
Input data requirements'steps, and
("pected results.
Q". What is #lack #o$ testing?
A: )lack bo" testing is functional testing, not based on any knowledge of internal software design or code.
)lack bo" testing are based on requirements and functionality.
Q%. What is white #o$ testing?
A: *hite bo" testing is based on knowledge of the internal logic of an application's code.
Q1&. What is unit testing?
+nit testing is performed after the e"pected test results are met.
Q11. What is arallel'audit testing?
A: ,arallel'audit testing is testing where the user reconciles the output of the new system to the output of
the current system to verify the new system performs the operations correctly.
Q12. What is functional testing?
A: -unctional testing is black!bo" type of testing geared to functional requirements of an application.
Q13. What is usa#ility testing?
+sability testing is testing for 'user!friendliness' and depends on the targeted end!user or customer.
Q14. What is incre(ental integration testing?
A: Incremental integration testing is continuous testing of an application as new functionality is
recommended.
Q15. What is integration testing?
A: +pon completion of unit testing, integration testing begins. Integration testing is black bo" testing. The
purpose of integration testing is to ensure distinct components of the application still work in accordance
to customer requirements.
Q16. What is syste( testing?
A: .ystem testing is black bo" testing, performed by the Test Team. The purpose of system testing is to
validate an application's accuracy and completeness in performing the functions as designed. +pon
completion of integration testing, system testing is started. )efore system testing, all unit and integration
test results are reviewed by .oftware % to ensure all problems have been resolved.
Q1!. What is regression testing?
A: The ob$ective of regression testing is to ensure the software remains intact.
Q1". What is sanity testing?
A: .anity testing is performed whenever cursory testing is sufficient to prove the application is functioning
according to specifications. This level of testing is a subset of regression testing. It normally includes a set
of core tests of basic /+I functionality to demonstrate connectivity to the database, application servers,
printers, etc.
Q1%. What is erfor(ance testing?
,erformance testing verifies loads, volumes and response times, as defined by requirements.
Q2&. What is load testing?
0oad testing is testing an application under heavy loads, such as the testing of a web site to determine at
what point the system response time will degrade or fail.
Q21. What is installation testing?
A: Installation testing is testing full, partial, upgrade, or install'uninstall processes.
Q22. What is security'enetration testing?
A: .ecurity'penetration testing is testing how well the system is protected against unauthori1ed internal or
e"ternal access,
Q23. What is recovery'error testing?
A: 2ecovery'error testing is testing how well a system recovers from crashes, hardware failures, or other
catastrophic problems.
Q24. What is co(ati#ility testing?
A: #ompatibility testing is testing how well software performs in a particular hardware, software, operating
system, or network environment.
Q25. What is co(arison testing?
A: #omparison testing is testing that compares software weaknesses and strengths to those of
competitors' products.
Q26. What is accetance testing?
A: %cceptance testing is black bo" testing that gives the client'customer'pro$ect manager the opportunity
to verify the system functionality and usability prior to the system being released to production. The
acceptance test is the responsibility of the client'customer or pro$ect manager.
Q2!. What is alha testing?
A: %lpha testing is testing of an application when development is nearing completion. 3inor design
changes can still be made as a result of alpha testing. %lpha testing is typically performed by end!users or
others, not programmers, software engineers, or test engineers.
Q2". What is #eta testing?
A: )eta testing is testing an application when development and testing are essentially completed and final
bugs and problems need to be found before the final release. )eta testing is typically performed by end!
users or others, not programmers, software engineers, or test engineers.
Q2%. What is stress testing?
A: .tress testing is testing that investigates the behavior of software 4and hardware5 under e"traordinary
operating conditions. -or e"ample, when a web server is stress tested, testing aims to find out how many
users can be on!line, at the same time, without crashing the server. .tress testing tests the stability of a
given system or entity.
Q3&. What is load testing?

A: 0oad testing simulates the e"pected usage of a software program, by simulating multiple users that
access the program's services concurrently. 0oad testing is most useful and most relevant for multi!user
systems, client'server models, including web servers.
Q31. What is software testing?
A: .oftware testing is a process that identifies the correctness, completenes, and quality of software.
Q32. What is alha testing?
A: %lpha testing is final testing before the software is released to the general public. -irst, 4and this is
called the first phase of alpha testing5, the software is tested by in!house developers. They use either
debugger software, or hardware!assisted debuggers. The goal is to catch bugs quickly. Then, 4and this is
called second stage of alpha testing5, the software is handed over to us, the software % staff, for
additional testing in an environment that is similar to the intended use.
Q33. What is the difference #etween alha and #eta testing?
A: %lpha testing is performed by in!house developers and software % personnel. )eta testing is
performed by the public, a few select prospective customers, or the general public.
Q34. What is clear #o$ testing?
A: #lear bo" testing is the same as white bo" testing.
Q35. What is glass #o$ testing?
A: /lass bo" testing is the same as white bo" testing.
Q36. What is oen #o$ testing?
A: &pen bo" testing is same as white bo" testing.
Q3!. What is #lack #o$ testing?
A: )lack bo" testing a type of testing that considers only e"ternally visible behavior. )lack bo" testing
considers neither the code itself, nor the 6inner workings6 of the software.
Q3". What is closed #o$ testing?
A: #losed bo" testing is same as black bo" testing.
Q3%. What are the hases of the software develo(ent rocess?
A: The software development process consists of the concept phase, requirements phase, design phase,
implementation phase, test phase, installation phase, and checkout phase.
Q4&. What (odels are used in software develo(ent?
A: In software development process the following models are used7 waterfall model, incremental
development model, rapid prototyping model, and spiral model.