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. 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
functional testing
Alpha Testing
Interoperability testing

2. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Incremental testing
Back-to-back testing
Compatibility Testing
software testing

3. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Model Based Testing
Invalid testing
Gorilla Testing
Testing best practice

4. 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.
Alpha Testing
Fuzz Testing
CAST
Defect

5. Can't see - test the functional testing - no access to code and testing is done on UI
N+ Testing
black box testing
Interoperability testing
Logic coverage Testing / Logic driven Testing / Structural

6. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Branch
Alpha Testing
Logic coverage Testing / Logic driven Testing / Structural
Load Testing

7. 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
Business process-based testing
Equivalence Class
Context Driven Testing
Invalid testing

8. 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)
AUT
Depth Testing
Defect density
Logic coverage Testing / Logic driven Testing / Structural

9. 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.
Endurance Testing
Code coverage
Arc Testing / Branch Testing
Coverage Testing

10. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Decision coverage
Installation Testing
Design based Testing
enough of testing

11. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Logic coverage Testing / Logic driven Testing / Structural
Keyword driven Testing
Decision condition testing
High order tests

12. 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.
High order tests
Conformance Testing / Compliance Testing / Standards Testing
Model Based Testing
Bottom-up Testing

13. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Ad-hoc Testing
GUI Testing
Business process-based testing
Fault

14. 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
Model Based Testing
Concurrency Testing
white box testing
best practice

15. executing the software
software testing
Defect density
High order tests
Incremental testing

16. The percentage of executable statements that have been exercised by a test suite.
Accessibility Testing
Coverage Testing
Boundary value analysis/ testing
Statement coverage

17. A white box test design technique in which test cases are designed to execute branches.
Acceptance criteria
AUT
Branch testing
backend testing/database testing

18. Testing which covers all combinations of input values and preconditions for an element of the software under test
Equivalence Partitioning
Keyword driven Testing
Maintainability Testing / Serviceability Testing
Exhaustive Testing

19. Provide critical information during project
providing information Objective
Breadth Testing
stop testing timing
Isolation Testing

20. The percentage of decision outcomes that have been exercised by a test suite.
Decision coverage
functional testing
Efficiency testing
best practice

21. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Isolation Testing
Dependency Testing
Depth Testing
Keyword driven Testing

22. 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
Endurance Testing
Breadth Testing
Integration Testing
white box testing

23. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Dependency Testing
Concurrency Testing
backend testing/database testing
Authorization Testing

24. The expected results or performance characteristics that define whether the test cases passed or failed
Fault
black box testing
Defect density
Acceptance criteria

25. Test case design
Bottom-up Testing
Logic coverage Testing / Logic driven Testing / Structural
Beta Testing / Field Testing
Efficiency testing

26. A test suite that exercises the full functionality of a product but does not test features in detail
Breadth Testing
Accessibility Testing
Gorilla Testing
backend testing/database testing

27. Determine whether a system meets some specified standard. external organization as complying with the standard
Ad-hoc Testing
Conformance Testing / Compliance Testing / Standards Testing
Incremental testing
Invalid testing

28. This term refers to making software specifically designed for a specific locality
Fuzz Testing
QA
Equivalence Class
Localization Testing

29. Testing concerned with the accuracy of documentation.
Development testing
Documentation Testing
SOA
Maintainability Testing / Serviceability Testing

30. The process of testing to determine the interoperability of a software product
stop testing timing
Interoperability testing
Decision condition testing
structural testing

31. 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
Defect
Compatibility Testing
Beta Testing / Field Testing
Agile Testing

32. Testing software through executing it.
Compatibility Testing
Dynamic Testing
Invalid testing
Decision table testing

33. Application Under Test
quality assurance process improvement
AUT
Monkey Testing
Loop Testing

34. Similar to black box testing - structure of test cases in order to find defects and its strutured
Agile Testing
Design based Testing
providing information - metric
functional testing

35. 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.
Design based Testing
providing information Objective
Arc Testing / Branch Testing
Ad-hoc Testing

36. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Decision coverage
Grey Box Testing
End-to-end Testing
Load Testing

37. A white box testing technique that exercises program loops
Gamma testing
Installation Testing
Business process-based testing
Loop 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
best practice
Back-to-back testing
architecure of SOA
Gorilla Testing

39. 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.
Authorization Testing
End-to-end Testing
Localization Testing
Acceptance criteria

40. A white box test design technique in which test cases are designed to execute decision outcomes
functional testing
Branch coverage
Decision testing
Code coverage

41. 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+.
Back-to-back testing
Logic coverage Testing / Logic driven Testing / Structural
Business process-based testing
N+ Testing

42. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Component Testing
Branch
Fault
Alpha Testing

43. 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
Branch
Quality
Arc Testing / Branch Testing
Fault

44. Kind of unit testing - internal working of software
Data-Driven Testing
High order tests
Context Driven Testing
structural testing

45. 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
Agile Testing
Efficiency testing
stop testing timing

46. It is a whole - is the whole process form review to plans strategy and whole thing
Decision coverage
exploratory testing
QA
High order tests

47. Testing in which test cases are designed based on variable usage within the code.
Basis Path Testing
GUI Testing
Data flow Testing
Exhaustive Testing

48. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Breadth Testing
best practice
functional testing
Branch coverage

49. Depends on the schedule and risk based - business impact follow the 20-80 rules
quality assurance process improvement
Conversion Testing / Migration Testing
stop testing timing
Agile Testing

50. Testing one particular module - functionality heavily
Gorilla Testing
Testing best practice
structural testing
Equivalence Partitioning