.
Regression testing
Integration testing
User acceptance testing
Incidents should always be fixed
An incident occurs when expected and actual results differ
Incidents can be analyzed to assist in test process improvement.
An incident can be raised against documentation
An Error
A fault
A defect
A failure
Testing to see where the system does not function correctly
Testing quality attributes of the system including performance and usability
Testing a system function using only the software required for that function
Testing for functions that should not exist
Updating tests when the software has changed
Testing a released system that has been changed
Testing by users to ensure that the system meets a business need
Testing to maintain business advantage
Is not important
Increases the later a fault is found
Decreases the later a fault is found
Can never be determined
Requirements
Code
Design
Decision Table
System testing
Usability testing
Performance testing
Both B & C
Post-release testing by end user representatives at the developer’s site.
The first testing that is performed.
Pre-release testing by end user representatives at the developer’s site.
Pre-release testing by end user representatives at their sites.
Test Recording
Test Planning
Test configuration
Test Specification
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.