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. Testing an integrated system to validate it meets requirements






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






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






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






5. Waterfall iterative-incremental "V"






6. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






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






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






18. Tools used to identify and calculate coverage items in program code.






19. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






22. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






32. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






41. One defect prevents the detection of another.






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






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






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






45. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






47. A review not based on a formal documented procedure






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






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






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