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






2. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






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






12. Actual inputs required to execute a test case






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






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






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






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






17. Human action that generates an incorrect result.






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






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






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






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






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






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






24. One defect prevents the detection of another.






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






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






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






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






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






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. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






32. A review not based on a formal documented procedure






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. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






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






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






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






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






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






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






43. Testing software in its operational environment






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






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






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






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






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






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






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






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