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. Human action that generates an incorrect result.






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






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






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






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






6. Response of the application to an input






7. Occurrences that happen before and after an unexpected event






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






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






10. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






11. Conditions required to begin testing activities.






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






13. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






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






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






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






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






27. Based on analysis of functional specifications of a system.






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






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






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






31. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






32. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






35. One defect prevents the detection of another.






36. Insertion of additional code in the existing program in order to count coverage items.






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






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






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






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






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






42. All possible combinations of input values and preconditions are tested.






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






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






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






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






47. Special additions or changes to the environment required to run a test case.






48. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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







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