Testing Question Part-2

16.The activity which includes confirming understanding, brainstorming and testing ideas is a
a. Code walkthrough
b. Inspection
c. Review
d. Structured walkthrough
Ans: c

17. The following can be considered to measure quality:
a. Customer satisfaction
b. Defects
c. Rework
d. All of the above
e.None of the above
Ans: d

18. The most common reason for the presence of a large number of bugs in a software product is,
a.Incompetence of the developer
b.Incompetence of the tester
c.Bad requirements
d.Wrong use of tools and techniques
Ans: d

19. The following is (are) not part of a data center operations
1. Capacity planning
2. I/O control
3. Scheduling
4. All of the above
5. None of the above
Ans:5

20. The process of securing future processing capability with proper data for future contingencies by duplicating systems procedures and data is
a. providing a Help Desk
b. Database Design
c. Artificial Intelligence
d. System Backup
e. All of the above
f. None of the above
Ans:

21. The objective of TQM is
a. To improve processes
b. To improve profitability
c. All of the above
d.None of the above
Ans: a

22. System Test Plan will not include
a. Approach
b.Pass/Fail criteria
c.Risks
d.Suspension and Resumption criteria
e.None of the above
Ans: c

23. The two types of checklists are _______________ and ________________________.

24. The following is NOT a category in MBNQA criteria:
a. Leadership
b. HR Focus
c. Quality Management
d. Information and Analysis
e. None of the above
Ans: c

25. The following are types of listening are:
a. Descriptive listening
b.Compensation listening
c.Apprehensive listening
d.All of the above
e.None of the above
Ans: c

26. Complaints must be resolved within
a. An hour
b. Four minutes
c. A day
d. Four hours
e.None of the above
Ans: b

27. Function Point is not a measure of
a. Effort
b.complexity
c.usability
d.all of the above
e.size
f.None of the above
Ans:

28.Quality Assurance personnel must not be involved in changing work products.
a. True
b. False
Ans:

29. The purpose of cost-of -quality computations is to show how much is being spent for the quality control and quality assurance program.
a. True
b. False
Ans: b

30. The method by which release from the requirements of a specific standard may be obtained for a specific situation is a
a. Tailoring
b. Customization
c. Force Field Analysis
d. Waiver
e. None of the above
Ans: d

Testing Question Part -1

1. The statement of an organization's commitment to quality is a
a. Policy
b. Vision
c. Mission
d. Principle
e. Goal
Ans: a

2. Which of the following is not a defect metric?
a. Location
b. Cause
c. Time to fix
d. Classification
e. Coverage
f. All of the above
Ans: f

3. Quality improvement programs may require the product itself to be changed.
a. True
b. False
Ans: b

4. The basis upon which adherence to policies is measured is
a. Standard
b. Requirement
c. Expected result
d. Value
e. All of the above
f. None of the above
Ans: a

5. Which of the following does not form a part of a workbench?
a. Standards
b. Quality attributes
c. Quality control
d. Procedures
e. Rework
Ans: b

6. The focus on the product is highest during
a. a walkthrough
b. a checkpoint review
c. an inspection
Ans: b

7. During an inspection, inspectors normally make suggestions on correcting the defects found.
a. True
b. False
Ans: b

8. There are _______ numbers of function types.
a. 2
b. 3
c. 4
d. 5
e. 6
Ans: c

9. The Quality manager will find it difficult to effectively implement the QAI Quality Improvement Process, unless his organization is willing to accept the Quality principles as
a. The organization’s policy
b. A challenge
c. The corporate vision
d. The organization’s goal
e. A management philosophy
f. All of the above
Ans: f

10. Baselines measure the _____________________ change.
a. Situation prior to
b. Expectation of benefits of
c. Effects of
d. Desirability of
e. None of the above
Ans: a

11. Modifying existing standards to better match the need of a project or environment is
a. Definition
b. Standard for a standard
c. Tailoring
d. Customization
e. None of the above
Ans: c

12. Malcolm Baldridge National Quality Award has the following eligibility categories/ dimensions
a. Approach
b. Deployment
c. Results
d. All of the above
e. Manufacturing, Service and small businesses
f. None of the above
Ans: e

13. The term “benchmarking” means
a. Comparing with past data from your organization
b. Comparing with the results of a market survey
c. Comparing with the results of a customer survey
d. None of the above
Ans: d

14. An example of deployment of a quality approach is:
a. The degree to which the approach embodies effective evaluation cycles
b. The appropriate and effective application to all product and service characteristics
c. The effectiveness of the use of tools, techniques, and methods
d. The contribution of outcomes and effects to quality improvement
e. The significance of improvement to the company’s business
Ans: c

15. The concept of continuous improvement as applied to quality means:
a. Employees will continue to get better
b. Processes will be improved by a lot of small improvements
c. Processes will be improved through a few large improvements
d. Improved technology will be added to the process, such as acquiring CASE tools
e. The functionality of the products will be enhanced
Ans: b

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 understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. The following are some of the items that might be included in a test plan, depending on the particular project:

* Title
* Identification of software including version/release numbers
* Revision history of document including authors, dates, approvals
* Table of Contents
* Purpose of document, intended audience
* Objective of testing effort
* Software product overview
* Relevant related document list, such as requirements, design documents, other test plans, etc.
* Relevant standards or legal requirements
* Traceability requirements
* Relevant naming conventions and identifier conventions
* Overall software project organization and personnel/contact-info/responsibilties
* Test organization and personnel/contact-info/responsibilities
* Assumptions and dependencies
* Project risk analysis
* Testing priorities and focus
* Scope and limitations of testing
* Test outline - a decomposition of the test approach by test type, feature, functionality, process, system, module, etc. as applicable
* Outline of data input equivalence classes, boundary value analysis, error classes
* Test environment - hardware, operating systems, other required software, data configurations, interfaces to other systems
* Test environment validity analysis - differences between the test and production systems and their impact on test validity.
* Test environment setup and configuration issues
* Software migration processes
* Software CM processes
* Test data setup requirements
* Database setup requirements
* Outline of system-logging/error-logging/other capabilities, and tools such as screen capture software, that will be used to help describe and report bugs
* Discussion of any specialized software or hardware tools that will be used by testers to help track the cause or source of bugs
* Test automation - justification and overview
* Test tools to be used, including versions, patches, etc.
* Test script/test code maintenance processes and version control
* Problem tracking and resolution - tools and processes
* Project test metrics to be used
* Reporting requirements and testing deliverables
* Software entrance and exit criteria
* Initial sanity testing period and criteria
* Test suspension and restart criteria
* Personnel allocation
* Personnel pre-training needs
* Test site/location
* Outside test organizations to be utilized and their purpose, responsibilties, deliverables, contact persons, and coordination issues
* Relevant proprietary, classified, security, and licensing issues.
* Open issues
* Appendix - glossary, acronyms, etc