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. Approach to doing something that generally give good results when applied appropriately and thoughfully






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






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






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






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






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






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






8. Testing one particular module - functionality heavily






9. executing the software






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






28. An approach to integration testing where the lowest level components are tested first - then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.






29. A white box testing technique that exercises program loops






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






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






32. Kind of unit testing - internal working of software






33. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






34. Testing software through executing it.






35. Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields & Cookie security and Lockout testing . permitting unauthorised access.






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






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






38. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.






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






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






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






42. Application Under Test






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






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






45. Computer Aided Software Testing






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






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






48. Test case design






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






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