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






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






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






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






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






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






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






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






9. Severity - Priority






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






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






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






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






14. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






17. Testing software in its operational environment






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






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






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






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






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






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






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






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






26. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






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






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






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






30. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






34. Input or combination of inputs required to test software.






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






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






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






38. A review not based on a formal documented procedure






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






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






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






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






43. Conditions required to begin testing activities.






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






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






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






47. Occurrences that happen before and after an unexpected event






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






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






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