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. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent






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






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






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






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






6. Computer Aided Software Testing






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






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






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






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






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






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






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






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






15. Application Under Test






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






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






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






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






20. A white box testing technique that exercises program loops






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






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






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






24. Test case design






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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