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. Linear Code Sequence and Jump.






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






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






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






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






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






7. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






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






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






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






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






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






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






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






15. Testing an integrated system to validate it meets requirements






16. Waterfall iterative-incremental "V"






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






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






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






20. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






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. A table showing combinations of inputs and their associated actions.






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






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






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






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






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






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






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






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






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






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






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






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






37. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






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






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






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






43. One defect prevents the detection of another.






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






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






46. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






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






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






49. Component - Integration - System - Acceptance






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