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. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






3. Response of the application to an input






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






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






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






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






8. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






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






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






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






13. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






21. Severity - Priority






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






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






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






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






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






27. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






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






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






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






32. Occurrences that happen before and after an unexpected event






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






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






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






36. Testing software in its operational environment






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






38. Human action that generates an incorrect result.






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






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






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






42. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






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






47. Testing an integrated system to validate it meets requirements






48. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






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






50. Components are integrated in the order in which they are developed