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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






20. Model-based testing refers to software testing where test cases are derived in whole or in part from a model that describes some (usually functional) aspects of the system under test.






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






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






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






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






25. Testing which covers all combinations of input values and preconditions for an element of the software under test






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






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






28. The testing of individual software components.






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






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






31. Computer Aided Software Testing






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






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






34. A white box test case design techniques that uses the algorithmic flow of the program to design tests






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






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






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






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






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






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






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






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






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






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






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






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






47. executing the software






48. Application Under Test






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






50. Provide critical information during project