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. Testing whether the system is compatible with other systems with which it should communicate.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






22. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)






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






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






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






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






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






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






29. Application Under Test






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






31. Test case design






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






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






34. The percentage of executable statements that have been exercised by a test suite.






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






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






37. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or






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






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






40. Testing one particular module - functionality heavily






41. Testing software through executing it.






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






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






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






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






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






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






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






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






50. Provide critical information during project