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






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






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






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






5. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






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






9. A table showing combinations of inputs and their associated actions.






10. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






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. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






15. Ability of software to provide appropriate performance relative to amount of resources used.






16. Calculates the number of executed branch outcomes in code.






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






18. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






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






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






23. Deviation of a software system from its expected delivery services or results






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






25. Human action that generates an incorrect result.






26. Combining components or sytems into larger structural units or subsystems.






27. Component - Integration - System - Acceptance






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






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






30. Tools used to store and manage incidents return phone defects failures or anomalies.






31. Used to replace a component that calls another component.






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






33. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






36. Conditions required to begin testing activities.






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






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






39. Allows storage of test input and expected results in one or more central data sources or databases.






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






41. Informal testing technique in which test planning and execution run in parallel






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






43. Software products or applications designed to automate manual testing tasks.






44. Waterfall iterative-incremental "V"






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






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






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






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






49. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






50. A unique identifier for each incident report generated during test execution.