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 are integrated in the order in which they are developed






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






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






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






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






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






7. Waterfall iterative-incremental "V"






8. Find defects in code while the software application being tested is running.






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






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






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






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






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






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






15. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






28. Severity - Priority






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






30. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






31. Conditions required to begin testing activities.






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






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






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






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






36. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






37. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






38. One defect prevents the detection of another.






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






40. Special-purpose software used to simulate a component that calls the component under test






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






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






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






44. Linear Code Sequence and Jump.






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






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






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. Software products or applications designed to automate manual testing tasks.






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






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