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. Human action that generates an incorrect result.






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






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






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






5. All possible combinations of input values and preconditions are tested.






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






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






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






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






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






11. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






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






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






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






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






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






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






19. Actual inputs required to execute a test case






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






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






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






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






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






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






26. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






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






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






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






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






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






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






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






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






38. Response of the application to an input






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






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






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






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






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






44. Special-purpose software used to simulate a component called by the component under test






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






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






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






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






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






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