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. 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
Basis Path Testing
Integration Testing
Black Box Testing / Functional Testing
Accessibility Testing

2. Root cause analyst - base of the problem - customer satisfaction report
quality assurance process improvement
Decision testing
Decision table testing
Bugs

3. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
test coverage
Development testing
SOA
Alpha Testing

4. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
enough of testing
Interface Testing
backend testing/database testing
Equivalence Class

5. Testing using input values that should be rejected by the component or system
Accessibility Testing
Endurance Testing
Concurrency Testing
Invalid testing

6. 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
Conversion Testing / Migration Testing
Heuristic evaluations
Ad-hoc Testing
Dependency Testing

7. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
High order tests
Acceptance criteria
white box testing
Conformance Testing / Compliance Testing / Standards Testing

8. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Interface Testing
Ad-hoc Testing
Testing best practice
Exploratory Testing

9. Testing concerned with the accuracy of documentation.
Interoperability testing
Documentation Testing
Ad-hoc Testing
Endurance Testing

10. 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
test coverage
Acceptance Testing/User Acceptance Testing
Beta Testing / Field Testing
organisation structure

11. 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
Conformance Testing / Compliance Testing / Standards Testing
Development testing
architecure of SOA
Data-Driven Testing

12. 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
GUI Testing
Defect
CAST

13. Provide critical information during project
white box testing
Alpha Testing
providing information Objective
architecure of SOA

14. A test that exercises a feature of a product in full detail.
CAST
GUI Testing
Defect
Depth Testing

15. 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.
Boundary value analysis/ testing
GUI Testing
Big Bang Testing
Exploratory Testing

16. 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.
Basis Path Testing
Interoperability testing
Context Driven Testing
Mutation testing

17. Approach to doing something that generally give good results when applied appropriately and thoughfully
AUT
Quality
best practice
Ad-hoc Testing

18. 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
Invalid testing
Authorization Testing
Branch
Mutation testing

19. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Statement coverage
Decision condition testing
Gamma testing
Business process-based testing

20. 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.
End-to-end Testing
Development testing
Equivalence Partitioning
Grey Box Testing

21. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
Big Bang Testing
High order tests
Loop Testing

22. 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.
Loop Testing
Conversion Testing / Migration Testing
Agile Testing
Keyword driven Testing

23. 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
providing information Objective
Decision condition testing
AUT

24. 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).
Dependency Testing
Authorization Testing
stop testing timing
Design based Testing

25. Black-box tests conducted once the software has been integrated
black box testing
Business process-based testing
High order tests
Load Testing

26. 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
Model Based Testing
N+ Testing
Installation Testing

27. It is a whole - is the whole process form review to plans strategy and whole thing
Mutation testing
QA
functional testing
Invalid testing

28. Stakeholder stakeholder satisfaction with test results report
Mutation testing
N+ Testing
white box testing
providing information - metric

29. Testing whether the system meets its specified objectives for maintainability.
Breadth Testing
Beta Testing / Field Testing
Isolation Testing
Maintainability Testing / Serviceability Testing

30. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Interface Testing
Testing best practice
Grey Box Testing
Interoperability testing

31. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Ad-hoc Testing
Basis Path Testing
exploratory testing
architecure of SOA

32. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Invalid testing
Decision condition testing
Defect density
Business process-based testing

33. A test suite that exercises the full functionality of a product but does not test features in detail
Maintenance testing
Data flow Testing
Basis Path Testing
Breadth Testing

34. 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
software testing
backend testing/database testing
Coverage Testing
Data-Driven Testing

35. This term refers to making software specifically designed for a specific locality
Equivalence Partitioning
Localization Testing
Acceptance Testing/User Acceptance Testing
Conversion Testing / Migration Testing

36. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Equivalence Partitioning
software testing
Benchmark Testing
Accessibility Testing

37. 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.
Boundary value analysis/ testing
N+ Testing
Code coverage
Fuzz Testing

38. executing the software
software testing
Design based Testing
Data flow Testing
Exploratory Testing

39. Test case design
Loop Testing
Defect density
Logic coverage Testing / Logic driven Testing / Structural
Back-to-back testing

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.
Fault
Breadth Testing
backend testing/database testing
exploratory testing

41. 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.
Accessibility Testing
architecure of SOA
Arc Testing / Branch Testing
Defect

42. The percentage of decision outcomes that have been exercised by a test suite.
Invalid testing
Decision coverage
CAST
Incremental testing

43. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Data flow Testing
Defect
Branch
Load Testing

44. Knows about the software and test - no proper plan
Equivalence Class
exploratory testing
enough of testing
Decision coverage

45. Kind of unit testing - internal working of software
Context Driven Testing
structural testing
Decision condition testing
Interface Testing

46. Testing in which test cases are designed based on variable usage within the code.
test coverage
Logic coverage Testing / Logic driven Testing / Structural
Decision coverage
Data flow Testing

47. Testing which covers all combinations of input values and preconditions for an element of the software under test
Branch testing
CAST
Incremental testing
Exhaustive Testing

48. The process of testing to determine the efficiency of a software product
Data-Driven Testing
Efficiency testing
exploratory testing
Concurrency Testing

49. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
enough of testing
Back-to-back testing
black box testing
GUI Testing

50. 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
Big Bang Testing
Ad-hoc Testing
Testing best practice