Testing knowledge ISTBQ 2 evaluates understanding of software testing principles, focusing on boundary values, non-functional testing methods, automation tools, logic coverage, and definitions of quality. This quiz is essential for learners aiming to enhance their software testing skills.
When the code is complete.
When the design is complete.
When the software requirements have been approved.
When the first code module is ready for unit testing
Rate this question:
This question is impossible to answer
This question is easy to answer
The answer depends on the risk for your industry, contract and special requirements
This answer depends on the maturity of your developers
Rate this question:
ReTesting
Confirmation Testing
Regression Testing
Negative Testing
Rate this question:
0,1,2,99
1, 99, 100, 98
0, 1, 99, 100
–1, 0, 1, 99
Rate this question:
Is the same as equivalence partitioning tests
Test boundary conditions on, below and above the edges of input and output equivalence classes
Tests combinations of input circumstances
Is used in white box testing strategy
Rate this question:
Error condition hiding another error condition
Creating a test case which does not reveal a fault
Masking a fault by developer
Masking a fault by a tester
Rate this question:
Only few tests should be run
Testing should be on the basis of Risk
Only Good Test Cases should be executed
Test Cases written by good test engineers should be executed
Rate this question:
Performance testing
Unit testing
Regression testing
Sanity testing
Rate this question:
No, because they apply to development documentation
No, because they are normally applied before testing
Yes, because both help detect faults and improve quality
Yes, because testing includes all non-constructive activities
Rate this question:
Measuring response times
Recovery testing
Simulating many users
Generating many transactions
Rate this question:
Interaction between html pages
Performance on the client side
Security aspects
All of the above
Rate this question:
Quality is job one
Zero defects
Conformance to requirements
Work as designed
Rate this question:
Statement and branch testing
Usability testing
Security testing
Performance testing
Rate this question:
Non-functional requirements only not Functional requirements
Functional requirements only not non-functional requirements
Non-functional requirements and Functional requirements
Non-functional requirements or Functional requirements
Rate this question:
Measuring response times
Recovery testing
Simulating many users
Generating many transactions
Rate this question:
Developers would typically use i and iv; test team ii and iii
Developers would typically use i and iii; test team ii and iv
Developers would typically use ii and iv; test team i and iii
Developers would typically use i, iii and iv; test team ii
Rate this question:
Re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects
Re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed
Re-testing is done after faults are fixed; regression testing is done earlier
Re-testing is done by developers; regression testing is done by independent testers
Rate this question:
Reviews cannot be performed on user requirements specifications.
Reviews are the least effective way of testing code.
Reviews are unlikely to find faults in test plans.
Reviews should be performed on specifications, code, and test plans.
Rate this question:
Find as many faults as possible.
Test high risk areas.
Obtain good test coverage.
Test whatever is easiest to test.
Rate this question:
Lack of technical documentation
Lack of test tools on the market for developers
Lack of training
Lack of Objectivity
Rate this question:
State transition testing
LCSAJ (Linear Code Sequence and Jump)
Syntax testing
Boundary value analysis
Rate this question:
Specifications
Test Cases
Test Data
Test Design
Rate this question:
Reliability
Usability
Scalability
Maintainability
Rate this question:
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
Rate this question:
Testing that the system functions with other systems
Testing that the components that comprise the system function together
Testing the end to end functionality of the system as a whole
Testing the system performs functions within specified response times
Rate this question:
Requirements
Documentation
Test cases
Improvements suggested by users
Rate this question:
Only important in system testing
Only used in component testing
Most useful when specified in advance
Derived from the code
Rate this question:
Requires knowledge on the bug fixes and how it affect the system
Includes the area of frequent defects
Includes the area which has undergone many/recent code changes
All of the above
Rate this question:
Features to be tested
Incident reports
Risks
Schedule
Rate this question:
Unit testing
Regression testing
Alpha testing
Integration testing
Rate this question:
When all the planned tests have been run
When time has run out
When all faults have been fixed correctly
It depends on the risks for the system being tested
Rate this question:
Performed by customers at their own site
Performed by customers at the software developer's site
Performed by an Independent Test Team
Performed as early as possible in the lifecycle
Rate this question:
0,1900,2004,2005
1900, 2004
1899,1900,2004,2005
1899, 1900, 1901,2003,2004,2005
Rate this question:
Missing Statements
Unused Branches
Dead Code
Unused Statement
Rate this question:
Testing that the system functions with other systems
Testing that the components that comprise the system function together
Testing the end to end functionality of the system as a whole
Testing the system performs functions within specified response times
Rate this question:
An error
A fault
A failure
A defect
Rate this question:
Identifying test conditions only, not Identifying test cases
Not Identifying test conditions, Identifying test cases only
Identifying test conditions and Identifying test cases
Identifying test conditions or Identifying test cases
Rate this question:
Performance testing
Unit testing
Business scenarios
Static testing
Rate this question:
To find faults in the software
To prove that the software has no faults
To give confidence in the software
To find performance problems
Rate this question:
Supplements formal test design techniques.
Can only be used in component, integration and system testing.
Is only performed in user acceptance testing.
Is not repeatable and should not be used.
Rate this question:
That you have tested every statement in the program.
That you have tested every statement and every branch in the program.
That you have tested every IF statement in the program.
That you have tested every combination of values of IF statements in the program
Rate this question:
Requirements
Design
Code
Decision table
Rate this question:
Defects
Trends analysis
Test Effectiveness
Time Spent Testing
Rate this question:
System testing
Acceptance testing
Integration testing
Smoke testing
Rate this question:
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.
Rate this question:
Time runs out.
The required level of confidence has been achieved.
No more faults are found.
The users won?t find any serious faults.
Rate this question:
How much regression testing should be done
Exit Criteria
How many more test cases need to written
Different Tools to perform Regression Testing
Rate this question:
The probability the negative event will occur
The potential loss or impact associated with the event
Both a and b
Neither a nor b
Rate this question:
Quiz Review Timeline (Updated): May 9, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
ST IV & V
This quiz titled 'ST IV & V' assesses knowledge in software testing techniques, including boundary value testing, decision coverage, and system integration, tailored for those...
Questions:
10 |
Attempts:
147 |
Last updated:
Sep 07, 2023
|
An Advanced Software Testing Practice Test
The software industry is at it's a more comfortable room, and why would it not be? After all, everything is now connected with softwares. Computers are operating almost every...
Questions:
79 |
Attempts:
1068 |
Last updated:
Mar 22, 2023
|
Do You Know How To Use Appium?
Appium exists to make your mobile app testing a whole lot easier. Use your preferred language and test framework to make the usage of Appium more enjoyable! But first, do you know...
Questions:
10 |
Attempts:
172 |
Last updated:
Mar 15, 2023
|
Software Testing Manual Quiz Questions
This Software Testing Manual Quiz assesses knowledge of common testing concepts and practices. It covers topics such as fault detection, test planning, and regression testing,...
Questions:
10 |
Attempts:
400 |
Last updated:
Sep 25, 2024
|
TestComplete Automation Test Quiz
Its a automated testing platform and today, I'll test you on your knowledge of it. So, care to partake and see where you lie in the hierachie?
Questions:
10 |
Attempts:
333 |
Last updated:
Mar 21, 2023
|
ISTQB- All Chapters Exam7
This ISTQB certification exam tests knowledge across all chapters, focusing on software testing principles and techniques. It assesses skills in test design, test process...
Questions:
40 |
Attempts:
558 |
Last updated:
Mar 21, 2023
|
|
Wait!
Here's an interesting quiz for you.