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. Behavior or response of a software application that you observe when you execute the action steps in the test case.






2. Operational testing performed at an _external_ site without involvement of the developing organization.






3. Testing software in its operational environment






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






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






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






7. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






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






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






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






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






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






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






15. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






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






18. Actual inputs required to execute a test case






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






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






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






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






23. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






24. Response of the application to an input






25. A component of the incident report that determines the actual effect of the incident on the software and its users.






26. One defect prevents the detection of another.






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






28. A review not based on a formal documented procedure






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






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






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






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






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






34. Testing software components that are separately testable. Also module program and unit testing.






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






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






37. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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. Process used to create a SW product from initial conception to public release






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. All possible combinations of input values and preconditions are tested.






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






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