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 testing of individual software components.
Component Testing
Context Driven Testing
Interoperability testing
Efficiency testing

2. 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
Data-Driven Testing
white box testing
Basis Path Testing
Development testing

3. Testing concerned with the accuracy of documentation.
Isolation Testing
Documentation Testing
Heuristic evaluations
enough of testing

4. Root cause analyst - base of the problem - customer satisfaction report
quality assurance process improvement
Acceptance criteria
Benchmark Testing
QA

5. 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
Logic coverage Testing / Logic driven Testing / Structural
Branch testing
Equivalence Class
Branch

6. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Integration Testing
Alpha Testing
Development testing
SOA

7. 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
software testing
Quality
Big Bang Testing
Maintainability Testing / Serviceability Testing

8. Test case design
Code coverage
best practice
Logic coverage Testing / Logic driven Testing / Structural
Acceptance criteria

9. The process of testing to determine the interoperability of a software product
Interoperability testing
Heuristic evaluations
Endurance Testing
Beta Testing / Field Testing

10. Black-box tests conducted once the software has been integrated
Decision condition testing
stop testing timing
Equivalence Class
High order tests

11. Checks for memory leaks or other problems that may occur with prolonged execution
Load Testing
Boundary value analysis/ testing
exploratory testing
Endurance Testing

12. 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
Black Box Testing / Functional Testing
Concurrency Testing
Gamma testing
AUT

13. A test suite that exercises the full functionality of a product but does not test features in detail
Breadth Testing
Installation Testing
architecure of SOA
exploratory testing

14. Testing one particular module - functionality heavily
Back-to-back testing
Coverage Testing
Design based Testing
Gorilla Testing

15. 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.
Agile Testing
AUT
Dependency Testing
Bottom-up Testing

16. 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
SOA
Big Bang Testing
Defect density
Interface Testing

17. 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.
End-to-end Testing
Back-to-back testing
Authorization Testing
architecure of SOA

18. 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.
quality assurance process improvement
Conformance Testing / Compliance Testing / Standards Testing
Testing best practice
Fuzz Testing

19. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared and analyzed in cases of discrepancies
Dependency Testing
organisation structure
Back-to-back testing
enough of testing

20. An accidental condition that causes the failure of a component in the implementation model to perform its required behavior. A fault is the root cause of one or more defects identified by observing one or more failures.
N+ Testing
Documentation Testing
quality assurance process improvement
Fault

21. 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.
Conversion Testing / Migration Testing
End-to-end Testing
white box testing
Gamma testing

22. 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
Accessibility Testing
Basis Path Testing
Heuristic evaluations
Conversion Testing / Migration Testing

23. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
Data-Driven Testing
Logic coverage Testing / Logic driven Testing / Structural
Decision condition testing

24. Stakeholder stakeholder satisfaction with test results report
Data-Driven Testing
Branch coverage
Maintainability Testing / Serviceability Testing
providing information - metric

25. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Basis Path Testing
Load Testing
Ad-hoc Testing
Bottom-up Testing

26. 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
Breadth Testing
Context Driven Testing
Statement coverage
test coverage

27. Approach to doing something that generally give good results when applied appropriately and thoughfully
Defect
Dependency Testing
best practice
Efficiency testing

28. The percentage of decision outcomes that have been exercised by a test suite.
providing information - metric
Decision coverage
Testing best practice
Efficiency testing

29. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Defect
Dynamic Testing
GUI Testing
Acceptance criteria

30. 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
Dynamic Testing
Integration Testing
Quality
Alpha Testing

31. 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+.
N+ Testing
Mutation testing
structural testing
Design based Testing

32. A white box test design technique in which test cases are designed to execute branches.
Acceptance Testing/User Acceptance Testing
Interface Testing
Branch testing
Development testing

33. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Back-to-back testing
Equivalence Partitioning
Business process-based testing
Data flow Testing

34. 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.
Gamma testing
High order tests
Decision condition testing
Boundary value analysis/ testing

35. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
best practice
Benchmark Testing
Data flow Testing
organisation structure

36. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Component Testing
Isolation Testing
white box testing
Bugs

37. 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
Equivalence partition Testing
Branch testing
Monkey Testing
Documentation Testing

38. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Acceptance Testing/User Acceptance Testing
Decision coverage
Gamma testing
Mutation testing

39. 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
Acceptance Testing/User Acceptance Testing
Decision coverage
Grey Box Testing
Bugs

40. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Component Testing
Dependency Testing
N+ Testing
Exhaustive Testing

41. Similar to black box testing - structure of test cases in order to find defects and its strutured
Arc Testing / Branch Testing
functional testing
N+ Testing
QA

42. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Gamma testing
Basis Path Testing
Back-to-back testing
Compatibility Testing

43. 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)
Documentation Testing
Conversion Testing / Migration Testing
Exploratory Testing
Defect density

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.
Accessibility Testing
Equivalence Class
Data flow Testing
Model Based Testing

45. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Business process-based testing
Equivalence Partitioning
Authorization Testing
Accessibility Testing

46. 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
Component Testing
stop testing timing
Installation Testing
N+ Testing

47. The expected results or performance characteristics that define whether the test cases passed or failed
Conformance Testing / Compliance Testing / Standards Testing
Acceptance criteria
Accessibility Testing
Black Box Testing / Functional Testing

48. 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
Authorization Testing
Equivalence Class
Acceptance Testing/User Acceptance Testing

49. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Ad-hoc Testing
Dynamic Testing
Agile Testing
Business process-based testing

50. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Boundary value analysis/ testing
quality assurance process improvement
white box testing
Testing best practice