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. The ratio between the number of defects found and the size of the component/system tested.






2. Waterfall iterative-incremental "V"






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






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






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






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






7. Testing software components that are separately testable. Also module program and unit testing.






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






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






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






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






12. One defect prevents the detection of another.






13. Severity - Priority






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






15. The process of finding analyzing and removing causes of failure in a software product.






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






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






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






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






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






21. Testing performed to determine whether the system meets acceptance criteria






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






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






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






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






26. A functional testing approach in which test cases are designed based on business processes.






27. Tools used to identify and calculate coverage items in program code.






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






29. The smallest software item that can be tested in isolation.






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






31. Response of the application to an input






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






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






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






35. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






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






37. Component - Integration - System - Acceptance






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






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






40. Actual inputs required to execute a test case






41. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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






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






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






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






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






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