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. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.






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






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






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






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






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






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






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






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






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






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






12. Provide critical information during project






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






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






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






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






17. Test case design






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






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






20. A white box testing technique that exercises program loops






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






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






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






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






25. executing the software






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






44. Application Under Test






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






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






47. Testing concerned with the accuracy of documentation.






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






49. Stakeholder stakeholder satisfaction with test results report






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