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 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.
Arc Testing / Branch Testing
Fault
Equivalence partition Testing
Breadth Testing

2. Application Under Test
AUT
Testing best practice
Business process-based testing
exploratory testing

3. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
architecure of SOA
functional testing
Alpha Testing
Exhaustive Testing

4. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Agile Testing
enough of testing
Compatibility Testing
Context Driven Testing

5. Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields & Cookie security and Lockout testing . permitting unauthorised access.
Authorization Testing
Model Based Testing
Data flow Testing
High order tests

6. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
test coverage
Black Box Testing / Functional Testing
black box testing

7. 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
Data-Driven Testing
Back-to-back testing
End-to-end Testing
Mutation testing

8. 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+.
SOA
Accessibility Testing
N+ Testing
Fault

9. 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
Localization Testing
test coverage
Loop Testing
Heuristic evaluations

10. 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.
Mutation testing
Fuzz Testing
Interface Testing
Gorilla Testing

11. 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
Statement coverage
Black Box Testing / Functional Testing
Monkey Testing
enough of testing

12. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
providing information Objective
Dependency Testing
Branch
Interoperability testing

13. 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
Business process-based testing
Logic coverage Testing / Logic driven Testing / Structural
Boundary value analysis/ testing
Back-to-back testing

14. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Installation Testing
Coverage Testing
Decision condition testing
Maintenance testing

15. Testing which covers all combinations of input values and preconditions for an element of the software under test
Design based Testing
Concurrency Testing
Exhaustive Testing
functional testing

16. 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.
Context Driven Testing
Dynamic Testing
Model Based Testing
CAST

17. 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
Design based Testing
Compatibility Testing
Arc Testing / Branch Testing

18. 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
Compatibility Testing
Decision testing
best practice
Integration Testing

19. 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
N+ Testing
Code coverage
Branch testing

20. 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
Isolation Testing
Black Box Testing / Functional Testing
Logic coverage Testing / Logic driven Testing / Structural
Data-Driven Testing

21. Testing the changes to an operational system or the impact of a changed environment to an operational system
CAST
Grey Box Testing
Maintenance testing
Dynamic Testing

22. The percentage of decision outcomes that have been exercised by a test suite.
Documentation Testing
Coverage Testing
Decision coverage
QA

23. 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.
Dependency Testing
Bugs
Ad-hoc Testing
Bottom-up Testing

24. 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).
GUI Testing
Business process-based testing
Design based Testing
Coverage Testing

25. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Big Bang Testing
Gorilla Testing
Branch
Acceptance criteria

26. Similar to black box testing - structure of test cases in order to find defects and its strutured
functional testing
Benchmark Testing
software testing
Black Box Testing / Functional Testing

27. 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
Decision coverage
Quality
Component Testing
Data flow Testing

28. 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
organisation structure
Coverage Testing
Defect
Design based Testing

29. Determine whether a system meets some specified standard. external organization as complying with the standard
Data-Driven Testing
Endurance Testing
Conformance Testing / Compliance Testing / Standards Testing
Equivalence Partitioning

30. Provide critical information during project
Benchmark Testing
providing information Objective
Decision coverage
white box testing

31. 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)
Big Bang Testing
backend testing/database testing
SOA
Defect density

32. 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.
AUT
Context Driven Testing
structural testing
Boundary value analysis/ testing

33. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Equivalence Partitioning
Accessibility Testing
Grey Box Testing
Conversion Testing / Migration Testing

34. Kind of unit testing - internal working of software
Invalid testing
structural testing
Equivalence Class
Fuzz Testing

35. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Branch
Compatibility Testing
Data flow Testing
white box testing

36. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
Heuristic evaluations
architecure of SOA
best practice

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.
Code coverage
Maintenance testing
Ad-hoc Testing
Acceptance criteria

38. A test suite that exercises the full functionality of a product but does not test features in detail
Incremental testing
Breadth Testing
Defect
Decision coverage

39. 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.
N+ Testing
Decision coverage
Boundary value analysis/ testing
Data flow Testing

40. Knows about the software and test - no proper plan
Gamma testing
Ad-hoc Testing
exploratory testing
Coverage Testing

41. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Conversion Testing / Migration Testing
Authorization Testing
Accessibility Testing
Testing best practice

42. 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
Equivalence partition Testing
Exhaustive Testing
Authorization Testing
architecure of SOA

43. A white box test design technique in which test cases are designed to execute decision outcomes
Decision testing
Testing best practice
Gamma testing
Black Box Testing / Functional Testing

44. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Interoperability testing
stop testing timing
Development testing
Basis Path Testing

45. 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
Basis Path Testing
Branch
best practice
white box testing

46. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Bugs
quality assurance process improvement
Basis Path Testing
Testing best practice

47. Testing using input values that should be rejected by the component or system
Decision testing
Exploratory Testing
Invalid testing
Loop Testing

48. A white box test design technique in which test cases are designed to execute branches.
Loop Testing
Development testing
Coverage Testing
Branch testing

49. Can't see - test the functional testing - no access to code and testing is done on UI
Coverage Testing
black box testing
GUI Testing
Branch coverage

50. 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.
Agile Testing
Fault
QA
Branch testing