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. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Efficiency testing
Grey Box Testing
best practice
Load Testing

2. 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
Breadth Testing
Defect density
Boundary value analysis/ testing
Quality

3. 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.
Statement coverage
Defect
Model Based Testing
High order tests

4. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Decision condition testing
Acceptance Testing/User Acceptance Testing
Benchmark Testing
High order tests

5. 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.
Big Bang Testing
Interface Testing
Context Driven Testing
Fuzz Testing

6. Approach to doing something that generally give good results when applied appropriately and thoughfully
organisation structure
Breadth Testing
best practice
backend testing/database testing

7. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Interface Testing
Branch
Authorization Testing
Development testing

8. 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
Boundary value analysis/ testing
Conformance Testing / Compliance Testing / Standards Testing
Logic coverage Testing / Logic driven Testing / Structural

9. 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
Development testing
Incremental testing
Monkey Testing
Data-Driven Testing

10. Kind of unit testing - internal working of software
software testing
Quality
Branch testing
structural testing

11. 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
N+ Testing
Localization Testing
Development testing

12. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Incremental testing
Branch coverage
organisation structure
Concurrency Testing

13. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
Component Testing
Fuzz Testing
Dynamic Testing

14. Testing whether the system meets its specified objectives for maintainability.
Maintainability Testing / Serviceability Testing
stop testing timing
Interface Testing
Back-to-back testing

15. 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
Conversion Testing / Migration Testing
Efficiency testing
Acceptance Testing/User Acceptance Testing
Equivalence partition Testing

16. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Decision coverage
Exploratory Testing
Fault
Data flow Testing

17. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Accessibility Testing
white box testing
QA
structural testing

18. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Dependency Testing
Dynamic Testing
Gamma testing
Big Bang Testing

19. Similar to black box testing - structure of test cases in order to find defects and its strutured
best practice
Component Testing
functional testing
Quality

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
Compatibility Testing
Black Box Testing / Functional Testing
quality assurance process improvement
Isolation Testing

21. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Fault
Acceptance criteria
Alpha Testing
Load Testing

22. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Loop Testing
Testing best practice
Component Testing
Accessibility Testing

23. 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).
Fault
Accessibility Testing
Design based Testing
Isolation Testing

24. A white box test design technique in which test cases are designed to execute decision outcomes
Decision testing
Defect density
Exploratory Testing
Integration Testing

25. 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.
providing information - metric
software testing
Concurrency Testing
Keyword driven Testing

26. Determine whether a system meets some specified standard. external organization as complying with the standard
Efficiency testing
Breadth Testing
Conformance Testing / Compliance Testing / Standards Testing
Branch

27. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
software testing
Acceptance Testing/User Acceptance Testing
Alpha Testing
Testing best practice

28. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
quality assurance process improvement
QA
test coverage

29. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Business process-based testing
quality assurance process improvement
GUI Testing
Alpha Testing

30. This term refers to making software specifically designed for a specific locality
Isolation Testing
Localization Testing
Maintenance testing
Alpha Testing

31. Computer Aided Software Testing
test coverage
CAST
Decision coverage
Integration Testing

32. A white box testing technique that exercises program loops
Loop Testing
End-to-end Testing
Defect density
structural testing

33. The expected results or performance characteristics that define whether the test cases passed or failed
Context Driven Testing
Acceptance criteria
Mutation testing
N+ Testing

34. A test suite that exercises the full functionality of a product but does not test features in detail
Breadth Testing
Conformance Testing / Compliance Testing / Standards Testing
Interface Testing
Depth Testing

35. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Acceptance criteria
Data flow Testing
Benchmark Testing
Business process-based testing

36. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
High order tests
Exhaustive Testing
Interoperability testing

37. 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
organisation structure
Branch
Mutation testing
Beta Testing / Field Testing

38. The process of testing to determine the interoperability of a software product
Branch
Grey Box Testing
Interoperability testing
Invalid testing

39. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Integration Testing
AUT
Basis Path Testing
stop testing timing

40. 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.
Localization Testing
Conformance Testing / Compliance Testing / Standards Testing
providing information Objective
Fault

41. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Documentation Testing
Conformance Testing / Compliance Testing / Standards Testing
Loop Testing
Isolation Testing

42. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Bugs
Design based Testing
Conversion Testing / Migration Testing
architecure of SOA

43. Root cause analyst - base of the problem - customer satisfaction report
quality assurance process improvement
Boundary value analysis/ testing
Keyword driven Testing
Branch

44. Testing software through executing it.
Design based Testing
Business process-based testing
Dynamic Testing
Localization Testing

45. 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
Integration Testing
Acceptance Testing/User Acceptance Testing
functional testing
Compatibility Testing

46. 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
Statement coverage
black box testing
Bugs
Endurance Testing

47. 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
Bottom-up Testing
Arc Testing / Branch Testing
Development testing

48. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Acceptance criteria
Basis Path Testing
Incremental testing
Alpha Testing

49. Stakeholder stakeholder satisfaction with test results report
Mutation testing
providing information - metric
Equivalence Partitioning
Decision table testing

50. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Gamma testing
Exhaustive Testing
Alpha Testing
test coverage