Explore the 'Testing knowledge ISTQB 1' quiz, designed to assess key competencies in software testing and quality assurance. Topics include boundary value testing, non-functional testing methods, and automation of regression tests, aligning with ISTQB standards.
System testing
Usability testing
Performance testing
Both b & c
Rate this question:
Data tester
Boundary tester
Capture/Playback
Output comparator
Rate this question:
Statement Coverage
Pole Coverage
Condition Coverage
Path Coverage
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:
Quality is job one
Zero defects
Conformance to requirements
Work as designed
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:
Lack of technical documentation
Lack of test tools on the market for developers
Lack of training
Lack of Objectivity
Rate this question:
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:
2 Test Cases
3 Test Cases
4 Test Cases
Not achievable
Rate this question:
Requirements
Design
Code
Decision table
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:
Statement and branch testing
Usability testing
Security testing
Performance testing
Rate this question:
Missing Statements
Unused Branches
Dead Code
Unused Statement
Rate this question:
Defects
Trends analysis
Test Effectiveness
Time Spent Testing
Rate this question:
Component testing
Non-functional system testing
User acceptance testing
Maintenance testing
Rate this question:
Test Analysis and Design
Test Planning and control
Test Implementation and execution
Evaluating exit criteria and reporting
Rate this question:
ReTesting
Confirmation Testing
Regression Testing
Negative Testing
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:
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:
State transition testing
LCSAJ (Linear Code Sequence and Jump)
Syntax testing
Boundary value analysis
Rate this question:
Ii,iii,iv are correct and i is incorrect
Iii , i , iv is correct and ii is incorrect
I , iii , iv , ii is incorrect
Ii is correct
Rate this question:
Specifications
Test Cases
Test Data
Test Design
Rate this question:
Statement coverage is 4
Statement coverage is 1
Statement coverage is 3
Statement coverage is 2
Rate this question:
The goal / purpose of testing is to demonstrate that the program works.
The purpose of testing is to demonstrate that the program is defect free
The purpose of testing is to demonstrate that the program does what it is supposed to do
Testing is executing Software for the purpose of finding defects
Rate this question:
Top down
Big-bang
Bottom up
Functional incrementation
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:
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:
Test recording.
Test planning.
Test configuration.
Test specification.
Rate this question:
Linkage of customer requirements to version numbers.
Facilities to compare test results with expected results.
The precise differences in versions of software component source code.
Restricted access to the source code library.
Rate this question:
An error
A fault
A failure
A defect
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:
Performance testing
Unit testing
Regression testing
Sanity testing
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:
Boundary value analysis
Equivalence partitioning
Decision table testing
State transition testing
Rate this question:
Performance testing
Unit testing
Business scenarios
Static testing
Rate this question:
Unit testing
Regression testing
Alpha testing
Integration testing
Rate this question:
Define when to stop testing
End of test level
When a set of tests has achieved a specific pre condition
All of the above
Rate this question:
Supplier issues
Organization factors
Technical issues
Error-prone software delivered
Rate this question:
Only Project risks
Only Product risks
Project risks and Product risks
Project risks or Product risks
Rate this question:
Tools and techniques
Procedures and standards
Processes and walkthroughs
Reviews and update
Rate this question:
Finding defects
Gaining confidence about the level of quality and providing information
Preventing defects
Debugging defects
Rate this question:
Open, Assigned, Fixed, Closed
Open, Fixed, Assigned, Closed
Assigned, Open, Closed, Fixed
Assigned, Open, Fixed, Closed
Rate this question:
Reliability
Usability
Scalability
Maintainability
Rate this question:
Early testing
Defect clustering
Pesticide paradox
Exhaustive testing
Rate this question:
0,1,2,99
1, 99, 100, 98
0, 1, 99, 100
–1, 0, 1, 99
Rate this question:
Planning and control
Test closure activities
Analysis and design
None
Rate this question:
Check the memory leaks
Check the robustness
Check the branch coverage
Check the decision tables
Rate this question:
Plan, Do, Check, Act
Plan, Do, Correct, Act
Plan, Debug, Check, Act
Plan, Do, Check, Accept
Rate this question:
Quiz Review Timeline (Updated): Mar 22, 2023 +
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.