Test your basic knowledge |

Software Testing And Qa

Subject : it-skills
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 testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations






2. A black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table






3. Informal method of usability inspection in the field of human-computer interaction. identifying the usability problems . involves evaluators examining the interface and judging its compliance






4. Testing software through executing it.






5. The process of testing to determine the interoperability of a software product






6. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing






7. A white box test design technique in which test cases are designed to execute decision outcomes






8. An approach to integration testing where the lowest level components are tested first - then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.






9. Provide critical information during project






10. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.






11. The totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs." defined by ISO 8402 1986






12. Kind of unit testing - internal working of software






13. Testing in which the action of a test case is parameterized by externally defined data values - maintained as a file or spreadsheet. A common technique in Automated Testing






14. This term refers to making software specifically designed for a specific locality






15. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes






16. Similar to black box testing - structure of test cases in order to find defects and its strutured






17. A white box test design technique in which test cases are designed to execute branches.






18. A scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested.






19. Designing tests based on objectives derived from the architectural or detail design of the software (e.g. - tests that execute specific invocation paths or probe the worst case behaviour of algorithms).






20. Stakeholder stakeholder satisfaction with test results report






21. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs






22. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.






23. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.






24. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.






25. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers






26. Testing a system or an Application on the fly - i.e just few tests here and there to ensure the system or an application does not crash out






27. Once the alpha phase is complete development enters the beta phase. Versions of the software known as beta-versions are released to a limited audience outside of the company to ensure that the product has few faults or bugs. black box






28. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned






29. Testing using input values that should be rejected by the component or system






30. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.






31. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]






32. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






33. An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.






34. An anomaly or flaw in a delivered work product. found during early lifecycle phases A defect can be any kind of issue you want tracked and resolved.






35. Black-box tests conducted once the software has been integrated






36. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration






37. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.






38. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.






39. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)






40. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or






41. A white box testing technique that exercises program loops






42. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database






43. Application Under Test






44. executing the software






45. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm






46. Testing one particular module - functionality heavily






47. A test case design technique for a component in which test cases are designed which include representatives of boundary values - the defined limits of an output domain.






48. Coverage testing is concerned with the degree to which test cases exercise or cover the logic (source code) of the software module or unit. It is also a measure of coverage of code lines & code branches and code branch combinations






49. A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification






50. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.