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. Integration approach components or subsystems are combined all at once rather than in stages.






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






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






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






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






6. Linear Code Sequence and Jump.






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






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






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






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






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






12. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






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






24. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






26. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






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






38. Allows storage of test input and expected results in one or more central data sources or databases.






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






40. Software products or applications designed to automate manual testing tasks.






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






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






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






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






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






46. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






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






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






50. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons