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. Special-purpose software used to simulate a component called by the component under test






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






3. Linear Code Sequence and Jump.






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






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






6. Measures amount of testing performed by a collection of test cases






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






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






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






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






11. Actual inputs required to execute a test case






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






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






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






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






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






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






18. A task of maintaining and controlling changes to all entities of a system.






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






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






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






22. Human action that generates an incorrect result.






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






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






25. Occurrences that happen before and after an unexpected event






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






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






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






29. Informal testing technique in which test planning and execution run in parallel






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






31. Testing an integrated system to validate it meets requirements






32. Response of the application to an input






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






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






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






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






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






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






39. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






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






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






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






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






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. Combining components or sytems into larger structural units or subsystems.






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






49. Tools used to store and manage incidents return phone defects failures or anomalies.






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