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 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
Alpha Testing
QA
Back-to-back testing

2. The percentage of decision outcomes that have been exercised by a test suite.
N+ Testing
Maintenance testing
Decision coverage
test coverage

3. Testing one particular module - functionality heavily
Integration Testing
Endurance Testing
Decision table testing
Gorilla Testing

4. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
white box testing
Acceptance criteria
Load Testing
Endurance Testing

5. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Big Bang Testing
Alpha Testing
Interoperability testing
Isolation Testing

6. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Data flow Testing
Branch testing
organisation structure
Dynamic Testing

7. 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.
stop testing timing
Keyword driven Testing
Bottom-up Testing
Grey Box Testing

8. 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).
Depth Testing
Benchmark Testing
Back-to-back testing
Design based Testing

9. A white box test design technique in which test cases are designed to execute decision outcomes
Equivalence Class
Decision testing
Monkey Testing
Grey Box Testing

10. 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
Benchmark Testing
Acceptance criteria
Quality
QA

11. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Authorization Testing
Benchmark Testing
End-to-end Testing
Incremental testing

12. 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
QA
Authorization Testing
exploratory testing

13. 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)
Dynamic Testing
Defect density
Depth Testing
Branch testing

14. A test that exercises a feature of a product in full detail.
Compatibility Testing
Gamma testing
Depth Testing
Back-to-back testing

15. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Equivalence Class
Development testing
enough of testing
white box testing

16. Testing software through executing it.
End-to-end Testing
Equivalence partition Testing
Dynamic Testing
Data flow Testing

17. 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
Boundary value analysis/ testing
Keyword driven Testing

18. 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
Exploratory Testing
stop testing timing
Heuristic evaluations

19. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
providing information - metric
Gamma testing
Interface Testing
Gorilla Testing

20. 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.
QA
Gamma testing
Fault
Invalid testing

21. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Load Testing
test coverage
Equivalence partition Testing
Incremental testing

22. 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
white box testing
Installation Testing
Bottom-up Testing
architecure of SOA

23. This term refers to making software specifically designed for a specific locality
Branch
Localization Testing
QA
Agile Testing

24. 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
architecure of SOA
software testing
Context Driven Testing
Branch

25. 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
Fault
N+ Testing

26. Similar to black box testing - structure of test cases in order to find defects and its strutured
Bugs
functional testing
Code coverage
Breadth Testing

27. The process of testing to determine the interoperability of a software product
Maintenance testing
best practice
Interoperability testing
test coverage

28. Depends on the schedule and risk based - business impact follow the 20-80 rules
Quality
stop testing timing
Arc Testing / Branch Testing
Localization Testing

29. 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
Interoperability testing
Depth Testing
black box testing
Back-to-back testing

30. Kind of unit testing - internal working of software
Quality
structural testing
architecure of SOA
Agile Testing

31. 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.
Ad-hoc Testing
Testing best practice
Defect
structural testing

32. Stakeholder stakeholder satisfaction with test results report
End-to-end Testing
Interoperability testing
quality assurance process improvement
providing information - metric

33. The process of testing to determine the efficiency of a software product
Decision condition testing
Efficiency testing
GUI Testing
Compatibility Testing

34. 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.
Fuzz Testing
Fault
Branch
Equivalence Partitioning

35. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
Branch
quality assurance process improvement
Acceptance Testing/User Acceptance Testing

36. 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
software testing
QA
Big Bang Testing

37. The expected results or performance characteristics that define whether the test cases passed or failed
best practice
Acceptance criteria
Business process-based testing
Big Bang Testing

38. Root cause analyst - base of the problem - customer satisfaction report
black box testing
quality assurance process improvement
Mutation testing
Beta Testing / Field Testing

39. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
Keyword driven Testing
Agile Testing
Branch testing

40. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Basis Path Testing
Model Based Testing
Context Driven Testing
Heuristic evaluations

41. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Conversion Testing / Migration Testing
Conformance Testing / Compliance Testing / Standards Testing
stop testing timing
SOA

42. Testing whether the system is compatible with other systems with which it should communicate.
software testing
Compatibility Testing
Accessibility Testing
Dynamic Testing

43. A test suite that exercises the full functionality of a product but does not test features in detail
Dynamic Testing
Equivalence partition Testing
Breadth Testing
Code coverage

44. Testing which covers all combinations of input values and preconditions for an element of the software under test
Exhaustive Testing
Isolation Testing
Mutation testing
Loop Testing

45. Can't see - test the functional testing - no access to code and testing is done on UI
CAST
Agile Testing
AUT
black box testing

46. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
white box testing
GUI Testing
Maintenance testing
enough of testing

47. 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.
Breadth Testing
Arc Testing / Branch Testing
Equivalence Class
Endurance Testing

48. 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
CAST
providing information - metric
test coverage
Documentation 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
Documentation Testing
Decision testing
Conformance Testing / Compliance Testing / Standards Testing
Decision table testing

50. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Acceptance criteria
Big Bang Testing
Benchmark Testing
best practice