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. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






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






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






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






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






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






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






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






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






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






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






12. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






13. Waterfall iterative-incremental "V"






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






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






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






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






18. Severity - Priority






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






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






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






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






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






24. Response of the application to an input






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






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






27. Occurrences that happen before and after an unexpected event






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






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






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






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






32. The ratio between the number of defects found and the size of the component/system tested.






33. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






35. Testing an integrated system to validate it meets requirements






36. A unique identifier for each incident report generated during test execution.






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






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






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






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






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






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






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






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






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






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






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






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






49. One defect prevents the detection of another.






50. A review not based on a formal documented procedure