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. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.






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






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






5. Test case design






6. executing the software






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






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






9. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






29. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






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






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






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






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






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






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. Approach to doing something that generally give good results when applied appropriately and thoughfully






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






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






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






45. Computer Aided Software Testing






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






47. Testing software through executing it.






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






49. The testing of individual software components.






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests