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. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
enough of testing
quality assurance process improvement
Alpha Testing
architecure of SOA

2. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
organisation structure
Coverage Testing
functional testing
Isolation Testing

3. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Dynamic Testing
Testing best practice
Keyword driven Testing
Efficiency testing

4. 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
QA
GUI Testing
CAST
Back-to-back testing

5. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Quality
Exploratory Testing
providing information - metric
Concurrency Testing

6. 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).
Maintenance testing
Design based Testing
Model Based Testing
stop testing timing

7. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Breadth Testing
Interface Testing
Compatibility Testing
Keyword driven Testing

8. 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.
Bottom-up Testing
Gamma testing
Acceptance criteria
Arc Testing / Branch Testing

9. 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.
Development testing
test coverage
Compatibility Testing
Model Based Testing

10. 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.
Big Bang Testing
Efficiency testing
Keyword driven Testing
Monkey Testing

11. Multi-user testing geared towards determining the effects of accessing the same application code - module or database records. Identifies and measures the level of locking - deadlocking and use of single-threaded code and locking semaphores
Arc Testing / Branch Testing
Context Driven Testing
Depth Testing
Concurrency Testing

12. Determine whether a system meets some specified standard. external organization as complying with the standard
Conformance Testing / Compliance Testing / Standards Testing
High order tests
Breadth Testing
Dynamic Testing

13. 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.
Heuristic evaluations
Boundary value analysis/ testing
Endurance Testing
Defect

14. 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 coverage
Interface Testing
Decision table testing
architecure of SOA

15. 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
best practice
Maintainability Testing / Serviceability Testing
Equivalence partition Testing

16. Testing in which test cases are designed based on variable usage within the code.
Load Testing
Dependency Testing
Data flow Testing
Benchmark Testing

17. 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.
organisation structure
Arc Testing / Branch Testing
Maintenance testing
Acceptance Testing/User Acceptance Testing

18. The percentage of executable statements that have been exercised by a test suite.
Decision testing
Basis Path Testing
Statement coverage
Depth Testing

19. 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
AUT
providing information - metric
Bugs

20. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Equivalence partition Testing
organisation structure
providing information - metric
black box testing

21. Root cause analyst - base of the problem - customer satisfaction report
Isolation Testing
Documentation Testing
Acceptance criteria
quality assurance process improvement

22. A white box test design technique in which test cases are designed to execute branches.
backend testing/database testing
Branch testing
black box testing
Localization Testing

23. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Endurance Testing
GUI Testing
Logic coverage Testing / Logic driven Testing / Structural
quality assurance process improvement

24. 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.
Business process-based testing
Code coverage
Component Testing
Data flow Testing

25. Once the alpha phase is complete development enters the beta phase. Versions of the software known as beta-versions are released to a limited audience outside of the company to ensure that the product has few faults or bugs. black box
Beta Testing / Field Testing
Fuzz Testing
Basis Path Testing
Design based Testing

26. Kind of unit testing - internal working of software
Branch
Acceptance criteria
Logic coverage Testing / Logic driven Testing / Structural
structural testing

27. 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.
Defect
Loop Testing
Business process-based testing
High order tests

28. The process of testing to determine the efficiency of a software product
Back-to-back testing
white box testing
Coverage Testing
Efficiency testing

29. 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
exploratory testing
Heuristic evaluations
test coverage
Decision coverage

30. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Benchmark Testing
Acceptance Testing/User Acceptance Testing
Endurance Testing
Equivalence Partitioning

31. 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
organisation structure
Localization Testing
functional testing

32. 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
Interface Testing
Endurance Testing
Defect density

33. 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
Authorization Testing
black box testing
Equivalence Class
QA

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.
enough of testing
Fuzz Testing
Design based Testing
Fault

35. The expected results or performance characteristics that define whether the test cases passed or failed
Gamma testing
SOA
Interface Testing
Acceptance criteria

36. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Bugs
Decision condition testing
Black Box Testing / Functional Testing
enough of testing

37. 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
Testing best practice
Agile Testing
Coverage Testing
Localization Testing

38. 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
Exhaustive Testing
Dynamic Testing
Fuzz Testing
Branch

39. Approach to doing something that generally give good results when applied appropriately and thoughfully
Localization Testing
best practice
CAST
Back-to-back testing

40. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Decision table testing
Equivalence Partitioning
Ad-hoc Testing
Logic coverage Testing / Logic driven Testing / Structural

41. The percentage of decision outcomes that have been exercised by a test suite.
Monkey Testing
Interface Testing
Decision coverage
stop testing timing

42. 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
Localization Testing
test coverage
Big Bang Testing

43. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Heuristic evaluations
test coverage
Accessibility Testing
Development testing

44. Can't see - test the functional testing - no access to code and testing is done on UI
Decision table testing
stop testing timing
GUI Testing
black box testing

45. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Logic coverage Testing / Logic driven Testing / Structural
Load Testing
quality assurance process improvement
Defect density

46. 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
Agile Testing
organisation structure
Bugs
Monkey Testing

47. Testing whether the system is compatible with other systems with which it should communicate.
Fuzz Testing
Conversion Testing / Migration Testing
Endurance Testing
Compatibility Testing

48. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Context Driven Testing
Arc Testing / Branch Testing
Benchmark Testing
Quality

49. Testing whether the system meets its specified objectives for maintainability.
Coverage Testing
N+ Testing
CAST
Maintainability Testing / Serviceability Testing

50. A test that exercises a feature of a product in full detail.
organisation structure
structural testing
Depth Testing
providing information Objective