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. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






2. Waterfall iterative-incremental "V"






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






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






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






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






7. A review not based on a formal documented procedure






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






9. Component - Integration - System - Acceptance






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






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






12. A set of conditions that a system needs to meet in order to be accepted by end users






13. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






14. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






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






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






18. Used to test the functionality of software as mentioned in software requirement specifications.






19. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






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






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






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






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






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






28. Testing an integrated system to validate it meets requirements






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






30. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






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






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






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






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






35. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






37. Severity - Priority






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






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






40. The smallest software item that can be tested in isolation.






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






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






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






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






45. Human action that generates an incorrect result.






46. Occurrences that happen before and after an unexpected event






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






48. Linear Code Sequence and Jump.






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






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







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