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: A frame or backbone is created and components are progressively integrated into it.






2. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






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






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






7. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






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






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






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






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






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






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






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






18. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






27. Occurrences that happen before and after an unexpected event






28. Actual inputs required to execute a test case






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






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






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






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






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






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






35. Conditions required to begin testing activities.






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






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






38. Waterfall iterative-incremental "V"






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






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






41. One defect prevents the detection of another.






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






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






44. A review not based on a formal documented procedure






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






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






47. Tests interfaces between components and between integrated components and systems.






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






49. Response of the application to an input






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