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. Testing which covers all combinations of input values and preconditions for an element of the software under test






2. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






13. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)






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






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






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






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






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






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






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






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






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






23. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs






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






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






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






27. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






34. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






43. The testing of individual software components.






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






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






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






47. Stakeholder stakeholder satisfaction with test results report






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






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






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