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. Stakeholder stakeholder satisfaction with test results report






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






3. Computer Aided Software Testing






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






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






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






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






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






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






10. Testing software through executing it.






11. Designing tests based on objectives derived from the architectural or detail design of the software (e.g. - tests that execute specific invocation paths or probe the worst case behaviour of algorithms).






12. Testing concerned with the accuracy of documentation.






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






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






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






16. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






34. Test case design






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






36. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






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






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






49. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers






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