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. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Accessibility Testing
Bugs
organisation structure
Defect density

2. 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
Incremental testing
Interoperability testing
Boundary value analysis/ testing
Black Box Testing / Functional Testing

3. Determine whether a system meets some specified standard. external organization as complying with the standard
Model Based Testing
Conformance Testing / Compliance Testing / Standards Testing
Decision coverage
GUI Testing

4. 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
Quality
Fault
Breadth Testing

5. Application Under Test
AUT
Logic coverage Testing / Logic driven Testing / Structural
End-to-end Testing
Decision testing

6. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Dependency Testing
architecure of SOA
High order tests
Endurance Testing

7. Testing whether the system meets its specified objectives for maintainability.
Logic coverage Testing / Logic driven Testing / Structural
Concurrency Testing
Maintainability Testing / Serviceability Testing
Decision table testing

8. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Context Driven Testing
Interface Testing
SOA
Incremental testing

9. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
providing information - metric
Branch testing
enough of testing
Development testing

10. Depends on the schedule and risk based - business impact follow the 20-80 rules
stop testing timing
Defect
Gamma testing
Interface Testing

11. Testing the changes to an operational system or the impact of a changed environment to an operational system
Model Based Testing
Maintenance testing
QA
Endurance Testing

12. 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).
Decision coverage
Design based Testing
Gamma testing
Arc Testing / Branch Testing

13. Stakeholder stakeholder satisfaction with test results report
Agile Testing
providing information - metric
AUT
Black Box Testing / Functional Testing

14. 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+.
N+ Testing
End-to-end Testing
Data-Driven Testing
QA

15. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Fuzz Testing
Agile Testing
Conversion Testing / Migration Testing
Heuristic evaluations

16. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
backend testing/database testing
Big Bang Testing
Isolation Testing
Breadth Testing

17. 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
quality assurance process improvement
Gorilla Testing
Branch coverage
test coverage

18. 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
Coverage Testing
Decision table testing
providing information Objective
Data-Driven Testing

19. 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.
End-to-end Testing
Installation Testing
Bottom-up Testing
Invalid testing

20. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
structural testing
Localization Testing
Fuzz Testing

21. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
structural testing
Data-Driven Testing
Development testing
Bottom-up Testing

22. Test case design
Exhaustive Testing
Logic coverage Testing / Logic driven Testing / Structural
CAST
Bottom-up Testing

23. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Agile Testing
Acceptance Testing/User Acceptance Testing
Acceptance criteria
Defect density

24. A white box test design technique in which test cases are designed to execute decision outcomes
stop testing timing
Quality
Back-to-back testing
Decision testing

25. 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
Monkey Testing
Localization Testing
enough of testing

26. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Exploratory Testing
Maintainability Testing / Serviceability Testing
Decision condition testing
Back-to-back testing

27. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
best practice
Maintenance testing
Ad-hoc Testing
Gamma testing

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.
software testing
Branch coverage
SOA
Fuzz Testing

29. 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
Efficiency testing
Heuristic evaluations
Integration Testing
Defect density

30. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Equivalence Class
Interoperability testing
Exploratory Testing
Dynamic Testing

31. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
white box testing
Fuzz Testing
Isolation Testing
enough of testing

32. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Mutation testing
Basis Path Testing
Gorilla Testing
Decision condition 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.
providing information Objective
Model Based Testing
N+ Testing
AUT

34. 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.
Grey Box Testing
QA
enough of testing
Authorization Testing

35. A test suite that exercises the full functionality of a product but does not test features in detail
Dependency Testing
Loop Testing
Breadth Testing
Black Box Testing / Functional Testing

36. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
structural testing
Equivalence partition Testing
Quality
Authorization Testing

37. 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
Authorization Testing
Decision testing
Equivalence Partitioning
Monkey Testing

38. 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
architecure of SOA
Back-to-back testing
CAST
Endurance Testing

39. A test that exercises a feature of a product in full detail.
stop testing timing
Monkey Testing
Gorilla Testing
Depth Testing

40. 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
Quality
Integration Testing
enough of testing
Mutation testing

41. 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.
Maintainability Testing / Serviceability Testing
Branch coverage
Code coverage
structural testing

42. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Business process-based testing
Exhaustive Testing
Heuristic evaluations
stop testing timing

43. The percentage of decision outcomes that have been exercised by a test suite.
Branch testing
Authorization Testing
Decision coverage
Branch coverage

44. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Acceptance Testing/User Acceptance Testing
Isolation Testing
Exhaustive Testing
Design based Testing

45. Testing one particular module - functionality heavily
Gorilla Testing
Ad-hoc Testing
Quality
Compatibility Testing

46. 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
Defect density
organisation structure
Accessibility Testing

47. Testing software through executing it.
stop testing timing
Dynamic Testing
Equivalence Class
Interoperability testing

48. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Branch testing
functional testing
Load Testing
Compatibility Testing

49. 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
Heuristic evaluations
Design based Testing
white box testing
Bugs

50. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Data flow Testing
Exhaustive Testing
Branch coverage
Defect