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






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






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






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






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






6. The process of testing to determine the efficiency of a software product






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






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






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






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






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






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






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






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






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






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






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






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






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






20. Kind of unit testing - internal working of software






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






22. Testing one particular module - functionality heavily






23. The testing of individual software components.






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






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






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






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






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






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






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






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






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






34. Can't see - test the functional testing - no access to code and testing is done on UI






35. Test case design






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






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






38. executing the software






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






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






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






42. A white box testing technique that exercises program loops






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






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






45. Computer Aided Software Testing






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






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






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






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






50. Stakeholder stakeholder satisfaction with test results report






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