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






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






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






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






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






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






7. The process of finding analyzing and removing causes of failure in a software product.






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






9. Response of the application to an input






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






11. Human action that generates an incorrect result.






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






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






14. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






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






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






20. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






42. Tests interfaces between components and between integrated components and systems.






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






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






45. Component - Integration - System - Acceptance






46. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






48. Testing an integrated system to validate it meets requirements






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






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