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. It is a whole - is the whole process form review to plans strategy and whole thing






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






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






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






5. Test case design






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






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






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






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






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






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






12. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.






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






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






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






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






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






18. Testing one particular module - functionality heavily






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






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






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






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






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






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






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






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






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






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






29. Provide critical information during project






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






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






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






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. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing






35. Testing software through executing it.






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. Similar to black box testing - structure of test cases in order to find defects and its strutured






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






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






40. Application Under Test






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






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






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






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






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






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






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






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






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






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