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. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs






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






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






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






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






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






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






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






9. A white box testing technique that exercises program loops






10. Multi-user testing geared towards determining the effects of accessing the same application code - module or database records. Identifies and measures the level of locking - deadlocking and use of single-threaded code and locking semaphores






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






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. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications






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






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






17. Testing concerned with the accuracy of documentation.






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






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






20. Stakeholder stakeholder satisfaction with test results report






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






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






23. Provide critical information during project






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






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






26. Testing software through executing it.






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






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






29. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices






30. Testing whether the system meets its specified objectives for maintainability.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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