Missing statements
Unreachable code
Unused statement
Unused branches
Testing for a business perspective.
Finding faults in the system.
Ensuring that the system is acceptable to all users.
Testing the system with other systems.
True
False
Performed by customers at their own site
Performed by customers at their software developer’s site
Performed by an independent test team
Useful to test bespoke software or Useful to test software developed for a specific customer or user.
Gives quality information about the code without executing it.
Checks expected results against actual results.
Can detect memory leaks.
Gives information about what code has and has not been exercised.
They find different types of defect.
Using more techniques is always better
Both find the same types of defect.
Because specifications tend to be unstructured
They can find defects missed by specification-based and structure-based techniques.
They don't require any training to be as effective as formal techniques.
They can be used most effectively when there are good specifications.
They will ensure that all of the code or system is tested.
Unrealistic expectations, expecting the tool to do too much.
Insufficient reliance on the tool, i.e. still doing manual testing when a test execution tool has been purchased.
The tool may find defects that aren't there.
The tool will repeat exactly the same thing it did the previous time.
Data-driven and keyword-driven
Data-driven and capture-driven
Capture-driven and keyhole-driven
Playback-driven and keyword-driven
True
False
With static analysis, defects can be found that are difficult to find with dynamic testing.
Compiling is not a form of static analysis.
When properly performed, static analysis makes functional testing redundant.
Static analysis finds all faults.
P, Q and R
Q, S and T
P,Q and S
R, S and T
The test plan describes one or more levels of testing, the test design specification identifies the associated high-level test cases and a test procedure specification describes the actions for executing a test.
The test plan is for managers, the test design specification is for programmers and the test procedure specification is for testers who are automating tests.
The test plan is the least thorough, the test procedure specification is the most thorough and the test design specification is midway between the two.
The test plan is finished in the first third of the project, the test design specification is finished in the middle third of the project and the test procedure specification is finished in the last third of the project.
Branch testing
Agile testing
Beta testing
Ad-hoc testing
Open, Assigned, Fixed, Closed
Open, Fixed, Assigned, Closed
Assigned, Open, Closed, Fixed
Assigned, Open, Fixed, Closed
17
19
24
21
True
False
True
False
Inspection.
Walkthrough.
Review
Non Conformance
True
False
Unit, integration, system, validation
System, integration, unit, validation
Unit, integration, validation, system
None of the above
True
False
End Usability License Agreement
End User License Agreement
End User License Arrangement
End User License Attachment
Computer Aided Software Testing
Computer Aided Software Tools
Computer Analysis Software Techniques
None
Incorrect program behaviour due to a fault in the program
Bug found before product Release
Bug found after product Release
Bug found during Design phase
Statement and branch testing
Usability testing
Security testing
Performance testing
Requirements
Design
Code
Decision table
Incorrect program behaviour due to a fault in the program
Bug found before product Release
Bug found after product Release
Bug found during Design phase
Missing Statements
Unused Branches
Dead Code
Unused Statement
Error guessing
Walkthrough
Data flow analysis
Inspections
How much regression testing should be done.
Exit Criteria
How many more test cases need to written.
Different Tools to perform Regression Testing
User Acceptance Test Cases
Integration Level Test Cases
Unit Level Test Cases
Program specifications
Dynamic analysis tool
Static Analysis tool.
Maintenance tool.
Configuration tool.
Deviation from expected result to actual result
Defect in the software.
Error in the program code.
Fault in the system.
Reducing test time
No change
Increasing test time
Can’t say
Code inspection
Coverage analysis
Usability assessment
Installation test
It is led by a trained leader, uses formal entry and exit criteria and checklists
It is led by the author of the document to be inspected
It can only be used for reviewing design and code
It is led by the author, uses checklists, and collects data for improvement
Both functional and non-functional requirements are to be tested
Only functional requirements are tested; non-functional requirements are validated in a review
Only non-functional requirements are tested; functional requirements are validated in a review
Only requirements which are listed in the specification document are to be tested
A walkthrough does not follow a defined process
For a walkthrough individual preparation by the reviewers is optional
A walkthrough requires meeting
A walkthrough finds the causes of failures, while formal review finds the failures
To specify when to stop the testing activity
To set the criteria used in generating test inputs
To ensure that the test case specification is complete
To know when a specific test has finished its execution
A software development model that illustrates how testing activities integrate with software development phases
A software life-cycle model that is not relevant for testing
The official software development and testing life-cycle model of ISTQB
A testing life cycle model including unit, integration, system and acceptance phases
True
False
Reviewing and Inspecting
Inspecting and Testing
Reviewing and Testing
Reviewing, Inspecting and Testing.
Ensure that test cases test each input and output equivalence class at least once
Identify all inputs and all outputs
Identify equivalence classes for each input
All of the above
True
False
Program is tested randomly sampling the input.
A black-box testing technique
Both A. and B.
None of the above.
Road map for testing
Tells about the actual results and expected results
Both a and b
None of the above
Boundary value analysis
Usability testing
Performance testing
Security testing
Quiz Review Timeline (Updated): Mar 22, 2022 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
SuiteBuilder Pre-Session Assessment Quiz | Custom Fields
This pre-session assessment quiz covers Custom Fields in SuiteBuilder, focusing on their application, types, and limitations within business software environments.
Questions:
10 |
Attempts:
27 |
Last updated:
Apr 07, 2023
|
Zoom Quiz Questions And Answers
Are you a frequent user of the Zoom app? If yes, then take this " Zoom Quiz Questions And Answers quiz" to find out some interesting facts about the application....
Questions:
15 |
Attempts:
2483 |
Last updated:
Jul 17, 2023
|
GIT & GitHub Quiz
This is an MCQ quiz to test the basics and essentials of Git & GitHub. Do you think you can pass this GIT & GitHub quiz? Git is a free and open-source software that is for...
Questions:
15 |
Attempts:
9601 |
Last updated:
Feb 13, 2024
|
The Facebook Messenger Quiz! Trivia
Do you know anything about Facebook Messenger? Do you suppose you could pass this quiz? The Facebook business manager is a free tool developed by Facebook to permit businesses...
Questions:
10 |
Attempts:
281 |
Last updated:
Mar 19, 2023
|
Ranorex Certification Trivia Quiz
Ranorex helps with automated testing, and certification in Ranorex is a great way to enrich your CV. You also get benefits like access to a LinkedIn group exclusively for...
Questions:
10 |
Attempts:
474 |
Last updated:
Mar 22, 2023
|
SoapUI Software Trivia Quiz
An open-source web service testing application, SoapUI's functionality covers a wide range including but not limited to inspection, loads and compliance testing, mocking, etc....
Questions:
10 |
Attempts:
265 |
Last updated:
Mar 21, 2023
|
Wait!
Here's an interesting quiz for you.