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. Requirements that determine the functionality of a software system.






2. Actual inputs required to execute a test case






3. A set of conditions that a system needs to meet in order to be accepted by end users






4. Tests interfaces between components and between integrated components and systems.






5. Waterfall iterative-incremental "V"






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






7. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






8. Special additions or changes to the environment required to run a test case.






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. Linear Code Sequence and Jump.






12. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






13. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






14. Black-box test design technique - test cases are designed from a decision table.






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






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






17. 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






18. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






20. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






21. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






22. Process used to create a SW product from initial conception to public release






23. Testing an integrated system to validate it meets requirements






24. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






25. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






26. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






30. Components are integrated in the order in which they are developed






31. Integration approach components or subsystems are combined all at once rather than in stages.






32. Conditions required to begin testing activities.






33. A component of the incident report that determines the actual effect of the incident on the software and its users.






34. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






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






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






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






38. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






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






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






41. Human action that generates an incorrect result.






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






43. A review not based on a formal documented procedure






44. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






45. Testing software in its operational environment






46. Measures amount of testing performed by a collection of test cases






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






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






49. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






50. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first