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. Sequence in which instructions are executed through a component or system






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






20. Testing software in its operational environment






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






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






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






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






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






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






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






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






29. Component - Integration - System - Acceptance






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. Tools used to identify and calculate coverage items in program code.






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






33. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






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






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






38. A review not based on a formal documented procedure






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






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






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






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






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






44. Waterfall iterative-incremental "V"






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






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






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






48. Response of the application to an input






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






50. Linear Code Sequence and Jump.