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 functional testing approach in which test cases are designed based on business processes.






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






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






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






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






6. Response of the application to an input






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






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






9. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






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






14. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






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






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






17. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






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






29. Waterfall iterative-incremental "V"






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






31. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






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






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






42. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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