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






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






3. executing the software






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






5. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.






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






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






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






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






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






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






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






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






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






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






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






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






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






19. Testing one particular module - functionality heavily






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






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






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. Kind of unit testing - internal working of software






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






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






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






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






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






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






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. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.






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






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






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






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






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






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






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






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






40. Application Under Test






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






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






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






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






45. Approach to doing something that generally give good results when applied appropriately and thoughfully






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






47. A service oriented architecture (SOA) is a design model which relies on a collection of loosely coupled self contained services that communicate with each other through the internet and can be called from multiple clients in a standard fashion






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






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






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.