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. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






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






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






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






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






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






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






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






12. Special-purpose software used to simulate a component that calls the component under test






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






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






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






16. Testing software in its operational environment






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. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






20. Waterfall iterative-incremental "V"






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






22. The capability of a software product to provide agreed and correct output with the required degree of precision






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






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






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






26. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






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






29. Linear Code Sequence and Jump.






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






31. Response of the application to an input






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






33. Conditions required to begin testing activities.






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






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






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






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






38. Insertion of additional code in the existing program in order to count coverage items.






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






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






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






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






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






44. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






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






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






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






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