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. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






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






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






4. One defect prevents the detection of another.






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






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






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






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






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






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






11. Linear Code Sequence and Jump.






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






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






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






15. Testing an integrated system to validate it meets requirements






16. Conditions required to begin testing activities.






17. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






20. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






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






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






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






33. A review not based on a formal documented procedure






34. Occurrences that happen before and after an unexpected event






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






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






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






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






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






40. Severity - Priority






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






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






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






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






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






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






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






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






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






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