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. The process of testing to determine the efficiency of a software product






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






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






4. Computer Aided Software Testing






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






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






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






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






9. Kind of unit testing - internal working of software






10. Application Under Test






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






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






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






14. executing the software






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






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






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






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






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






20. Test case design






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






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






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






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






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






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






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






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






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






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






31. Testing concerned with the accuracy of documentation.






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






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. Testing whether the system meets its specified objectives for maintainability.






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






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






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






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






39. The testing of individual software components.






40. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






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






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






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