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. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






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






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






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






7. Occurrences that happen before and after an unexpected event






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






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






10. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






26. Linear Code Sequence and Jump.






27. Used to test the functionality of software as mentioned in software requirement specifications.






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






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






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






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






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






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






34. Input or combination of inputs required to test software.






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






36. A set of conditions that a system needs to meet in order to be accepted by end users






37. A review not based on a formal documented procedure






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






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






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






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






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






43. Human action that generates an incorrect result.






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






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






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






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






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






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






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