Font size
WorksheetsPage 1
Total questions: 96
Worksheet time: 48mins
_____ methods can be used to drive validations tests
Yellow-box testing
Black-box testing
White-box testing
All of the mentioned
A predicate expression associated with an event is known as
Transition
Class
Guard
None of the above
Testing of nested loops were suggested by
Littlewood
Beizer
Boehm
None of the above
A powerful technique to use any time a system presents a small input domain with a large number of permutations is known as
Regression testing
Object oriented testing
Orthogonal array testing
None of the above
What is the normal order of activities in which traditional software testing is organized? Select the correct sequence.
Unit testing → Integration testing → System testing → Validation testing
Integration testing → Unit testing → System testing → Validation testing
System testing → Integration testing → Validation testing → Unit testing
Validation testing → System testing → Integration testing → Unit testing
Which of the following need to be assessed during unit testing?
Algorithmic performance
Code stability
Execution paths
Both c and c
Top-down integration testing has as its major advantage(s) that
Low level modules never need testing
Major decision points are tested early
No drivers need to be written
Both b and c
Bottom-up integration testing has as its major advantage(s) that
Major decision points are tested early
No drivers need to be written
No stubs need to be written
Regression testing is not required
The OO testing integration strategy involves testing
Groups of classes that collaborate or communicate in some way
Single operations as they are added to the evolving class implementation
Operator programs derived from use-case scenarios
None of the above
Acceptance tests are normally conducted by the
Developer
End users
Test team
Systems engineers
Testing OO class operations is made more difficult by
Encapsulation
Inheritance
Polymorphism
Both b and c
Scenario-based testing
Concentrates on actor and software interaction
Misses errors in specifications
Misses errors in subsystem interactions
Both a and b
Deep structure testing is not designed to
Examine object behaviors
Exercise communication mechanisms
Exercise object dependencies
Exercise structure observable by the user
Which of these techniques is not useful for partition testing at the class level?
Attribute-based partitioning
Category-based partitioning
Equivalence class partitioning
State-based partitioning
Tests derived from behavioral class models should be based on the
Data flow diagram
Object-relation diagram
State diagram
Use-case diagram
______ is the least effective method in isolating the cause of software errors.
Algorithmic Bugs
Brute Force Approach
Cause Elimination Approach
Backtracking Approach
The major disadvantage of top-down approach is need for ______.
Critical module
Skeleton
Stub
Project
______ couples top-down, bottom-up for upper and subordinate levels.
Alpha testing
Unit testing
Sandwich testing
Performance testing
What are the types of Integration Testing?
Big Bang Testing
Bottom up Testing
Top Down Testing
All of the above
Which of the following testing strategy is applicable at all three levels of testing
White box testing
Mutation testing
Regression testing
None of the above
Alpha testing involves
Customers
Testers
Developers
Site for Alpha testing is
Software development company
Installation site
Anywhere
None of the above
Site of Beta testing is
Software organization
Customer’s site
Anywhere
All of the above
Testing and subsequent debugging can account for ________ software development effort.
5–10%
10–20%
30–40%
80–90%
Integration testing techniques are
Top down
Bottom up
Sandwich
All of the above
Top-down approach is used for
Development
Identification of faults
Validation
Functional testing
Which of the following validation activities belong to low-level testing?
Unit testing
Integration testing
Performance testing
Both (a) and (b)
Debugging is a two-step process that begins when you find an error as a result of a successful test case. Step 1 is the determination of the exact nature and location of the suspected error within the program. Step 2 consists of _________
Viewing the error
Locating the error
Fixing the error
Filing the error
______ establishes the existence of errors ______ locates and corrects the errors.
Debugging, testing
Testing, Debugging
Testing, Verifying
Testing, Validation
What is the relationship between testing and quality assurance?
QA is part of a complete testing process
Testing and QA are two terms for the same thing
Testing is part of a complete QA process
When Testing is over it becomes QA
The Pareto analysis is most effective for ____________
Showing relationships between items
Measuring the impact of identified items
Ranking items by importance
None of the above
ITG stands for
Instantaneous test group
Integration testing group
Individual testing group
Independent test group
By collecting ______ during software testing, it is possible to develop meaningful guidelines to halt the testing process.
Failure intensity
Testing time
Metrics
All of the mentioned
Which of the following issues must be addressed if a successful software testing strategy is to be implemented?
Use effective formal technical reviews as a filter prior to testing
Develop a testing plan that emphasizes “rapid cycle testing.”
State testing objectives explicitly
All of the mentioned
Test cases should uncover errors like
Nonexistent loop termination
Comparison of different data types
Incorrect logical operators or precedence
All of the mentioned
Which of the following is not regression test case?
A representative sample of tests that will exercise all software functions
Additional tests that focus on software functions that are likely to be affected by the change
Tests that focus on the software components that have been changed
Low-level components are combined into clusters that perform specific software sub-function
The object of ______ within an OO system is to design tests that have a high likelihood of uncovering plausible bugs.
Fault-based testing
Integration testing
Use-based testing
Scenario-based testing
What refers to the externally observable structure of an OO program?
Deep structure
Surface structure
Core structure
All of the above
______ categorizes class operations based on the generic function that each performs
Category-based partitioning
Attribute-based partitioning
State-based partitioning
Which chart is a tool that depicts a project as a network diagram capable of graphically representing main events of a project in both parallel banal and consecutive way?
PERT chart
Gantt chart
Both A and B
None of the above
User Acceptance testing is
White box testing
Black box testing
Gray box testing
None of the above
Error guessing is a
Test verification technique
Test execution technique
Test control management technique
Test data management technique
The testing done to make sure existing features are not affected by new changes is called
Recursive testing
White box testing
Unit testing
Regression testing
According to Pareto’s principle, x% of defects can be traced to y% of all causes. What are the values of x and y?
60, 40
70, 30
80, 20
Which of the following is the primary goal of a software testing process?
To fix bugs
To ensure software meets user requirements
To write code
To develop software faster
In software quality, which of the following is the most critical factor for success?
Software design
Test planning
Customer satisfaction
Cost management
Which of the following tools is commonly used for software test management?
Jira
Eclipse
NetBeans
Visual Studio
What is the main focus of 'Agile testing'?
Reducing testing efforts
Testing software at the end of development
Iterative testing and continuous feedback
Using automation tools exclusively
Controlling and monitoring in testing ensures:
Bugs are hidden
Testing stays on track
Requirements are removed
Developers do testing
Which of the following is used to track test progress?
Test metrics
Storyboards
Encryption keys
UI design
A milestone in test management is:
A runtime error
A significant event in test progress
A code bug
A data record
Status meetings are conducted to:
Assign UI tasks
Update testing progress
Hire new testers
Install software
Measurements in testing are used to:
Evaluate test effectiveness
Modify product prices
Delete design documents
Change user requirements
Test completion criteria defines:
When coding starts
When testing can stop
When marketing begins
When installation is complete
Exit criteria may include:
Minimum test coverage
Maximum test cases
Coding standards
Database size
SCM stands for:
Software Component Management
Software Configuration Management
Secure Code Monitoring
Software Cost Monitoring
SCM ensures:
Version control
Code rewriting
UI improvement
Customer support
Which of the following is NOT part of SCM?
Change tracking
Version control
Defect prevention
Sales tracking
Reviews help in:
Identifying problems early
Speeding up marketing
Replacing customers
Changing UI theme
Which review is performed informally?
Walkthrough
Inspection
Audit
Inspection is usually:
Formal
Casual
Optional
Unstructured
Peer review involves:
Managers only
Review by colleagues
Customers only
Government auditors
The purpose of a review plan is to:
Schedule review activities
Test the database
Rewrite test cases
Execute regression test
Review components include:
Objective
Entry criteria
Reviewers
All of the above
A defect detected during review is called:
Review bug
Static defect
Regression issue
None
Reporting review results should be:
Confidential
Timely and clear
Delayed
Optional
Monitoring involves:
Track progress against plan
Adding new features
Writing design patterns
Running acceptance test only
Corrective action is taken when:
Goals are met early
Testing deviates from plan
No bugs are found
Customer requests a feature
A major purpose of controlling testing is:
Ensuring quality targets are met
Reducing hardware cost
Updating software license
Enhancing UI
Trend analysis helps in:
Predicting future test progress
UI prototyping
Sales forecasting
Product branding
A good report must include:
Summary of results
Defect details
Test coverage
All of the above
Review activities improve:
Development and testing quality
Office interior design
Hardware performance
Social media reach
A walkthrough is usually led by:
Developer
Reviewer
Moderator
Client
Inspection teams typically include:
Analysts, testers, moderators
Government officials
Sales team
End users
Review feedback helps in:
Improving documentation and code
Stopping testing
Increasing cost
Reducing automation
Change request tracking is part of:
SCM
Review system
Test execution
Report writing
Baseline in SCM refers to:
Approved version of a document
Test script
UI sketch
User feedback
Configuration items include:
Source code
Test cases
Requirement documents
All of the above
Monitoring tools are used to:
Track progress and performance
Install OS
Test UI elements only
Improve documentation style
Progress report must include:
Completed tasks
Pending tasks
Issues and risks
All of the above
Test effectiveness can be measured by:
Number of detected defects
Execution speed
Design style
Tester skill
Defect leakage indicates:
Bugs missed in earlier test stages
All bugs detected
Test summary
Customer satisfaction
Metrics collection begins during:
Test execution
Test planning
Deployment
Maintenance
A retrospective meeting is conducted:
After project completion
Before development
During coding
During unit test only
Quality audit ensures:
Process compliance
Product redesign
The UI is aesthetic
Testing stops
Test control decisions are based on:
Metrics and progress
Guesswork
Customer emotions
Team workload alone
Test schedule variance indicates:
Schedule difference from plan
UI changes
Customer opinion
Software size
Milestones act as:
Progress checkpoints
Deployment reports
Test failures
A defect summary report shows:
Defect distribution and status
UI feedback
Sales reports
Security breaches
Which type of review checks compliance to standards?
Formal review
Inspection
Audit
Walkthrough
Control issues may involve:
Lack of resources
Testing delays
Poor communication
All of the above
Testing is considered complete when:
Exit criteria are met
Developer approves
No defects remain
Customer stops calling
A configuration audit ensures:
All approved versions are stored correctly
Automation is removed
Testers debug the code
Deployment stops
Defect priority indicates:
How quickly it should be fixed
Who introduced the error
User impact
Code complexity
Review metrics measure:
Review effort and defect rate
UI theme
Code architecture
Software installation
Monitoring improves:
Control and decision-making
Social marketing
UI animation
Hardware updates
