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. Tools used to store and manage incidents return phone defects failures or anomalies.






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






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






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






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






6. A review not based on a formal documented procedure






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






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






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






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






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






12. Occurrences that happen before and after an unexpected event






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






14. Waterfall iterative-incremental "V"






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






16. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






23. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






24. An event or item that can be tested using one or more test cases






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






26. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






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






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






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






33. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






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






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






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






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






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






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






40. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






43. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






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






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






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






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






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






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