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. A test suite that exercises the full functionality of a product but does not test features in detail
organisation structure
Breadth Testing
Development testing
Design based Testing

2. 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
black box testing
Equivalence partition Testing
End-to-end Testing
Beta Testing / Field Testing

3. Testing the changes to an operational system or the impact of a changed environment to an operational system
Maintenance testing
software testing
Data-Driven Testing
Invalid testing

4. This term refers to making software specifically designed for a specific locality
Localization Testing
Black Box Testing / Functional Testing
Acceptance criteria
Gamma testing

5. The process of testing to determine the interoperability of a software product
Interoperability testing
software testing
Development testing
quality assurance process improvement

6. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Code coverage
Equivalence Partitioning
Isolation Testing
Authorization Testing

7. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Equivalence partition Testing
Decision condition testing
Back-to-back testing
Documentation Testing

8. Application Under Test
Decision coverage
Dynamic Testing
AUT
Context Driven Testing

9. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Decision table testing
Concurrency Testing
Testing best practice
Breadth Testing

10. 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.
Authorization Testing
N+ Testing
black box testing
Code coverage

11. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Data-Driven Testing
High order tests
Context Driven Testing
Alpha Testing

12. A test that exercises a feature of a product in full detail.
Data flow Testing
Bugs
Depth Testing
Bottom-up Testing

13. 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
Maintenance testing
Data-Driven Testing
Localization Testing
Dependency Testing

14. 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
AUT
Arc Testing / Branch Testing
Component Testing

15. Testing one particular module - functionality heavily
stop testing timing
Gorilla Testing
Bottom-up Testing
Grey Box Testing

16. 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
Alpha Testing
Decision table testing
Monkey Testing
Loop Testing

17. Black-box tests conducted once the software has been integrated
Endurance Testing
Isolation Testing
High order tests
Compatibility Testing

18. Determine whether a system meets some specified standard. external organization as complying with the standard
Loop Testing
providing information Objective
Conformance Testing / Compliance Testing / Standards Testing
CAST

19. Stakeholder stakeholder satisfaction with test results report
Decision condition testing
Integration Testing
Gamma testing
providing information - metric

20. Approach to doing something that generally give good results when applied appropriately and thoughfully
Monkey Testing
best practice
Beta Testing / Field Testing
providing information Objective

21. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Data-Driven Testing
Grey Box Testing
Business process-based testing
Installation Testing

22. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
Isolation Testing
Mutation testing
Back-to-back 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).
Accessibility Testing
Conversion Testing / Migration Testing
Design based Testing
Business process-based testing

24. Testing concerned with the accuracy of documentation.
architecure of SOA
Gorilla Testing
Documentation Testing
Depth Testing

25. Testing whether the system is compatible with other systems with which it should communicate.
Compatibility Testing
Big Bang Testing
Efficiency testing
Alpha Testing

26. Testing which covers all combinations of input values and preconditions for an element of the software under test
Acceptance criteria
SOA
Exhaustive Testing
High order tests

27. Kind of unit testing - internal working of software
Keyword driven Testing
test coverage
structural testing
Monkey Testing

28. 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
providing information Objective
Defect
Mutation testing
structural testing

29. 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
Interoperability testing
Defect
SOA
Coverage Testing

30. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
SOA
software testing
Interface Testing
white box testing

31. 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
Statement coverage
GUI Testing
software testing

32. 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
test coverage
Acceptance Testing/User Acceptance Testing
Authorization Testing
Agile Testing

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
Equivalence Class
quality assurance process improvement
Quality
Defect density

34. 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.
Endurance Testing
Authorization Testing
SOA
Accessibility Testing

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
High order tests
N+ Testing
Acceptance criteria

36. 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.
Code coverage
Keyword driven Testing
Back-to-back testing
Fault

37. Test case design
Integration Testing
Agile Testing
Gamma testing
Logic coverage Testing / Logic driven Testing / Structural

38. 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)
Defect density
Acceptance Testing/User Acceptance Testing
Bugs
white box testing

39. executing the software
End-to-end Testing
Conformance Testing / Compliance Testing / Standards Testing
software testing
Data flow Testing

40. It is a whole - is the whole process form review to plans strategy and whole thing
Acceptance criteria
QA
Documentation Testing
Gorilla Testing

41. The process of testing to determine the efficiency of a software product
Efficiency testing
Installation Testing
Equivalence Partitioning
Gorilla Testing

42. Testing whether the system meets its specified objectives for maintainability.
Keyword driven Testing
End-to-end Testing
Decision testing
Maintainability Testing / Serviceability Testing

43. 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
Model Based Testing
Bugs
End-to-end Testing
Equivalence Partitioning

44. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Logic coverage Testing / Logic driven Testing / Structural
Fault
Dependency Testing
Breadth Testing

45. 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.
Acceptance criteria
Defect
Conversion Testing / Migration Testing
Quality

46. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Testing best practice
Exploratory Testing
SOA
Data flow Testing

47. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Testing best practice
Decision coverage
Dependency Testing
Gamma testing

48. Testing in which test cases are designed based on variable usage within the code.
Decision condition testing
Data flow Testing
Load Testing
Invalid testing

49. Can't see - test the functional testing - no access to code and testing is done on UI
Boundary value analysis/ testing
black box testing
Data flow Testing
backend testing/database testing

50. 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.
Acceptance Testing/User Acceptance Testing
structural testing
Boundary value analysis/ testing
Equivalence Partitioning