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. Black-box tests conducted once the software has been integrated






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






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






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






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






6. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






23. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






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






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






36. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






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






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






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






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






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






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






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






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






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