This QUIZ gives you a clear idea on how the questions are asked from Testing Fundamentals which would help you to think and sharpen your knowledge on Testing Fundamentals.
. 0,1900,2004,2005
1900, 2004
1899,1900,2004,2005
1899, 1900, 1901,2003,2004,2005
System testing
Usability testing
Performance testing
Both b & c
Data tester
Boundary tester
Capture/Playback
Output comparator.
Statement Coverage
Pole Coverage
Condition Coverage
Path Coverage
Stub
Driver
Proxy
None of the above
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
Quality is job one
Zero defects
Conformance to requirements
Work as designed
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
Lack of technical documentation
Lack of test tools on the market for developers
Lack of training
Lack of Objectivity
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
Requirements
Design
Code
Decision Table
Impossible to answer
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
Statement and Branch Testing
Usability Testing
Security Testing
Performance Testing
Done by the Developer
Done by Test Engineers
Done by Management
Done by an Entity Outside the Project’s sphere of influence
Testing is the same as quality assurance
Testing is a part of quality assurance
Testing is not a part of quality assurance
Testing is same as debugging
Because testing is good method to make there are not defects in the software
Because verification and validation are not enough to get to know the quality of the software
Because testing measures the quality of the software system and helps to increase the quality
Because testing finds more defects than reviews and inspections.
I, II and III are correct
I is correct
I, III and IV are correct
I, II and IV are correct
The test manager should do only automated regression testing.
The test manager is justified in her decision because no bug has been fixed in other modules
The test manager should only do confirmation testing. There is no need to do regression testing
Regression testing should be done on other modules as well because fixing one module may affect other modules
1, 2, capacity -1, capacity, capacity plus 1
0, 1, capacity, capacity plus 1
0, 1, 2, capacity plus 1, a very large number
0, 1, 10, 100, capacity, capacity plus one
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
Because it is an industry standard
Because errors are frequently made during programming of the different cases near the ‘edges’ of the range of values
Because only equivalence classes that are equal from a functional point of view are considered in the test cases
Because the test object is tested under maximal load up to its performance limits
Number of detected defects, testing cost;
Number of residual defects in the test object.
Percentage of completed tasks in the preparation of test environment; test cases prepared
Number of test cases run / not run; test cases passed / failed
None of the above
Less than 1, 1 through 15, more than 15
Negative numbers, 1 through 15, above 15
Less than 1, 1 through 14, more than 15
Less than 0, 1 through 14, 15 and more
As there are many different ways to test software, thought must be given to decide what will be the most effective way to test the project on hand.
Starting testing without prior planning leads to chaotic and inefficient test project
A strategy is needed to inform the project management how the test team will schedule the test-cycles
Software failure may cause loss of money, time, business reputation, and in extreme cases injury and death. It is therefore critical to have a proper test strategy in place.
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.