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. Events that occurred during the testing process our investigation.






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






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






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






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






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






7. An analysis that determines the portion of code on software executed by a set of test cases






8. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






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






20. Severity - Priority






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






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






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






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






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






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






27. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






28. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






30. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






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






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






41. Actual inputs required to execute a test case






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






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






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






45. Human action that generates an incorrect result.






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






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






48. Allows storage of test input and expected results in one or more central data sources or databases.






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests