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. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






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






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






4. Response of the application to an input






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






6. Measures amount of testing performed by a collection of test cases






7. Testing an integrated system to validate it meets requirements






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






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






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






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






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






13. Linear Code Sequence and Jump.






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






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






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






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






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






19. Special-purpose software used to simulate a component that calls the component under test






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






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






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






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






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






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






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






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






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






29. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






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






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






32. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






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






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






36. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






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






39. Severity - Priority






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






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






42. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






45. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






46. Human action that generates an incorrect result.






47. Insertion of additional code in the existing program in order to count coverage items.






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






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






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