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. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






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






4. A review not based on a formal documented procedure






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






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






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






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






9. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






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






11. Examine changes made to an operational system cause defects.






12. Occurrences that happen before and after an unexpected event






13. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






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






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






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






21. One defect prevents the detection of another.






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






23. Component - Integration - System - Acceptance






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






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






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






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






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






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






30. Severity - Priority






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






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






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






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






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






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






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






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






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






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






41. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






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






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






46. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






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






48. Waterfall iterative-incremental "V"






49. Actual inputs required to execute a test case






50. Specific groups that represent a set of valid or invalid partitions for input conditions.