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. The capability of a software product to provide agreed and correct output with the required degree of precision






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






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






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






5. Special-purpose software used to simulate a component called by the component under test






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






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






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






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






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






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






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






13. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






20. Conditions required to begin testing activities.






21. The process of finding analyzing and removing causes of failure in a software product.






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






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






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






25. Process used to create a SW product from initial conception to public release






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






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






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






29. Linear Code Sequence and Jump.






30. One defect prevents the detection of another.






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






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






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






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






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






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






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






38. Human action that generates an incorrect result.






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






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






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






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






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






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






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






46. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






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






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






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