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






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






3. Stakeholder stakeholder satisfaction with test results report






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






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






6. Test case design






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






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






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






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






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






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






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






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






15. executing the software






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






17. Testing software through executing it.






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






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






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. Application Under Test






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






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






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






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






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






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






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






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






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






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






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






33. Provide critical information during project






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






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






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






37. Kind of unit testing - internal working of software






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






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






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






41. A white box testing technique that exercises program loops






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






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






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






45. An anomaly or flaw in a delivered work product. found during early lifecycle phases A defect can be any kind of issue you want tracked and resolved.






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






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






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






49. Coverage testing is concerned with the degree to which test cases exercise or cover the logic (source code) of the software module or unit. It is also a measure of coverage of code lines & code branches and code branch combinations






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