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. 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).
stop testing timing
Context Driven Testing
Design based Testing
Incremental testing

2. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Dynamic Testing
Concurrency Testing
Isolation Testing
Decision condition testing

3. Test case design
Data-Driven Testing
Logic coverage Testing / Logic driven Testing / Structural
Testing best practice
Branch

4. 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.
Context Driven Testing
Maintenance testing
Business process-based testing
Localization Testing

5. Testing concerned with the accuracy of documentation.
Isolation Testing
Breadth Testing
Logic coverage Testing / Logic driven Testing / Structural
Documentation Testing

6. Can't see - test the functional testing - no access to code and testing is done on UI
Testing best practice
black box testing
Statement coverage
Conversion Testing / Migration Testing

7. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Data-Driven Testing
Quality
backend testing/database testing
Interface Testing

8. Testing the changes to an operational system or the impact of a changed environment to an operational system
Localization Testing
Maintenance testing
Exhaustive Testing
Design based Testing

9. Stakeholder stakeholder satisfaction with test results report
Concurrency Testing
Equivalence Partitioning
functional testing
providing information - metric

10. Testing in which test cases are designed based on variable usage within the code.
Business process-based testing
Acceptance criteria
Data flow Testing
Boundary value analysis/ testing

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
Decision table testing
Branch coverage
Gorilla Testing
organisation structure

12. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
Maintainability Testing / Serviceability Testing
Compatibility Testing
Interface Testing

13. 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
Installation Testing
Maintainability Testing / Serviceability Testing
Monkey Testing
Exploratory Testing

14. 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
Equivalence Class
Integration Testing
Authorization Testing
Decision table testing

15. The process of testing to determine the interoperability of a software product
Interface Testing
N+ Testing
Interoperability testing
Concurrency Testing

16. Provide critical information during project
providing information Objective
N+ Testing
Equivalence Partitioning
Dynamic Testing

17. A white box testing technique that exercises program loops
Localization Testing
stop testing timing
Loop Testing
quality assurance process improvement

18. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
High order tests
Efficiency testing
Boundary value analysis/ testing
Agile Testing

19. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Alpha Testing
Interface Testing
Acceptance criteria
Conversion Testing / Migration Testing

20. 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
Data-Driven Testing
Ad-hoc Testing
Big Bang Testing
Quality

21. A test suite that exercises the full functionality of a product but does not test features in detail
Breadth Testing
Coverage Testing
functional testing
SOA

22. Testing whether the system is compatible with other systems with which it should communicate.
Fuzz Testing
exploratory testing
Development testing
Compatibility Testing

23. 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
End-to-end Testing
Mutation testing
Invalid testing
Defect density

24. Kind of unit testing - internal working of software
Design based Testing
backend testing/database testing
QA
structural testing

25. 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.
Code coverage
Bottom-up Testing
exploratory testing
Branch testing

26. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Conversion Testing / Migration Testing
Fuzz Testing
Maintainability Testing / Serviceability Testing
Ad-hoc Testing

27. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Depth Testing
Code coverage
Branch coverage
Equivalence Partitioning

28. 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.
Branch testing
Fuzz Testing
Depth Testing
white box testing

29. This term refers to making software specifically designed for a specific locality
Arc Testing / Branch Testing
Agile Testing
Back-to-back testing
Localization Testing

30. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Incremental testing
Defect density
providing information Objective
Gamma testing

31. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Decision coverage
Gamma testing
Branch testing
Incremental testing

32. The percentage of decision outcomes that have been exercised by a test suite.
Decision coverage
High order tests
SOA
exploratory testing

33. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Equivalence Class
Design based Testing
Equivalence partition Testing
Branch

34. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
GUI Testing
Monkey Testing
Conversion Testing / Migration Testing
Compatibility Testing

35. The percentage of executable statements that have been exercised by a test suite.
Conformance Testing / Compliance Testing / Standards Testing
Loop Testing
Black Box Testing / Functional Testing
Statement coverage

36. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Gamma testing
software testing
organisation structure
Decision coverage

37. 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
Load Testing
Black Box Testing / Functional Testing
Development testing

38. 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.
Model Based Testing
Fault
stop testing timing
providing information - metric

39. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Conformance Testing / Compliance Testing / Standards Testing
End-to-end Testing
software testing
Development testing

40. Root cause analyst - base of the problem - customer satisfaction report
Compatibility Testing
quality assurance process improvement
Data flow Testing
Fault

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

42. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Branch
Basis Path Testing
Dynamic Testing
Maintainability Testing / Serviceability Testing

43. Checks for memory leaks or other problems that may occur with prolonged execution
Beta Testing / Field Testing
Endurance Testing
Conformance Testing / Compliance Testing / Standards Testing
Decision table testing

44. 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.
Data flow Testing
Testing best practice
Arc Testing / Branch Testing
Defect

45. Testing which covers all combinations of input values and preconditions for an element of the software under test
Exhaustive Testing
Dependency Testing
Acceptance Testing/User Acceptance Testing
Exploratory Testing

46. 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
Breadth Testing
Context Driven Testing
architecure of SOA

47. It is a whole - is the whole process form review to plans strategy and whole thing
Back-to-back testing
QA
Statement coverage
Conversion Testing / Migration Testing

48. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
black box testing
Load Testing
Data-Driven Testing
enough of testing

49. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Gamma testing
enough of testing
Decision condition testing
Alpha Testing

50. Knows about the software and test - no proper plan
Testing best practice
Depth Testing
exploratory testing
Compatibility Testing