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. A set of conditions that a system needs to meet in order to be accepted by end users






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






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






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






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






6. A review not based on a formal documented procedure






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






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






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






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






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






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






13. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






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






17. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






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






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






21. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






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






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






26. Occurrences that happen before and after an unexpected event






27. Response of the application to an input






28. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






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






31. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






40. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






41. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






45. Components are integrated in the order in which they are developed






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






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






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






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






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