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. A unique identifier for each incident report generated during test execution.






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






3. Testing an integrated system to validate it meets requirements






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






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






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






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






8. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






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






11. Conditions required to begin testing activities.






12. Human action that generates an incorrect result.






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






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






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






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






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






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






19. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






44. Testing software in its operational environment






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






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






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






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






49. Actual inputs required to execute a test case






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






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests