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. Process used to create a SW product from initial conception to public release






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






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






4. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






5. A technique used to improve testing coverage by deliberately introducing faults in code.






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






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






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






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






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






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






12. Conditions required to begin testing activities.






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






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






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






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






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






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






19. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






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






22. Find defects in code while the software application being tested is running.






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






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






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






26. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






35. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






44. A review not based on a formal documented procedure






45. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






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






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






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






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






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