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






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






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






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






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






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






7. Testing software through executing it.






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






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






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






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






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






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






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






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






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






17. Stakeholder stakeholder satisfaction with test results report






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






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






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






21. Test case design






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






23. executing the software






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






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






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






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






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






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






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






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






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






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






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






35. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






47. The testing of individual software components.






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






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






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