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. Testing software components that are separately testable. Also module program and unit testing.






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






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






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






5. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






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






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






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






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






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






13. Actual inputs required to execute a test case






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






15. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






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






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






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






20. A review not based on a formal documented procedure






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






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






23. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






33. Sequence in which data items are accessed or modified by code.






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






35. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






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






46. Severity - Priority






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






48. Testing an integrated system to validate it meets requirements






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






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







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