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. Testing software through executing it.






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






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






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






5. Test case design






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






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






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






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






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






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






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. The process of testing to determine the efficiency of a software product






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






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






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






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






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






19. Testing the changes to an operational system or the impact of a changed environment to an operational system






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






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






22. A basic block that can be selected for execution based on a program construct in which one of two or more alternative program path is available






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






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






25. An accidental condition that causes the failure of a component in the implementation model to perform its required behavior. A fault is the root cause of one or more defects identified by observing one or more failures.






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






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






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






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






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






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






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






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






34. A test suite that exercises the full functionality of a product but does not test features in detail






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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