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. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
white box testing
Mutation testing
Interface Testing
enough of testing

2. Root cause analyst - base of the problem - customer satisfaction report
Gorilla Testing
Grey Box Testing
quality assurance process improvement
organisation structure

3. Testing concerned with the accuracy of documentation.
Documentation Testing
Data-Driven Testing
CAST
Keyword driven Testing

4. 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
Quality
Decision table testing
stop testing timing
exploratory testing

5. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
white box testing
functional testing
Black Box Testing / Functional Testing
Monkey Testing

6. Testing whether the system is compatible with other systems with which it should communicate.
Compatibility Testing
Fault
Isolation Testing
exploratory testing

7. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
enough of testing
Maintenance testing
Equivalence Class

8. Testing whether the system meets its specified objectives for maintainability.
Acceptance Testing/User Acceptance Testing
Interface Testing
Bottom-up Testing
Maintainability Testing / Serviceability Testing

9. The testing of individual software components.
Bugs
GUI Testing
Development testing
Component Testing

10. 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
Depth Testing
Interface Testing
Ad-hoc Testing
Equivalence Class

11. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Development testing
N+ Testing
Statement coverage
backend testing/database testing

12. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
SOA
backend testing/database testing
Data-Driven Testing
Big Bang Testing

13. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
backend testing/database testing
AUT
Maintenance testing
Fuzz Testing

14. Model-based testing refers to software testing where test cases are derived in whole or in part from a model that describes some (usually functional) aspects of the system under test.
Accessibility Testing
Installation Testing
Model Based Testing
backend testing/database testing

15. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Context Driven Testing
Branch testing
Business process-based testing
Isolation Testing

16. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Grey Box Testing
Gamma testing
Heuristic evaluations
GUI Testing

17. This term refers to making software specifically designed for a specific locality
Interface Testing
black box testing
Localization Testing
white box testing

18. 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
N+ Testing
test coverage
Acceptance Testing/User Acceptance Testing
End-to-end Testing

19. Application Under Test
Quality
stop testing timing
AUT
Dynamic Testing

20. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Ad-hoc Testing
Compatibility Testing
Dependency Testing
Accessibility Testing

21. The percentage of decision outcomes that have been exercised by a test suite.
Exploratory Testing
Keyword driven Testing
Load Testing
Decision coverage

22. 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.
Context Driven Testing
white box testing
Keyword driven Testing
GUI Testing

23. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Alpha Testing
Statement coverage
AUT
Benchmark Testing

24. A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations
Mutation testing
Back-to-back testing
Defect density
Benchmark Testing

25. Testing in which test cases are designed based on variable usage within the code.
Maintainability Testing / Serviceability Testing
Data flow Testing
Equivalence Partitioning
white box testing

26. 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).
Design based Testing
test coverage
Heuristic evaluations
Statement coverage

27. Knows about the software and test - no proper plan
Compatibility Testing
exploratory testing
Model Based Testing
GUI Testing

28. Test case design
Branch
Efficiency testing
Depth Testing
Logic coverage Testing / Logic driven Testing / Structural

29. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
QA
Model Based Testing
Incremental testing
Testing best practice

30. 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
SOA
Beta Testing / Field Testing
Endurance Testing
Quality

31. Testing which covers all combinations of input values and preconditions for an element of the software under test
Gorilla Testing
Exhaustive Testing
Context Driven Testing
Documentation Testing

32. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Defect
Interface Testing
GUI Testing
Bottom-up Testing

33. 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.
Fuzz Testing
Installation Testing
Equivalence Partitioning
functional testing

34. The percentage of executable statements that have been exercised by a test suite.
Gamma testing
Quality
Beta Testing / Field Testing
Statement coverage

35. 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.
AUT
Code coverage
software testing
Interface Testing

36. 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.
Arc Testing / Branch Testing
Gamma testing
Efficiency testing
Model Based Testing

37. Stakeholder stakeholder satisfaction with test results report
Load Testing
CAST
providing information - metric
Development testing

38. executing the software
functional testing
Context Driven Testing
Invalid testing
software testing

39. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
providing information - metric
Equivalence Class
Isolation Testing

40. 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
providing information - metric
Gorilla Testing
Boundary value analysis/ testing
Concurrency Testing

41. 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
Dependency Testing
Basis Path Testing
best practice
Bugs

42. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Gamma testing
Context Driven Testing
Decision condition testing
Testing best practice

43. 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
SOA
Heuristic evaluations
providing information - metric
Benchmark Testing

44. Depends on the schedule and risk based - business impact follow the 20-80 rules
Fuzz Testing
stop testing timing
exploratory testing
Basis Path Testing

45. Provide critical information during project
providing information Objective
Integration Testing
Model Based Testing
GUI Testing

46. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Conversion Testing / Migration Testing
Gamma testing
Logic coverage Testing / Logic driven Testing / Structural
Big Bang Testing

47. Black-box tests conducted once the software has been integrated
High order tests
Bugs
Acceptance Testing/User Acceptance Testing
Conversion Testing / Migration Testing

48. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
High order tests
Monkey Testing
architecure of SOA
GUI Testing

49. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Development testing
quality assurance process improvement
Basis Path Testing
Alpha Testing

50. Can't see - test the functional testing - no access to code and testing is done on UI
Ad-hoc Testing
black box testing
N+ Testing
Interface Testing