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. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.






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






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






4. Testing software through executing it.






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






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






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. Determine whether a system meets some specified standard. external organization as complying with the standard






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






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






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






12. Application Under Test






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






14. A white box testing technique that exercises program loops






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






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






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






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






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






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






21. Provide critical information during project






22. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






39. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






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