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. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases






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






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






4. A test that a user/sponsor and manufacturer/producer jointly perform on a finished - engineered product/system through black-box testing - as functional test & beta test & QA test & application test & confidence test & final test or end user test






5. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.






6. A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point - each possible branch be executed at least once.






7. They arise from mistakes and errors made by people in either a program's source code or its design that prevents it from working correctly or produces an incorrect result






8. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).






9. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared and analyzed in cases of discrepancies






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






11. The percentage of decision outcomes that have been exercised by a test suite.






12. Testing one particular module - functionality heavily






13. Application Under Test






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






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






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






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






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






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






20. executing the software






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






22. The process of testing to determine the efficiency of a software product






23. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications






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






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






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






27. The testing of individual software components.






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






29. Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing






30. Stakeholder stakeholder satisfaction with test results report






31. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules






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






33. Defined as any testing that occurs outside of the development environment. installed on. simply appear to be to run a setup program - can be used with confidence






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






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






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






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






38. The expected results or performance characteristics that define whether the test cases passed or failed






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






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






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






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






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






44. Testing software through executing it.






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






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






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






48. Checks for memory leaks or other problems that may occur with prolonged execution






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






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