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 process of testing to determine the interoperability of a software product
Exploratory Testing
Accessibility Testing
Interoperability testing
Beta Testing / Field Testing

2. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Maintenance testing
Mutation testing
organisation structure
Branch coverage

3. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Decision table testing
Decision condition testing
GUI Testing
Decision testing

4. Testing the changes to an operational system or the impact of a changed environment to an operational system
Maintenance testing
Decision testing
Bugs
Localization Testing

5. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
N+ Testing
Conformance Testing / Compliance Testing / Standards Testing
Testing best practice
Equivalence Partitioning

6. 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.
stop testing timing
Monkey Testing
Keyword driven Testing
backend testing/database testing

7. Provide critical information during project
Back-to-back testing
providing information Objective
Defect density
Fuzz Testing

8. 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)
High order tests
Development testing
Decision table testing
Defect density

9. Determine whether a system meets some specified standard. external organization as complying with the standard
Conformance Testing / Compliance Testing / Standards Testing
Acceptance criteria
Statement coverage
Equivalence Class

10. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Development testing
Decision condition testing
Conformance Testing / Compliance Testing / Standards Testing
Defect

11. 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.
Dynamic Testing
white box testing
Code coverage
Dependency Testing

12. 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.
End-to-end Testing
functional testing
Endurance Testing
Ad-hoc Testing

13. 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
Equivalence Partitioning
Incremental testing
Logic coverage Testing / Logic driven Testing / Structural
Beta Testing / Field Testing

14. 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
Compatibility Testing
Defect density
End-to-end Testing
Branch

15. Can't see - test the functional testing - no access to code and testing is done on UI
Load Testing
black box testing
providing information Objective
Branch

16. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
CAST
Grey Box Testing
Acceptance criteria
AUT

17. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Business process-based testing
Equivalence Class
Code coverage
Equivalence Partitioning

18. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Model Based Testing
Acceptance Testing/User Acceptance Testing
Endurance Testing
Accessibility Testing

19. 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
Statement coverage
exploratory testing
test coverage
white box testing

20. Testing concerned with the accuracy of documentation.
Decision coverage
Testing best practice
SOA
Documentation Testing

21. A white box test design technique in which test cases are designed to execute branches.
Testing best practice
Branch testing
Fuzz Testing
Documentation Testing

22. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
Defect
Compatibility Testing
Statement coverage

23. 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.
exploratory testing
Efficiency testing
Concurrency Testing
Fault

24. 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
Ad-hoc Testing
Alpha Testing
Compatibility Testing
Black Box Testing / Functional Testing

25. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
providing information - metric
Interface Testing
Quality
enough of testing

26. 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
Monkey Testing
Conformance Testing / Compliance Testing / Standards Testing
Acceptance criteria
Big Bang Testing

27. 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.
CAST
Model Based Testing
Back-to-back testing
Black Box Testing / Functional Testing

28. A white box test design technique in which test cases are designed to execute decision outcomes
Benchmark Testing
Branch
Alpha Testing
Decision testing

29. 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
Incremental testing
End-to-end Testing
Dependency Testing
Coverage Testing

30. 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
Branch coverage
Endurance Testing
Gorilla Testing
Acceptance Testing/User Acceptance Testing

31. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Grey Box Testing
Decision testing
Isolation Testing
Equivalence Class

32. The process of testing to determine the efficiency of a software product
Exhaustive Testing
Decision condition testing
white box testing
Efficiency testing

33. Testing whether the system meets its specified objectives for maintainability.
N+ Testing
SOA
Heuristic evaluations
Maintainability Testing / Serviceability Testing

34. A white box test case design techniques that uses the algorithmic flow of the program to design tests
best practice
GUI Testing
CAST
Basis Path Testing

35. The percentage of decision outcomes that have been exercised by a test suite.
Agile Testing
Basis Path Testing
Decision coverage
Dependency Testing

36. Kind of unit testing - internal working of software
structural testing
Bottom-up Testing
Statement coverage
Invalid testing

37. 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.
Breadth Testing
Fault
Conformance Testing / Compliance Testing / Standards Testing
Arc Testing / Branch Testing

38. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Context Driven Testing
Interoperability testing
Decision condition testing
Big Bang Testing

39. Computer Aided Software Testing
backend testing/database testing
Equivalence Class
Authorization Testing
CAST

40. 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
Branch
Data-Driven Testing
Depth Testing
Documentation Testing

41. Depends on the schedule and risk based - business impact follow the 20-80 rules
Grey Box Testing
Arc Testing / Branch Testing
stop testing timing
Back-to-back testing

42. An anomaly or flaw in a delivered work product. found during early lifecycle phases A defect can be any kind of issue you want tracked and resolved.
Boundary value analysis/ testing
Development testing
exploratory testing
Defect

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
Exploratory Testing
Monkey Testing
Efficiency testing
Heuristic evaluations

44. Application Under Test
Conversion Testing / Migration Testing
Endurance Testing
AUT
Data flow Testing

45. The expected results or performance characteristics that define whether the test cases passed or failed
software testing
Grey Box Testing
Gamma testing
Acceptance criteria

46. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Authorization Testing
Dependency Testing
Maintenance testing
QA

47. 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
End-to-end Testing
Equivalence Class
Dependency Testing
Component Testing

48. Testing using input values that should be rejected by the component or system
Invalid testing
enough of testing
Decision testing
Equivalence Partitioning

49. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Maintainability Testing / Serviceability Testing
architecure of SOA
Exploratory Testing
Alpha Testing

50. A test suite that exercises the full functionality of a product but does not test features in detail
AUT
Breadth Testing
Concurrency Testing
Gorilla Testing