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






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






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






4. A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+.






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






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






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






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






9. Testing one particular module - functionality heavily






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






11. Testing in which test cases are designed based on variable usage within the code.






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






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






14. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality






15. The percentage of executable statements that have been exercised by a test suite.






16. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.






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






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






19. A white box testing technique that exercises program loops






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






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






22. Computer Aided Software Testing






23. Kind of unit testing - internal working of software






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






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






26. 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).






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






28. It is a whole - is the whole process form review to plans strategy and whole thing






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






30. A test that exercises a feature of a product in full detail.






31. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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






33. executing the software






34. Stakeholder stakeholder satisfaction with test results report






35. Depends on the schedule and risk based - business impact follow the 20-80 rules






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






37. Approach to doing something that generally give good results when applied appropriately and thoughfully






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






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






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






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






42. Can't see - test the functional testing - no access to code and testing is done on UI






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






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






45. Testing whether the system is compatible with other systems with which it should communicate.






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






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






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






49. Knows about the software and test - no proper plan






50. Root cause analyst - base of the problem - customer satisfaction report