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. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Load Testing
Component Testing
Arc Testing / Branch Testing
Maintainability Testing / Serviceability Testing

2. A test that exercises a feature of a product in full detail.
exploratory testing
Monkey Testing
Depth Testing
functional testing

3. Test case design
Logic coverage Testing / Logic driven Testing / Structural
Equivalence Partitioning
structural testing
Efficiency testing

4. Can't see - test the functional testing - no access to code and testing is done on UI
Fuzz Testing
Endurance Testing
Branch coverage
black box testing

5. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
High order tests
Development testing
Model Based Testing
Logic coverage Testing / Logic driven Testing / Structural

6. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Bottom-up Testing
Big Bang Testing
Alpha Testing
Grey Box Testing

7. 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
Load Testing
Statement coverage
Gorilla Testing
Mutation testing

8. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
organisation structure
Gorilla Testing
Ad-hoc Testing
Interface Testing

9. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases
Boundary value analysis/ testing
Agile Testing
Data flow Testing
test coverage

10. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Grey Box Testing
Coverage Testing
Interface Testing
Benchmark Testing

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

12. Determine whether a system meets some specified standard. external organization as complying with the standard
Bugs
Ad-hoc Testing
Conformance Testing / Compliance Testing / Standards Testing
Interoperability testing

13. 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)
functional testing
Testing best practice
Development testing
Defect density

14. The expected results or performance characteristics that define whether the test cases passed or failed
best practice
Exhaustive Testing
Gamma testing
Acceptance criteria

15. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
providing information Objective
Testing best practice
Maintainability Testing / Serviceability Testing
Exhaustive Testing

16. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
High order tests
Ad-hoc Testing
best practice
GUI Testing

17. This term refers to making software specifically designed for a specific locality
Mutation testing
Alpha Testing
Localization Testing
Equivalence Class

18. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or
Defect density
Black Box Testing / Functional Testing
enough of testing
organisation structure

19. The percentage of decision outcomes that have been exercised by a test suite.
Beta Testing / Field Testing
Business process-based testing
Decision coverage
Statement coverage

20. Testing whether the system meets its specified objectives for maintainability.
Bottom-up Testing
Maintainability Testing / Serviceability Testing
High order tests
Breadth Testing

21. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Incremental testing
High order tests
GUI Testing
Data flow Testing

22. 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.
software testing
N+ Testing
Accessibility Testing
End-to-end Testing

23. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Documentation Testing
architecure of SOA
Big Bang Testing
Keyword driven Testing

24. Application Under Test
Loop Testing
Localization Testing
Business process-based testing
AUT

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
best practice
Heuristic evaluations
Data-Driven Testing
Documentation Testing

26. 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
Documentation Testing
Acceptance criteria
Arc Testing / Branch Testing
Integration Testing

27. 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.
Code coverage
Isolation Testing
Interface Testing
Black Box Testing / Functional Testing

28. 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.
Decision coverage
Maintenance testing
providing information Objective
Bottom-up Testing

29. 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
Big Bang Testing
Dynamic Testing
Concurrency Testing
functional testing

30. Depends on the schedule and risk based - business impact follow the 20-80 rules
black box testing
stop testing timing
Model Based Testing
Arc Testing / Branch Testing

31. Testing one particular module - functionality heavily
Maintenance testing
Arc Testing / Branch Testing
Gorilla Testing
Testing best practice

32. 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
End-to-end Testing
Agile Testing
Bugs
Arc Testing / Branch Testing

33. Knows about the software and test - no proper plan
exploratory testing
Fuzz Testing
Ad-hoc Testing
enough of testing

34. Testing concerned with the accuracy of documentation.
High order tests
Monkey Testing
Documentation Testing
Defect density

35. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Gamma testing
Localization Testing
backend testing/database testing
Arc Testing / Branch Testing

36. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Gamma testing
Alpha Testing
Mutation testing
enough of testing

37. Root cause analyst - base of the problem - customer satisfaction report
Quality
CAST
Black Box Testing / Functional Testing
quality assurance process improvement

38. A white box testing technique that exercises program loops
Compatibility Testing
Loop Testing
Beta Testing / Field Testing
Arc Testing / Branch Testing

39. Approach to doing something that generally give good results when applied appropriately and thoughfully
best practice
Documentation Testing
Endurance Testing
Dependency Testing

40. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
providing information - metric
Model Based Testing
High order tests

41. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
CAST
test coverage
Localization Testing
Equivalence Partitioning

42. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Decision table testing
Invalid testing
End-to-end Testing
Dependency Testing

43. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
best practice
Exploratory Testing
Decision condition testing
GUI Testing

44. 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.
Decision coverage
End-to-end Testing
Decision testing
Model Based Testing

45. Testing using input values that should be rejected by the component or system
Heuristic evaluations
Gamma testing
Fuzz Testing
Invalid testing

46. executing the software
Coverage Testing
software testing
Equivalence Partitioning
Localization Testing

47. Checks for memory leaks or other problems that may occur with prolonged execution
Quality
Endurance Testing
Conversion Testing / Migration Testing
Concurrency Testing

48. The process of testing to determine the interoperability of a software product
Bottom-up Testing
Depth Testing
CAST
Interoperability testing

49. 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+.
Code coverage
Mutation testing
N+ Testing
Heuristic evaluations

50. Kind of unit testing - internal working of software
SOA
Branch coverage
structural testing
organisation structure