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. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






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






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






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






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






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






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






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






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






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






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






15. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






16. Component - Integration - System - Acceptance






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






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






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






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






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






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






23. A review not based on a formal documented procedure






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






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






26. Response of the application to an input






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






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






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






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






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






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






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






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






35. Used to replace a component that calls another component.






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






37. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






47. A component of the incident report that determines the actual effect of the incident on the software and its users.






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






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






50. Occurrences that happen before and after an unexpected event







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests