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. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.






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






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






4. Testing software through executing it.






5. Test case design






6. A white box testing technique that exercises program loops






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






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






9. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules






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






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






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






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






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






15. Application Under Test






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






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






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






19. executing the software






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






35. The testing of individual software components.






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






37. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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






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






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






48. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases






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






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