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






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






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






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






5. Testing one particular module - functionality heavily






6. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






14. A test that exercises a feature of a product in full detail.






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






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






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






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






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






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






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






22. A white box testing technique that exercises program loops






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






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






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






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






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






28. Kind of unit testing - internal working of software






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






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






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






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






33. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






49. Stakeholder stakeholder satisfaction with test results report






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