Software Testing-Question Bank: Q. 31 to 40
Q. 31: What is Verification?
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; this can be done with checklists, issues lists, walkthroughs and inspection meetings.
<<<<<< =================== >>>>>>
Q. 32: What is Validation?
Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed.
<<<<<< =================== >>>>>>
Q. 33: What is a Test Plan?
A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group nderstand the why and how of product validation. It should be thorough enough to be useful, but not so thorough that none outside the test group will be able to read it.
<<<<<< =================== >>>>>>
Q. 34: What is a Walkthrough?
A walkthrough is an informal meeting for evaluation or informational purposes. A walkthrough is also a process at an abstract level. It’s the process of inspecting software code by following paths through the code (as determined by input conditions and choices made along the way). The purpose of code walkthroughs is to ensure the code fits the purpose. Walkthroughs also offer opportunities to assess an individual’s or team’s competency.
<<<<<< =================== >>>>>>
Q. 35: What is Software Life Cycle?
Software life cycle begins when a software product is first conceived and ends when it is no longer in use. It includes phases like initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, re-testing and phase-out.
<<<<<< =================== >>>>>>
Q. 36: What is the Difference between STLC & SDLC?
STLC means ” Software Testing Life Cycle”. It starts with activities like : 1) Preparation of Requirements Document 2) Preparation of Test Plan 3) Preparation of Test Cases 4) Execution of Test Cases 5) Analysis of Bugs 6) Reporting of Bugs 7) Tracking of Bugs till closure.
Whereas SDLC means ” Software Development Life Cycle” is a software development process, used by a systems analyst to develop an information system. It starts with activities like :
1) Project Initiation
2) Requirement Gathering and Documenting
3) Designing
4) Coding and Unit Testing
5) Integration Testing
6) System Testing
7) Installation and Acceptance Testing
8) Support or Maintenance
<<<<<< =================== >>>>>>
Q. 37: What are the various components of STLC?
Various components of “Software Testing Life Cycle” are
1) Requirements Document
2) Preparation of Test Plan
3) Preparation of Test Cases
4) Execution of Test Cases
5) Analysis of Bugs
6) Reporting of Bugs
7) Tracking of Bugs till closure
<<<<<< =================== >>>>>>
Q. 38: What is the Difference between Project and Product Testing?
If any organization is developing the application according to the client specification then it is called as project. Accordingly its testing is known as “Project Testing”
Whereas If any organization is developing the application and marketing it is called as product. Hence its testing is known as “Product Testing”
<<<<<< =================== >>>>>>
Q. 39: What are the Testing Types & Techniques?
Black Box and White Box are the most popular types of software testing. These are not the stand-alone testing techniques.
Testing techniques falling under the Black-Box type are: 1) Equivalence Partitioning 2) Boundary Value Analysis 3) Cause-Effect Graphing 4) Error-Guessing etc.
Whereas testing techniques falling under the White-Box type are:
1) Statement coverage
2) Decision coverage
3) Condition coverage
4) Decision-condition coverage
5) Multiple condition coverage
6) Basis Path Testing
7) Loop testing
8) Data flow testing etc.
<<<<<< =================== >>>>>>
Q. 40: How do you introduce a new software QA process?
It depends on the size of the organization and the risks involved. For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required.
Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, test engineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable.
Continue to Next Part : Q 41 to 50
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.
the website http://www.softwaretestinggenius is actually genius it is very supportive nd in easy laguage…….thanx genius………..