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. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






3. Actual inputs required to execute a test case






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






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






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






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






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






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






10. Response of the application to an input






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






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






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






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






15. Testing performed to determine whether the system meets acceptance criteria






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






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






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






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






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






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






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






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






24. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






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






26. An event or item that can be tested using one or more test cases






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






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






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






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






31. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






42. Human action that generates an incorrect result.






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






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






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






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






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






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






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






50. Develop & proiroitize test cases Create groups of test cases Set up test environment







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