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






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






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






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






6. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent






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






8. Testing software through executing it.






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






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






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






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






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






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






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






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






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






18. Test case design






19. Provide critical information during project






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






21. A white box testing technique that exercises program loops






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






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






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






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






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






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






28. The testing of individual software components.






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






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






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






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






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






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






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






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






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






38. Determine whether a system meets some specified standard. external organization as complying with the standard






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






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






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






42. Application Under Test






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






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






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






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






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






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






49. executing the software






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