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 metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






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






6. Events that occurred during the testing process our investigation.






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






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






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






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






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






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






13. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






30. All possible combinations of input values and preconditions are tested.






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






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






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






34. Actual inputs required to execute a test case






35. Human action that generates an incorrect result.






36. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






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






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






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






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






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






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






44. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






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






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






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






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






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






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