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 white box testing technique that exercises program loops
Loop Testing
quality assurance process improvement
SOA
Interoperability testing

2. Checks for memory leaks or other problems that may occur with prolonged execution
Load Testing
Endurance Testing
Efficiency testing
Code coverage

3. Testing which covers all combinations of input values and preconditions for an element of the software under test
Invalid testing
Mutation testing
Exhaustive Testing
Acceptance criteria

4. 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
Back-to-back testing
Isolation Testing
Mutation testing
Compatibility Testing

5. The percentage of executable statements that have been exercised by a test suite.
Acceptance criteria
Fuzz Testing
Statement coverage
Authorization Testing

6. Testing in which test cases are designed based on variable usage within the code.
Fault
best practice
Authorization Testing
Data flow Testing

7. Can't see - test the functional testing - no access to code and testing is done on UI
QA
black box testing
Isolation Testing
Benchmark Testing

8. 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
Coverage Testing
Statement coverage
Gorilla Testing
Monkey Testing

9. 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
Integration Testing
Beta Testing / Field Testing
Coverage Testing
Documentation Testing

10. Application Under Test
AUT
Depth Testing
best practice
Exhaustive Testing

11. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Interface Testing
Gamma testing
functional testing
Load Testing

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.
Bugs
Branch
Equivalence Class
Model Based Testing

13. 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
Development testing
Dependency Testing
Arc Testing / Branch Testing
Acceptance Testing/User Acceptance Testing

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
Concurrency Testing
Bottom-up Testing
Branch
Breadth Testing

15. 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.
Agile Testing
Maintainability Testing / Serviceability Testing
Statement coverage
End-to-end Testing

16. Test case design
Fuzz Testing
Incremental testing
Gorilla Testing
Logic coverage Testing / Logic driven Testing / Structural

17. Root cause analyst - base of the problem - customer satisfaction report
QA
quality assurance process improvement
Beta Testing / Field Testing
Branch coverage

18. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Development testing
Ad-hoc Testing
Compatibility Testing
white box testing

19. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Depth Testing
quality assurance process improvement
Branch coverage
Alpha Testing

20. The process of testing to determine the efficiency of a software product
Efficiency testing
Agile Testing
Quality
CAST

21. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Incremental testing
structural testing
Business process-based testing
best practice

22. A white box test design technique in which test cases are designed to execute branches.
Branch testing
Breadth Testing
Heuristic evaluations
Documentation Testing

23. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Equivalence Partitioning
structural testing
Equivalence Class
Gamma testing

24. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Accessibility Testing
Localization Testing
Benchmark Testing
Business process-based testing

25. Testing software through executing it.
Incremental testing
Load Testing
Dynamic Testing
Big Bang Testing

26. The process of testing to determine the interoperability of a software product
Conformance Testing / Compliance Testing / Standards Testing
Branch
Interoperability testing
Decision condition testing

27. The percentage of decision outcomes that have been exercised by a test suite.
Depth Testing
Decision coverage
Decision testing
Maintainability Testing / Serviceability Testing

28. The testing of individual software components.
Coverage Testing
Decision condition testing
Branch coverage
Component Testing

29. executing the software
software testing
Dynamic Testing
Benchmark Testing
Breadth Testing

30. Similar to black box testing - structure of test cases in order to find defects and its strutured
quality assurance process improvement
functional testing
Black Box Testing / Functional Testing
Defect

31. 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
Arc Testing / Branch Testing
architecure of SOA
Gamma testing
backend testing/database testing

32. Provide critical information during project
Maintainability Testing / Serviceability Testing
End-to-end Testing
Branch
providing information Objective

33. Testing one particular module - functionality heavily
enough of testing
Gorilla Testing
Basis Path Testing
Defect density

34. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Gamma testing
Endurance Testing
Acceptance criteria
Isolation Testing

35. Testing concerned with the accuracy of documentation.
quality assurance process improvement
Acceptance Testing/User Acceptance Testing
Incremental testing
Documentation Testing

36. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Dependency Testing
Conformance Testing / Compliance Testing / Standards Testing
exploratory testing
white box testing

37. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Development testing
providing information - metric
backend testing/database testing
Business process-based testing

38. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Monkey Testing
Basis Path Testing
Dynamic Testing
Installation Testing

39. 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
Data-Driven Testing
Defect
Heuristic evaluations
Bottom-up Testing

40. Stakeholder stakeholder satisfaction with test results report
providing information - metric
Mutation testing
organisation structure
Bugs

41. Approach to doing something that generally give good results when applied appropriately and thoughfully
Conversion Testing / Migration Testing
Dependency Testing
Data-Driven Testing
best practice

42. Testing the changes to an operational system or the impact of a changed environment to an operational system
Fault
Maintenance testing
GUI Testing
functional testing

43. 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).
CAST
Exploratory Testing
Design based Testing
Equivalence partition Testing

44. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Equivalence Partitioning
Installation Testing
Data-Driven Testing
GUI Testing

45. 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
Boundary value analysis/ testing
Branch coverage
Gamma testing
Integration Testing

46. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
backend testing/database testing
GUI Testing
Agile Testing
organisation structure

47. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Incremental testing
Interface Testing
CAST
Development testing

48. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
test coverage
Decision table testing
Alpha Testing
Gorilla Testing

49. 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.
Arc Testing / Branch Testing
Loop Testing
Depth Testing
Gorilla Testing

50. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Decision testing
Arc Testing / Branch Testing
End-to-end Testing
enough of testing