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. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






2. Sequence in which data items are accessed or modified by code.






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






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






5. Testing software in its operational environment






6. A review not based on a formal documented procedure






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






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






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






10. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






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






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






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






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






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






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






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






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






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






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






23. Component - Integration - System - Acceptance






24. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






25. Components are combined and tested in the order in which basic functionalities start working






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






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






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






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






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






31. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






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






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






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






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






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






39. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






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






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






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