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. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






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






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






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






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






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






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






10. Informal testing technique in which test planning and execution run in parallel






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






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






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






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






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






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






17. Component - Integration - System - Acceptance






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






19. Human action that generates an incorrect result.






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






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






22. An analysis that determines the portion of code on software executed by a set of test cases






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






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






25. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






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






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






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






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






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






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






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






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






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






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






36. Severity - Priority






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






38. Ability of software to provide appropriate performance relative to amount of resources used.






39. Measures amount of testing performed by a collection of test cases






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






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






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






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






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






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






46. Actual inputs required to execute a test case






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






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






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






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