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 code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






2. Waterfall iterative-incremental "V"






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






4. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






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






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






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






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






10. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






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






15. Conditions required to begin testing activities.






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






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






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






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






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






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






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






23. One defect prevents the detection of another.






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






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






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






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






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






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






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. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






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






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






36. Human action that generates an incorrect result.






37. Component - Integration - System - Acceptance






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






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






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






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






42. A document that provides the structure for writing test cases.






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






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






45. A review not based on a formal documented procedure






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






47. Testing an integrated system to validate it meets requirements






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






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






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