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. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality






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






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






4. Testing one particular module - functionality heavily






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






7. Root cause analyst - base of the problem - customer satisfaction report






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






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






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






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






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






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






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






15. Testing software through executing it.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






35. Computer Aided Software Testing






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






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






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






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






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






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






42. A black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table






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






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






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






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






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






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






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






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