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. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






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






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






14. Sequence in which instructions are executed through a component or system






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






16. Conditions required to begin testing activities.






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






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






19. Testing an integrated system to validate it meets requirements






20. A functional testing approach in which test cases are designed based on business processes.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






36. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






44. A table showing combinations of inputs and their associated actions.






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






46. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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