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 expected results or performance characteristics that define whether the test cases passed or failed






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 test suite that exercises the full functionality of a product but does not test features in detail






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






28. A white box testing technique that exercises program loops






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






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






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






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






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






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






35. Kind of unit testing - internal working of software






36. Computer Aided Software Testing






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






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






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






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






41. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs






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






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






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






45. Application Under Test






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






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






48. Testing concerned with the accuracy of documentation.






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






50. Testing one particular module - functionality heavily







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