Font size
WorksheetsCSA3703 - Software Testing: Multiple Choice Questions
Total questions: 100
Worksheet time: 50mins
_____ must be developed to describe when and how testing will occur.
Test Strategy
Test Plan
Test Design
High Level document
Testing Process comprised of
Test Plan and Test Cases
Test log and Test Status
Defect Tracking
All of the above
As a tester, what is your main objective in reviewing a requirement document?
To ascertain that each requirement is traceable to a business need
To ascertain that each requirement is both testable and uniquely identifiable
To ascertain that each requirement is traceable to a business need, testable, and uniquely identifiable
To ascertain that each requirement is uniquely identifiable
We split testing into distinct stages primarily because:
Each test stage has a different purpose.
It is easier to manage testing in stages.
We can run different tests in different environments.
The more stages we have, the better the testing.
Which of the following characterizes the cost of faults?
They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases.
They are easiest to find during system testing but the most expensive to fix then.
Faults are cheapest to find in the early development phases but the most expensive to fix then.
Although faults are most expensive to find during early development phases, they are cheapest to fix then.
A failure is:
Found in the software; the result of an error.
Departure from specified behavior.
An incorrect step, process or data definition in a computer program.
A human action that produces an incorrect result.
Enough testing has been performed when
Time runs out.
The required level of confidence has been achieved.
No more faults are found
Test design mainly emphasizes all the following except
Data planning
Test procedures planning
Mapping the data and test cases
Data synchronization
Which one of the following describes the major benefit of verification early in the life cycle?
It allows the identification of changes in user requirements.
It facilitates timely set up of the test environment.
It reduces defect multiplication.
It allows testers to become involved early in the project.
Which of the following is NOT a reasonable testing objective?
To find faults in the software
To prove that the software has no faults
To give confidence in the software
To find performance problems
In Life cycle approach to testing, test execution occurs ______
During testing phase
During requirement phase
During coding phase
None of the above.
A deviation from the specified or expected behavior that is visible to end-users is called:
An error
A fault
A failure
A defect
What is the important criterion in deciding what testing technique to use?
How well you know a particular technique
The objective of the test
How appropriate the technique is for testing the application
Whether there is a tool to support the technique
Which of the following are characteristics of testable software?
Observability
Simplicity
Stability
All of the above
The Planning phase of a formal review includes the following:
Explaining the objectives
Selecting the personnel, allocating roles.
Follow up
Individual Meeting preparations
A Person who documents all the issues, problems and open points that were identified during a formal review.
Moderator
Scribe
Author
Manager
Who are the persons involved in a Formal Review? i. Manager ii. Moderator iii. Scribe / Recorder iv. Assistant Manager
ii,iii,iv are true
i,ii,iii are true and iv is false.
ii,iii,iv are true and i is false.
i,iv are true and ii, iii are false.
Which of the following is a Key Characteristics of Walk Through?
Scenario, Dry Run, Peer Group
Pre Meeting Preparations
Formal Follow Up Process
Includes Metrics
Which of the following term describes testing?
Finding broken code
Evaluating deliverable to find errors
A stage of all projects
None of the mentioned
What type of fault remains in the system for some period and then disappears?
Permanent
Transient
Intermittent
Non-Permanent
Which of the following approaches are used to achieve reliable systems?
Fault prevention
Fault removal
Fault tolerance
All of the mentioned
A system maintaining its integrity while accepting a temporary halt in its operation is said to be in a state of
Full Fault Tolerance
Graceful Degradation
Fail Soft
Fail Safe
Which of the following Error Detection checks is not a part of Application detection?
Hardware checks
Timing checks
Reversal checks
Coding checks
Exception handling is a type of
Forward error recovery mechanism
Backward error recovery mechanism
Top recovery mechanism
Bottom recovery mechanism
All fault-tolerant techniques rely on
Integrity
Dependability
Redundancy
Inter-dependability
It is imperative for communicating processes to reach consistent recovery points to avoid the _effect, with backward error recovery mechanism.
Static
Dynamic
Domino
Whirlpool
What do you understand by V&V in software testing?
Verified Version
Version Validation
Verification and Validation
Version Verification
When does the testing process stops?
When resources (time and budget) are over
When some coverage is reached
When quality criterion is reached
Testing never ends
Quality also can be looked at in terms of user satisfaction which includes
A compliant product
Good quality output
Delivery within budget and schedule
All of the mentioned
Inspections and testing are what kinds of Quality Costs
Prevention
Internal Failure
External Failure
Appraisal
According to ISO 9001, inspection and testing comes under which management responsibility?
Process control
Document control
Control of non-conforming products
Servicing
The degree to which the design specifications are followed during manufacturing is known as
Quality of design
Quality of conformance
Quality of testing
None of the mentioned
What kind of quality cost is incurred when an error is detected in a product prior to shipment?
Prevention
Internal Failure
External Failure
Appraisal
Non-conformance to software requirements is known as
Software availability
Software reliability
Software failure
None of the mentioned
Software project manager is engaged with software management activities. He is responsible for _____.
Project planning
Monitoring the progress
Communication among stakeholders
All mentioned above
Which quality deals with the maintaining the quality of the software product?
Quality assurance
Quality control
Quality Efficiency
None of the above
The interviews, which are held between two persons across the table is _____.
Written
Non-structured
Group
One-to-one
How many forms exists of Barry Boehm’s COCOMO Model?
Two
Three
Four
No form exists
Who suggested the four different approaches to the sizing problem?
Putnam
Myers
Boehm
Putnam and Myers
Which of the following is not one of the five information domain characteristics of Function Point (FP) decomposition?
External inputs
External outputs
External process
Internal Inputs
The main guide for selecting test cases is
To assess risks
To assess quality
Both (a) and (b)
None of the above
Which of the following is not a risk reduction scheme?
Priority category scheme
Risk analysis
Interviewing
None of the above
The potential problems are identified and their probabilities and impacts are given weights in which technique
Priority categorization scheme
Risk analysis
Interviews
None of the above
Risk exposure is given by which formula
It is the product of probability of occurrence of risk and its impact
It is the sum of probability of its occurrence and its impact
It is the standard deviation of the sum of its probability and its impact
None of the above
A risk matrix
Allows the testers to evaluate and rank potential problems by giving weights to probability or severity value as necessary
Allows testers to assign thresholds that classify the potential problems into priority categories
Both (a) and (b)
None of the above
In diagonal band prioritisation scheme
Severity equals probability
Severity is never equal to probability
Either (a) or (b)
Both (a) and (b)
Some managers found out that
Reducing the number of test cases
Increased the number of test cases
It does not affect the number of test cases
None of the above
Equivalence partitioning is a technique for?
Correction regression testing
Retest-all strategy
Combinational explosion
None of the above
The test cases derived from use cases
Are most useful in uncovering the defects in the process flows during real world use of the system.
Are most useful in uncovering the defects in the process flows during the testing use of the system.
Are most useful in covering the defects in the process flows during real world use of the system.
Are most useful in covering the defects at the integration level.
Several techniques for using test execution information to prioritize test cases for regression testing include,
Techniques that order test cases based on their total coverage of code components.
Techniques that order test cases based on their total coverage of code components not previously covered.
Techniques that order test cases based on their estimated ability to reveal faults in the code components that they cover.
All of the above
Test management primarily focuses on
Coding
Planning and controlling testing activities
Writing documentation
Designing UI
Testing and debugging goals must be defined during
Deployment
Test Planning
Maintenance
Coding
Which document defines how testing will be carried out?
SRS
Test Plan
Vision Document
Test Strategy
A test plan is usually prepared by the
Developer
Client
Test Manager
End user
Which of the following is NOT a test plan component?
Test items
Risks and mitigation
Network design
Schedule
Test objectives describe:
The overall goals and success criteria for testing activities
The scope of features to be developed in the product
The coding standards to be followed by developers
The deployment strategy for releasing the product
A Test Plan Attachment usually contains:
Test Data
Source Code
User Manuals
Sales Forecast
Locating test items refers to identifying:
Stakeholders
Requirements
The components to be tested
Hardware setup
The final outcome of testing is documented in the:
Bug log
Test report
Risk matrix
Review form
A test result report should be:
Complex
Understandable
Brief only
Confidential
Which group creates test policies and procedures?
End users
Management
Operation staff
Customers
The testing specialist group mainly deals with:
Designing UI
Executing tests
Writing business proposals
Marketing strategies
A policy document defines:
Test cases
Rules and guidelines for testing
Coding style
Regression timelines
Testing and debugging are:
Same
Opposites
Complementary
Not related
Debugging is performed by:
Tester
Developer
Customer
Project Manager
The role of testing group in planning includes:
Estimating resources
Creating UI mockups
Deployment activities
Database setup
A testing group must possess skills such as:
UX design
Analytical and technical skill
Sales negotiation
Photography
Building a testing group involves:
Hiring and skill development
Removing automation
Stopping training
Changing product features
Which of the following is a part of test policy development?
Test coverage rules
Marketing strategy
UI design guideline
None
Test scheduling includes:
Debug steps
Timeline for activities
Code style guidelines
Customer survey
A good test plan must be:
Ambiguous
Flexible and clear
Confidential
Very lengthy
Entry and exit criteria define:
Who writes code
When testing starts and stops
Cost of project
Business risks
Risk analysis in test planning helps in:
Increasing product defects
Mitigating issues before testing
Reducing coverage
Removing manual testing
Scope of testing identifies:
What will be tested
What will NOT be tested
Both a and b
Only test schedule
A good test report must include:
Test results and defect statistics
Source code
Budget
All emails
Traceability matrix is used for:
Linking requirements to test cases
Designing UI
Managing budget
Database mapping
The primary audience for a test report is:
Testers only
Developers and managers
End users
Public
Test metrics help in:
Measuring effectiveness
Debugging
Changing UI
Deployment
Resource planning determines:
Code architecture
Hardware, software, manpower required
User feedback
UI color
Communication in testing must be:
Delayed
Clear and continuous
One-time
Optional
Test environment setup includes:
Hardware setup
Software installation
Database setup
All of the above
Which group approves the final test strategy?
Test Engineer
Management
Customer
Developer
Test execution is guided by:
Test strategy
Test plan
Both a and b
None
A bug triage meeting is held to:
Write test cases
Prioritize defects
Train new users
Perform acceptance testing
A stable testing team improves:
Defect count
Test consistency and accuracy
Cost of product
Deployment time
Test planning begins during:
Requirement phase
Deployment phase
Maintenance phase
After coding
Test execution schedule defines:
Who will run tests and when
User interface details
Network setup
Business strategy
Test deliverables include:
Test plan
Test scripts
Test report
All of the above
Pilot testing is mainly done during:
Planning
Final acceptance testing
Deployment
Debugging
A skilled testing group reduces:
Test accuracy
Risk of product failure
Customer satisfaction
Regression coverage
A review of the test plan ensures:
Proper test coverage
UI consistency
Code formatting
Packaging
Test management tools help in:
Writing code
Tracking test cases and results
Marketing
Billing
Which skill is most important for testers?
Analytical thinking
Drawing
Singing
Cooking
Test policy defines:
High-level test guidelines
Individual test steps
Debug instructions
Code comments
A defect reporting system must track:
Status
Priority
Severity
All of the above
Test control ensures:
Testing stays on schedule
Testers stop reporting bugs
UI is updated
Database is clean
Stakeholders use test reports to:
Approve release decisions
Change UI theme
Write test cases
Debug code
A well-defined testing policy helps in:
Standardizing testing process
Increasing software size
Reducing quality
Avoiding automation
Testing maturity improves when:
Policies and procedures evolve
Tester skill decreases
Communication stops
No documentation exists
The final goal of test management is:
Finding all bugs
Delivering high-quality software
Reducing development time only
Running test cases
