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. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






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






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






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






7. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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






16. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






38. Human action that generates an incorrect result.






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






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






41. Actual inputs required to execute a test case






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






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






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






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






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






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






48. A review not based on a formal documented procedure






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






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