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. Testing concerned with the accuracy of documentation.
Heuristic evaluations
stop testing timing
Logic coverage Testing / Logic driven Testing / Structural
Documentation Testing

2. 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
enough of testing
Branch testing
Load Testing
Back-to-back testing

3. Informal method of usability inspection in the field of human-computer interaction. identifying the usability problems . involves evaluators examining the interface and judging its compliance
Heuristic evaluations
stop testing timing
Alpha Testing
Defect density

4. The process of testing to determine the interoperability of a software product
test coverage
Arc Testing / Branch Testing
Interoperability testing
Business process-based testing

5. 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).
Design based Testing
black box testing
Heuristic evaluations
Acceptance Testing/User Acceptance Testing

6. Kind of unit testing - internal working of software
Bottom-up Testing
structural testing
organisation structure
CAST

7. Can't see - test the functional testing - no access to code and testing is done on UI
black box testing
Defect density
Agile Testing
Heuristic evaluations

8. Testing which covers all combinations of input values and preconditions for an element of the software under test
Decision table testing
Exhaustive Testing
Dynamic Testing
Design based Testing

9. 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
Decision testing
Acceptance Testing/User Acceptance Testing
backend testing/database testing
Business process-based testing

10. 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.
Model Based Testing
black box testing
Fuzz Testing
Dependency Testing

11. 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.
Dynamic Testing
Branch coverage
Authorization Testing
Fuzz Testing

12. 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.
white box testing
Fuzz Testing
Bottom-up Testing
providing information - metric

13. Root cause analyst - base of the problem - customer satisfaction report
enough of testing
quality assurance process improvement
Fuzz Testing
Localization Testing

14. The percentage of executable statements that have been exercised by a test suite.
Quality
Statement coverage
white box testing
stop testing timing

15. Testing software through executing it.
backend testing/database testing
Dynamic Testing
Concurrency Testing
Testing best practice

16. 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.
best practice
providing information - metric
Exhaustive Testing
Boundary value analysis/ testing

17. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
End-to-end Testing
Efficiency testing
Black Box Testing / Functional Testing
Accessibility Testing

18. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Basis Path Testing
organisation structure
Concurrency Testing
Accessibility Testing

19. executing the software
Boundary value analysis/ testing
software testing
black box testing
Context Driven Testing

20. 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.
Conformance Testing / Compliance Testing / Standards Testing
Authorization Testing
Back-to-back testing
Mutation testing

21. Computer Aided Software Testing
architecure of SOA
Documentation Testing
CAST
Dynamic Testing

22. This term refers to making software specifically designed for a specific locality
architecure of SOA
Incremental testing
Localization Testing
Isolation Testing

23. 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.
structural testing
Fault
Defect
Dependency Testing

24. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
N+ Testing
GUI Testing
Loop Testing
Bottom-up Testing

25. Knows about the software and test - no proper plan
Interoperability testing
CAST
exploratory testing
Bugs

26. Test case design
software testing
Logic coverage Testing / Logic driven Testing / Structural
Acceptance Testing/User Acceptance Testing
Loop Testing

27. 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
Branch testing
Accessibility Testing
Gamma 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
Monkey Testing
Coverage Testing
Isolation Testing
Keyword driven Testing

29. 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
Decision table testing
Installation Testing
Exhaustive Testing
Authorization Testing

30. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Big Bang Testing
Alpha Testing
Model Based Testing
Conversion Testing / Migration Testing

31. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Benchmark Testing
End-to-end Testing
Branch coverage
best practice

32. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Dependency Testing
Exploratory Testing
structural testing
Branch coverage

33. 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
test coverage
Data-Driven Testing
structural testing
Maintainability Testing / Serviceability Testing

34. 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)
Ad-hoc Testing
Branch coverage
QA
Defect density

35. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Big Bang Testing
Business process-based testing
Grey Box Testing
functional testing

36. Testing using input values that should be rejected by the component or system
Breadth Testing
Benchmark Testing
Invalid testing
Boundary value analysis/ testing

37. A test suite that exercises the full functionality of a product but does not test features in detail
Monkey Testing
Breadth Testing
quality assurance process improvement
Code coverage

38. 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+.
Keyword driven Testing
N+ Testing
GUI Testing
Coverage Testing

39. 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
QA
Incremental testing
Bugs
High order tests

40. The percentage of decision outcomes that have been exercised by a test suite.
Heuristic evaluations
Data-Driven Testing
black box testing
Decision coverage

41. A white box test design technique in which test cases are designed to execute decision outcomes
Decision testing
Design based Testing
Defect density
Loop Testing

42. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
organisation structure
Alpha Testing
Defect
black box testing

43. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Branch testing
Testing best practice
Authorization Testing
black box testing

44. Similar to black box testing - structure of test cases in order to find defects and its strutured
functional testing
CAST
End-to-end Testing
High order tests

45. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Fuzz Testing
Decision table testing
Gamma testing
Agile Testing

46. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Decision table testing
backend testing/database testing
white box testing
Fault

47. Testing in which test cases are designed based on variable usage within the code.
exploratory testing
providing information - metric
Accessibility Testing
Data flow Testing

48. It is a whole - is the whole process form review to plans strategy and whole thing
QA
Monkey Testing
Development testing
Heuristic evaluations

49. A white box testing technique that exercises program loops
Mutation testing
Loop Testing
Keyword driven Testing
Concurrency Testing

50. A white box test design technique in which test cases are designed to execute branches.
Gamma testing
Branch testing
Decision table testing
quality assurance process improvement