Software Testing Practice Test-1
A. as soon as the code is written
B. during the design stage
C. when the requirements have been formally documented
D. as soon as possible in the development life cycle
A. Poor quality software
B. Poor software and poor testing
C. bad luck
D. insufficient time for testing
A. to show that system will work after release
B. to decide when the software is of sufficient quality to release
C. to find as many bugs as possible before release
D. to give information for a risk based decision about release
A. performance testing can be done during unit testing as well as during the testing of whole system
B. The acceptance test does not necessarily include a regression test
C. Verification activities should not involve testers (reviews, inspections etc)
D. Test environments should be as similar to production environments as possible
A. as polite, constructive and helpful as possible
B. firm about insisting that a bug is not a “feature” if it should be fixed
C. diplomatic, sensitive to the way they may react to criticism
D. All of the above
A. the most important tests first
B. the most difficult tests first(to allow maximum time for fixing)
C. the easiest tests first(to give initial confidence)
D. the order they are thought of
A. the documentation is poor, so it takes longer to find out what the software is doing.
B. wages are rising
C. the fault has been built into more documentation,code,tests, etc
D. None of the above
A. should be able to understand a functional specification or requirements document
B. should be able to understand the source code.
C. is highly motivated to find faults
D. is creative to find the system’s weaknesses
A. a process for selecting test cases
B. a process for determining expected outputs
C. a way to measure the quality of software
D. a way to measure in a test plan what has to be done
A. needs configuration management just like requirements, design and code
B. should be newly constructed for each new version of the software
C. is needed only until the software is released into production or use
A only records defects
B is of limited value
C is a valuable source of project information during testing if it contains all incidents
D. should be used only by the test team.
A. reducing test time
B. no change
C. increasing test time
A. is nothing to do with testing
B. is a partial measure of test thoroughness
C. branch coverage should be mandatory for all software
D. can only be applied at unit or module testing, not at system testing
A. when time for testing has run out.
B. when all planned tests have been run
C. when the test completion criteria have been met
D. when no faults have been found by the tests run
A. Component testing should be black box, system testing should be white box.
B. if u find a lot of bugs in testing, you should not be very confident about the quality of software
C. the fewer bugs you find,the better your testing was
D. the more tests you run, the more bugs you will find.
A. how well you know a particular technique
B. the objective of the test
C. how appropriate the technique is for testing the application
D. whether there is a tool to support the technique
A. 1
B. 2
C. 3
D. 4
A) v & w are true, x, y & z are false
B) w, x & y are true, v & z are false
C) w & y are true, v, x & z are false
D) w is true, v, x, y & z are false
A. State-Transition
B. Usability
C. Performance
D. Security
A. State analysis
B. Coverage analysis
C. Dynamic analysis
D. Memory analysis
A) to know when a specific test has finished its execution
B) to ensure that the test case specification is complete
C) to set the criteria used in generating test inputs
D) to determine when to stop testing
A) 1 test for statement coverage, 3 for branch coverage
B) 1 test for statement coverage, 2 for branch coverage
C) 1 test for statement coverage, 1 for branch coverage
D) 2 tests for statement coverage, 2 for branch coverage
A) testing that the system functions with other systems
B) testing that the components that comprise the system function together
C) testing the end to end functionality of the system as a whole
D) testing the system performs functions within specified response times
A) the use of a variable before it has been defined
B) unreachable (“dead”) code
C) memory leaks
D) array bound violations
A) calculating expected outputs
B) comparison of expected outcomes with actual outcomes
C) recording test inputs
D) reading test values from a data file
Wait!
Here's an interesting quiz for you.