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. Depends on the schedule and risk based - business impact follow the 20-80 rules






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






24. executing the software






25. A service oriented architecture (SOA) is a design model which relies on a collection of loosely coupled self contained services that communicate with each other through the internet and can be called from multiple clients in a standard fashion






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






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






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






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






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






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






32. Kind of unit testing - internal working of software






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






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






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






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






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






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






39. Stakeholder stakeholder satisfaction with test results report






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






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






42. The testing of individual software components.






43. This term refers to making software specifically designed for a specific locality






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






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






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






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






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






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






50. Computer Aided Software Testing