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. Application Under Test
architecure of SOA
Arc Testing / Branch Testing
AUT
quality assurance process improvement

2. 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
Back-to-back testing
Testing best practice
Invalid testing
Branch

3. Computer Aided Software Testing
CAST
Agile Testing
Branch coverage
Exploratory Testing

4. Depends on the schedule and risk based - business impact follow the 20-80 rules
Basis Path Testing
Model Based Testing
Authorization Testing
stop testing timing

5. It is a whole - is the whole process form review to plans strategy and whole thing
Bugs
Grey Box Testing
test coverage
QA

6. 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
Statement coverage
Context Driven Testing
Mutation testing
Heuristic evaluations

7. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Accessibility Testing
Equivalence Class
best practice
providing information - metric

8. Testing whether the system is compatible with other systems with which it should communicate.
Defect density
Compatibility Testing
exploratory testing
Ad-hoc Testing

9. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Documentation Testing
Bottom-up Testing
Gamma testing
enough of testing

10. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
architecure of SOA
Testing best practice
Breadth Testing
Dependency Testing

11. Testing whether the system meets its specified objectives for maintainability.
software testing
Decision coverage
enough of testing
Maintainability Testing / Serviceability Testing

12. Testing the changes to an operational system or the impact of a changed environment to an operational system
Back-to-back testing
Alpha Testing
Design based Testing
Maintenance testing

13. Similar to black box testing - structure of test cases in order to find defects and its strutured
Boundary value analysis/ testing
functional testing
Conformance Testing / Compliance Testing / Standards Testing
Maintainability Testing / Serviceability Testing

14. executing the software
Accessibility Testing
Compatibility Testing
Fault
software testing

15. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Design based Testing
Decision testing
Boundary value analysis/ testing
Exploratory Testing

16. The percentage of decision outcomes that have been exercised by a test suite.
Compatibility Testing
Integration Testing
Equivalence Class
Decision coverage

17. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
Quality
QA
Load Testing

18. 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 partition Testing
providing information Objective
Maintainability Testing / Serviceability Testing

19. 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.
Logic coverage Testing / Logic driven Testing / Structural
Interoperability testing
Gamma testing
Fuzz Testing

20. Provide critical information during project
Heuristic evaluations
providing information Objective
Decision condition testing
Concurrency Testing

21. Root cause analyst - base of the problem - customer satisfaction report
Coverage Testing
quality assurance process improvement
Gamma testing
white box testing

22. Testing software through executing it.
Integration Testing
Authorization Testing
Dynamic Testing
Efficiency testing

23. Kind of unit testing - internal working of software
Exhaustive Testing
Maintainability Testing / Serviceability Testing
Load Testing
structural testing

24. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Basis Path Testing
Heuristic evaluations
Branch testing
backend testing/database testing

25. 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
Heuristic evaluations
Bottom-up Testing
providing information Objective

26. 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
Beta Testing / Field Testing
Coverage Testing
Branch
test coverage

27. 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.
Statement coverage
backend testing/database testing
Decision coverage
Boundary value analysis/ testing

28. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
backend testing/database testing
Code coverage
Isolation Testing
Bugs

29. Stakeholder stakeholder satisfaction with test results report
providing information - metric
Basis Path Testing
Back-to-back testing
Bottom-up Testing

30. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Gorilla Testing
structural testing
Big Bang Testing
providing information - metric

31. The percentage of executable statements that have been exercised by a test suite.
QA
Basis Path Testing
Statement coverage
Acceptance Testing/User Acceptance Testing

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
Conversion Testing / Migration Testing
Equivalence Partitioning
Bugs
stop testing timing

33. 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
N+ Testing
Integration Testing
providing information Objective
Invalid testing

34. 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
Documentation Testing
Defect density
Integration Testing
Back-to-back testing

35. 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.
Acceptance criteria
Authorization Testing
Model Based Testing
Quality

36. Determine whether a system meets some specified standard. external organization as complying with the standard
Branch testing
Defect density
Compatibility Testing
Conformance Testing / Compliance Testing / Standards Testing

37. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Logic coverage Testing / Logic driven Testing / Structural
Gamma testing
Arc Testing / Branch Testing
Design based Testing

38. 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.
Defect density
providing information Objective
Branch
End-to-end Testing

39. Black-box tests conducted once the software has been integrated
Accessibility Testing
High order tests
Dependency Testing
Back-to-back testing

40. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
backend testing/database testing
Fuzz Testing
Loop Testing
Benchmark Testing

41. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Mutation testing
Business process-based testing
enough of testing
Fuzz Testing

42. The process of testing to determine the efficiency of a software product
Equivalence Class
High order tests
Efficiency testing
Monkey Testing

43. 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.
Defect
End-to-end Testing
Context Driven Testing
Heuristic evaluations

44. 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
Gorilla Testing
organisation structure
Installation Testing
Testing best practice

45. Testing one particular module - functionality heavily
Testing best practice
quality assurance process improvement
Conformance Testing / Compliance Testing / Standards Testing
Gorilla Testing

46. A test suite that exercises the full functionality of a product but does not test features in detail
Back-to-back testing
Decision testing
Breadth Testing
test coverage

47. 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
Acceptance Testing/User Acceptance Testing
Fuzz Testing
Arc Testing / Branch Testing

48. A white box testing technique that exercises program loops
Documentation Testing
Loop Testing
Equivalence partition Testing
Depth Testing

49. 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
functional testing
Compatibility Testing
Decision table testing
providing information - metric

50. 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
End-to-end Testing
Code coverage
QA
test coverage