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 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
Acceptance Testing/User Acceptance Testing
Exhaustive Testing
Maintenance testing
Equivalence Class

2. Testing software through executing it.
Dynamic Testing
Decision condition testing
white box testing
Equivalence Class

3. Similar to black box testing - structure of test cases in order to find defects and its strutured
Mutation testing
black box testing
functional testing
Load Testing

4. A test that exercises a feature of a product in full detail.
Depth Testing
Logic coverage Testing / Logic driven Testing / Structural
black box testing
SOA

5. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Equivalence partition Testing
Incremental testing
Testing best practice
SOA

6. 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
Mutation testing
Back-to-back testing
Context Driven Testing

7. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Decision condition testing
AUT
Ad-hoc Testing
Alpha Testing

8. 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.
Boundary value analysis/ testing
Fuzz Testing
Data-Driven Testing
End-to-end Testing

9. Depends on the schedule and risk based - business impact follow the 20-80 rules
Interoperability testing
Ad-hoc Testing
stop testing timing
Design based Testing

10. 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
Fuzz Testing
Bugs
Depth Testing
providing information Objective

11. 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
Incremental testing
Breadth Testing
Decision table testing
Grey Box Testing

12. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Branch
Agile Testing
providing information Objective
best practice

13. Provide critical information during project
Gorilla Testing
providing information Objective
Documentation Testing
Exhaustive 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.
Branch testing
enough of testing
Model Based Testing
Loop Testing

15. 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
Defect
providing information Objective
Code coverage

16. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Equivalence Partitioning
Decision testing
stop testing timing
Acceptance criteria

17. 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
Maintainability Testing / Serviceability Testing
Decision testing
Model Based Testing
Integration Testing

18. Testing concerned with the accuracy of documentation.
Documentation Testing
Model Based Testing
Beta Testing / Field Testing
Exhaustive Testing

19. 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)
black box testing
Breadth Testing
Defect density
Monkey Testing

20. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Logic coverage Testing / Logic driven Testing / Structural
Efficiency testing
Authorization Testing
Business process-based testing

21. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Keyword driven Testing
Monkey Testing
Load Testing
test coverage

22. A white box testing technique that exercises program loops
Loop Testing
SOA
Equivalence Partitioning
Compatibility Testing

23. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Boundary value analysis/ testing
Accessibility Testing
Ad-hoc Testing
Code coverage

24. It is a whole - is the whole process form review to plans strategy and whole thing
QA
Basis Path Testing
Back-to-back testing
Authorization Testing

25. A white box test design technique in which test cases are designed to execute decision outcomes
Arc Testing / Branch Testing
Testing best practice
Decision testing
Accessibility Testing

26. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
High order tests
Exploratory Testing
Logic coverage Testing / Logic driven Testing / Structural
Context Driven Testing

27. 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
Heuristic evaluations
functional testing
Compatibility Testing
Breadth Testing

28. 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
stop testing timing
Interoperability testing
Mutation testing
test coverage

29. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
Code coverage
Quality
Business process-based testing

30. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Documentation Testing
organisation structure
Development testing
Maintainability Testing / Serviceability Testing

31. Stakeholder stakeholder satisfaction with test results report
Bottom-up Testing
providing information - metric
Arc Testing / Branch Testing
Model Based Testing

32. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Arc Testing / Branch Testing
architecure of SOA
Testing best practice
Benchmark Testing

33. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
exploratory testing
Keyword driven Testing
organisation structure
Equivalence Class

34. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Incremental testing
Benchmark Testing
Coverage Testing
Isolation Testing

35. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Basis Path Testing
Acceptance Testing/User Acceptance Testing
white box testing
Heuristic evaluations

36. Testing in which test cases are designed based on variable usage within the code.
Acceptance Testing/User Acceptance Testing
providing information Objective
Data flow Testing
stop testing timing

37. 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.
exploratory testing
Code coverage
Documentation Testing
Conformance Testing / Compliance Testing / Standards Testing

38. Root cause analyst - base of the problem - customer satisfaction report
Keyword driven Testing
Decision testing
quality assurance process improvement
Branch testing

39. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
functional testing
Fault
structural testing

40. Testing the changes to an operational system or the impact of a changed environment to an operational system
Black Box Testing / Functional Testing
Concurrency Testing
Maintenance testing
structural testing

41. Approach to doing something that generally give good results when applied appropriately and thoughfully
End-to-end Testing
Acceptance Testing/User Acceptance Testing
best practice
Bottom-up Testing

42. 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
Quality
Maintainability Testing / Serviceability Testing
Compatibility Testing

43. A test suite that exercises the full functionality of a product but does not test features in detail
End-to-end Testing
Keyword driven Testing
Breadth Testing
Loop Testing

44. Application Under Test
AUT
Coverage Testing
Design based Testing
Authorization Testing

45. 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
Branch testing
Black Box Testing / Functional Testing
Conversion Testing / Migration Testing
Data flow Testing

46. 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
Equivalence Partitioning
Statement coverage
SOA

47. Can't see - test the functional testing - no access to code and testing is done on UI
black box testing
Statement coverage
Heuristic evaluations
architecure of SOA

48. Black-box tests conducted once the software has been integrated
Conformance Testing / Compliance Testing / Standards Testing
High order tests
Incremental testing
quality assurance process improvement

49. 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
Depth Testing
Accessibility Testing
Monkey Testing
Concurrency Testing

50. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
QA
Design based Testing
enough of testing
exploratory testing