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. Based on analysis of functional specifications of a system.






2. Conditions required to begin testing activities.






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






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






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






6. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






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






10. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






12. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






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






16. A review not based on a formal documented procedure






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






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






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






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






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






22. One defect prevents the detection of another.






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






24. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






36. Testing software in its operational environment






37. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






39. A table showing combinations of inputs and their associated actions.






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






41. Linear Code Sequence and Jump.






42. Occurrences that happen before and after an unexpected event






43. Tools used to store and manage incidents return phone defects failures or anomalies.






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






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






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






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






48. Actual inputs required to execute a test case






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests