Software Testing Practice Test-1
Software Testing Practice Test-1
- 1.1.Software testing activities should start
- A.
A. as soon as the code is written
- B.
B. during the design stage
- C.
C. when the requirements have been formally documented
- D.
D. as soon as possible in the development life cycle
- 2.2.Faults found by users are due to:
- A.
A. Poor quality software
- B.
B. Poor software and poor testing
- C.
C. bad luck
- D.
D. insufficient time for testing
- 3.3.What is the main reason for testing software before releasing it?
- A.
A. to show that system will work after release
- B.
B. to decide when the software is of sufficient quality to release
- C.
C. to find as many bugs as possible before release
- D.
D. to give information for a risk based decision about release
- 4.4. which of the following statements is not true
- A.
A. performance testing can be done during unit testing as well as during the testing of whole system
- B.
B. The acceptance test does not necessarily include a regression test
- C.
C. Verification activities should not involve testers (reviews, inspections etc)
- D.
D. Test environments should be as similar to production environments as possible
- 5.5. When reporting faults found to developers, testers should be:
- A.
A. as polite, constructive and helpful as possible
- B.
B. firm about insisting that a bug is not a “feature” if it should be fixed
- C.
C. diplomatic, sensitive to the way they may react to criticism
- D.
D. All of the above
- 6.6.In which order should tests be run?
- A.
A. the most important tests first
- B.
B. the most difficult tests first(to allow maximum time for fixing)
- C.
C. the easiest tests first(to give initial confidence)
- D.
D. the order they are thought of
- 7.7. The later in the development life cycle a fault is discovered, the more expensive it is to fix. why?
- A.
A. the documentation is poor, so it takes longer to find out what the software is doing.
- B.
B. wages are rising
- C.
C. the fault has been built into more documentation,code,tests, etc
- D.
D. None of the above
- 8.8. Which is not true-The black box tester
- A.
A. should be able to understand a functional specification or requirements document
- B.
B. should be able to understand the source code.
- C.
C. is highly motivated to find faults
- D.
D. is creative to find the system’s weaknesses
- 9.9. A test design technique is
- A.
A. a process for selecting test cases
- B.
B. a process for determining expected outputs
- C.
C. a way to measure the quality of software
- D.
D. a way to measure in a test plan what has to be done
- 10.10. Testware(test cases, test dataset)
- A.
A. needs configuration management just like requirements, design and code
- B.
B. should be newly constructed for each new version of the software
- C.
C. is needed only until the software is released into production or use
- 11.11. An incident logging system
- A.
A only records defects
- B.
B is of limited value
- C.
C is a valuable source of project information during testing if it contains all incidents
- D.
D. should be used only by the test team.
- 12.12. Increasing the quality of the software, by better development methods, will affect the time needed for testing (the test phases) by:
- A.
A. reducing test time
- B.
B. no change
- C.
C. increasing test time
- 13.13. Coverage measurement
- A.
A. is nothing to do with testing
- B.
B. is a partial measure of test thoroughness
- C.
C. branch coverage should be mandatory for all software
- D.
D. can only be applied at unit or module testing, not at system testing
- 14.14. When should you stop testing?
- A.
A. when time for testing has run out.
- B.
B. when all planned tests have been run
- C.
C. when the test completion criteria have been met
- D.
D. when no faults have been found by the tests run
- 15.15. Which of the following is true?
- A.
A. Component testing should be black box, system testing should be white box.
- B.
B. if u find a lot of bugs in testing, you should not be very confident about the quality of software
- C.
C. the fewer bugs you find,the better your testing was
- D.
D. the more tests you run, the more bugs you will find.
- 16.16. What is the important criterion in deciding what testing technique to use?
- A.
A. how well you know a particular technique
- B.
B. the objective of the test
- C.
C. how appropriate the technique is for testing the application
- D.
D. whether there is a tool to support the technique
- 17.17. If the pseudo code below were a programming language ,how many tests are required to achieve 100% statement coverage? 1.If x=3 then 2. Display_messageX; 3. If y=2 then 4. Display_messageY; 5.Else 6.Display_messageZ; 7.Else 8.Display_messageZ;
- A.
A. 1
- B.
B. 2
- C.
C. 3
- D.
D. 4
- 18.18. Regression testing should be performed: v) every week w) after the software has changed x) as often as possible y) when the environment has changed z) when the project manager says
- A.
A) v & w are true, x, y & z are false
- B.
B) w, x & y are true, v & z are false
- C.
C) w & y are true, v, x & z are false
- D.
D) w is true, v, x, y & z are false
- 19.19 Which of the following is NOT a type of non-functional test?
- A.
A. State-Transition
- B.
B. Usability
- C.
C. Performance
- D.
D. Security
- 20.20. Which of the following tools would you use to detect a memory leak?
- A.
A. State analysis
- B.
B. Coverage analysis
- C.
C. Dynamic analysis
- D.
D. Memory analysis
- 21.21. What is the purpose of a test completion criterion?
- A.
A) to know when a specific test has finished its execution
- B.
B) to ensure that the test case specification is complete
- C.
C) to set the criteria used in generating test inputs
- D.
D) to determine when to stop testing
- 22.22. Given the following code, which statement is true about the minimum number of test cases required for full statement and branch coverage? Read p Read q IF p+q > 100 THEN Print “Large” ENDIF IF p > 50 THEN Print “p Large” ENDIF
- A.
A) 1 test for statement coverage, 3 for branch coverage
- B.
B) 1 test for statement coverage, 2 for branch coverage
- C.
C) 1 test for statement coverage, 1 for branch coverage
- D.
D) 2 tests for statement coverage, 2 for branch coverage
- 23.23. Functional system testing is:
- A.
A) testing that the system functions with other systems
- B.
B) testing that the components that comprise the system function together
- C.
C) testing the end to end functionality of the system as a whole
- D.
D) testing the system performs functions within specified response times
- 24.24. What can static analysis NOT find?
- A.
A) the use of a variable before it has been defined
- B.
B) unreachable (“dead”) code
- C.
C) memory leaks
- D.
D) array bound violations
- 25.25. A typical commercial test execution tool would be able to perform all of the following, EXCEPT:
- A.
A) calculating expected outputs
- B.
B) comparison of expected outcomes with actual outcomes
- C.
C) recording test inputs
- D.
D) reading test values from a data file
Questions: 20 | Attempts: 3386 | Last updated: Feb 2, 2018
-
Sample QuestionWho are the project stakeholders?
Questions: 15 | Attempts: 3317 | Last updated: Sep 26, 2017
-
Sample QuestionThe testing which is done by going through the code is known as,
Questions: 9 | Attempts: 2656 | Last updated: Feb 4, 2016
-
Sample QuestionWhich of the following artifacts can be examined by using review techniques?
Back to top