Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






2. Testing software in its operational environment






3. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






4. Special-purpose software used to simulate a component called by the component under test






5. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






6. Severity - Priority






7. Events that occurred during the testing process our investigation.






8. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






9. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






10. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






11. Human action that generates an incorrect result.






12. Requirements that determine the functionality of a software system.






13. A document that provides the structure for writing test cases.






14. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






15. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






16. Tools used by developers to identify defects in programs.






17. A task of maintaining and controlling changes to all entities of a system.






18. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






19. A document that records the description of each event that occurs during the testing process and that requires further investigation






20. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






21. Conditions required to begin testing activities.






22. Based on analysis of functional specifications of a system.






23. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






24. Increased load (transations) used to test behavior of system under high volume.






25. Record details of test cases executed Record order of execution record results






26. Operational testing performed at an _external_ site without involvement of the developing organization.






27. Input or combination of inputs required to test software.






28. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






29. Special-purpose software used to simulate a component that calls the component under test






30. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






31. Separation of testing responsibilities which encourages the accomplishment of objective testing






32. The ratio between the number of defects found and the size of the component/system tested.






33. Actual inputs required to execute a test case






34. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






35. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






36. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






37. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






38. The capability of a software product to provide agreed and correct output with the required degree of precision






39. Testing an integrated system to validate it meets requirements






40. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






41. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






42. An analysis that determines the portion of code on software executed by a set of test cases






43. Components are combined and tested in the order in which basic functionalities start working






44. White-box design technique used to design test cases for a software component using LCSAJ.






45. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






46. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






47. Sequence in which instructions are executed through a component or system






48. Black-box testing technique used to create groups of input conditions that create the same kind of output.






49. An event or item that can be tested using one or more test cases






50. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.