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. An event or item that can be tested using one or more test cases






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






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






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






5. Deviation of a software system from its expected delivery services or results






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






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






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






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






10. Testing software components that are separately testable. Also module program and unit testing.






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






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






13. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






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






25. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






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






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






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






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






32. Testing an integrated system to validate it meets requirements






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






34. Separation of testing responsibilities which encourages the accomplishment of objective testing






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






36. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






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






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






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






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






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






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






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






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






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






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






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






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






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






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