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 white box test case design techniques that uses the algorithmic flow of the program to design tests
Acceptance Testing/User Acceptance Testing
Maintenance testing
N+ Testing
Basis Path Testing

2. Checks for memory leaks or other problems that may occur with prolonged execution
Efficiency testing
Breadth Testing
Agile Testing
Endurance Testing

3. Testing the changes to an operational system or the impact of a changed environment to an operational system
Maintenance testing
Ad-hoc Testing
Fuzz Testing
Bottom-up Testing

4. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
white box testing
Loop Testing
Gamma testing
stop testing timing

5. Testing concerned with the accuracy of documentation.
Equivalence Class
Equivalence partition Testing
Fuzz Testing
Documentation Testing

6. It is a whole - is the whole process form review to plans strategy and whole thing
Heuristic evaluations
QA
best practice
Beta Testing / Field Testing

7. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
functional testing
Interface Testing
Beta Testing / Field Testing
organisation structure

8. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Breadth Testing
Equivalence Class
Business process-based testing
Fuzz Testing

9. A white box testing technique that exercises program loops
Authorization Testing
Loop Testing
Decision condition testing
Heuristic evaluations

10. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Breadth Testing
providing information - metric
Heuristic evaluations
Big Bang Testing

11. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.
Decision testing
Context Driven Testing
Incremental testing
Isolation Testing

12. The percentage of decision outcomes that have been exercised by a test suite.
Benchmark Testing
Acceptance Testing/User Acceptance Testing
Business process-based testing
Decision coverage

13. Kind of unit testing - internal working of software
Testing best practice
test coverage
Isolation Testing
structural testing

14. 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.
Maintenance testing
AUT
CAST
Bottom-up Testing

15. 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
quality assurance process improvement
Localization Testing
Equivalence Class
black box testing

16. 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.
Defect density
Exhaustive Testing
Keyword driven Testing
Context Driven Testing

17. Testing which covers all combinations of input values and preconditions for an element of the software under test
Defect
enough of testing
Exhaustive Testing
Endurance Testing

18. 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
Component Testing
Documentation Testing
Conversion Testing / Migration Testing
Bugs

19. 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+.
Beta Testing / Field Testing
Acceptance criteria
Conformance Testing / Compliance Testing / Standards Testing
N+ Testing

20. This term refers to making software specifically designed for a specific locality
Big Bang Testing
Localization Testing
Invalid testing
black box testing

21. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Defect
Design based Testing
providing information - metric
Testing best practice

22. Designing tests based on objectives derived from the architectural or detail design of the software (e.g. - tests that execute specific invocation paths or probe the worst case behaviour of algorithms).
Design based Testing
best practice
architecure of SOA
Equivalence partition Testing

23. 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
Back-to-back testing
N+ Testing
Coverage Testing
GUI Testing

24. Stakeholder stakeholder satisfaction with test results report
Authorization Testing
Exploratory Testing
providing information - metric
Endurance Testing

25. Testing using input values that should be rejected by the component or system
Endurance Testing
providing information Objective
Invalid testing
Decision table testing

26. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Accessibility Testing
QA
Statement coverage
Component Testing

27. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Fault
Alpha Testing
Defect density
Grey Box Testing

28. Testing whether the system meets its specified objectives for maintainability.
Boundary value analysis/ testing
Dynamic Testing
Gorilla Testing
Maintainability Testing / Serviceability Testing

29. The process of testing to determine the interoperability of a software product
Big Bang Testing
Compatibility Testing
Equivalence Partitioning
Interoperability testing

30. Similar to black box testing - structure of test cases in order to find defects and its strutured
white box testing
Component Testing
functional testing
Dynamic Testing

31. A test suite that exercises the full functionality of a product but does not test features in detail
Beta Testing / Field Testing
Dynamic Testing
Breadth Testing
Design based Testing

32. 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
Integration Testing
Acceptance criteria
structural testing

33. 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.
Exploratory Testing
functional testing
Model Based Testing
architecure of SOA

34. 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
Branch coverage
Mutation testing
architecure of SOA
Equivalence Class

35. 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
Equivalence partition Testing
Acceptance criteria
Integration Testing
High order tests

36. 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
Decision testing
Gorilla Testing
Arc Testing / Branch Testing
Heuristic evaluations

37. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Interface Testing
Benchmark Testing
Exploratory Testing
functional testing

38. Testing software through executing it.
Acceptance Testing/User Acceptance Testing
Basis Path Testing
Fault
Dynamic Testing

39. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Endurance Testing
N+ Testing
Defect
Ad-hoc Testing

40. A test that exercises a feature of a product in full detail.
Depth Testing
Big Bang Testing
Testing best practice
Arc Testing / Branch Testing

41. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
backend testing/database testing
Back-to-back testing
Decision condition testing
Fault

42. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Isolation Testing
End-to-end Testing
Defect density
Conformance Testing / Compliance Testing / Standards Testing

43. 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.
best practice
N+ Testing
Code coverage
Exhaustive Testing

44. The expected results or performance characteristics that define whether the test cases passed or failed
Decision coverage
Acceptance criteria
quality assurance process improvement
QA

45. Approach to doing something that generally give good results when applied appropriately and thoughfully
best practice
Equivalence Class
AUT
Bugs

46. 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
Integration Testing
Statement coverage
Exhaustive Testing

47. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices
Coverage Testing
architecure of SOA
Logic coverage Testing / Logic driven Testing / Structural
organisation structure

48. 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.
Breadth Testing
Fuzz Testing
Defect
Dependency Testing

49. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
organisation structure
Basis Path Testing
Fuzz Testing
Isolation Testing

50. 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
Heuristic evaluations
Development testing
Agile Testing
Quality