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. 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
Interoperability testing
Defect
Invalid testing
Heuristic evaluations

2. 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.
Keyword driven Testing
Load Testing
Benchmark Testing
Quality

3. A white box test design technique in which test cases are designed to execute decision outcomes
Decision testing
Fuzz Testing
Branch testing
Data-Driven Testing

4. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Branch coverage
test coverage
Loop Testing
Equivalence Partitioning

5. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Gamma testing
Documentation Testing
Bugs
Maintenance testing

6. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
quality assurance process improvement
Coverage Testing
Equivalence partition Testing
Big Bang Testing

7. Root cause analyst - base of the problem - customer satisfaction report
stop testing timing
quality assurance process improvement
Boundary value analysis/ testing
Depth Testing

8. 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
Beta Testing / Field Testing
CAST
Grey Box Testing

9. Testing which covers all combinations of input values and preconditions for an element of the software under test
Decision condition testing
Exhaustive Testing
Branch coverage
Context Driven Testing

10. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Dependency Testing
Alpha Testing
backend testing/database testing
Authorization Testing

11. It is a whole - is the whole process form review to plans strategy and whole thing
Agile Testing
Dependency Testing
Mutation testing
QA

12. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Conversion Testing / Migration Testing
Development testing
Bugs
Ad-hoc Testing

13. Checks for memory leaks or other problems that may occur with prolonged execution
Component Testing
Dynamic Testing
Endurance Testing
Invalid testing

14. The percentage of decision outcomes that have been exercised by a test suite.
Design based Testing
Testing best practice
test coverage
Decision coverage

15. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or
Agile Testing
Conversion Testing / Migration Testing
Data flow Testing
Black Box Testing / Functional Testing

16. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
white box testing
Decision testing
Installation Testing
Development testing

17. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
stop testing timing
black box testing
Interface Testing
Authorization Testing

18. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Authorization Testing
Alpha Testing
Accessibility Testing
Bottom-up Testing

19. 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+.
Localization Testing
N+ Testing
stop testing timing
Interoperability testing

20. 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
Defect
Coverage Testing
Maintenance testing
CAST

21. This term refers to making software specifically designed for a specific locality
Integration Testing
Fuzz Testing
Localization Testing
Back-to-back testing

22. 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
Model Based Testing
Equivalence Partitioning
Acceptance Testing/User Acceptance Testing
Big Bang Testing

23. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Black Box Testing / Functional Testing
Alpha Testing
Bottom-up Testing
Conformance Testing / Compliance Testing / Standards Testing

24. 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
Context Driven Testing
architecure of SOA
Fault
Breadth Testing

25. 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
Decision coverage
Monkey Testing
Decision table testing

26. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Acceptance criteria
Statement coverage
Beta Testing / Field Testing
Exploratory Testing

27. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
black box testing
Depth Testing
providing information - metric

28. Determine whether a system meets some specified standard. external organization as complying with the standard
Conformance Testing / Compliance Testing / Standards Testing
Integration Testing
Big Bang Testing
Mutation testing

29. A white box test design technique in which test cases are designed to execute branches.
SOA
Branch testing
structural testing
Exploratory Testing

30. The testing of individual software components.
Benchmark Testing
Accessibility Testing
Ad-hoc Testing
Component Testing

31. 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
Business process-based testing
Data-Driven Testing
Compatibility Testing
Decision table testing

32. executing the software
Gamma testing
software testing
Acceptance criteria
Depth Testing

33. Testing the changes to an operational system or the impact of a changed environment to an operational system
Maintenance testing
Alpha Testing
black box testing
Decision coverage

34. 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
Basis Path Testing
exploratory testing
Conversion Testing / Migration Testing
test coverage

35. 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
Decision testing
Integration Testing
Equivalence partition Testing
Alpha Testing

36. 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
Gamma testing
Decision table testing
Acceptance criteria

37. Can't see - test the functional testing - no access to code and testing is done on UI
Statement coverage
black box testing
Branch testing
Development testing

38. 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
QA
organisation structure
Keyword driven Testing

39. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
backend testing/database testing
Localization Testing
Gamma testing
white box testing

40. Testing software through executing it.
Testing best practice
organisation structure
Dynamic Testing
Gamma testing

41. Computer Aided Software Testing
Gorilla Testing
CAST
Maintenance testing
Accessibility Testing

42. Provide critical information during project
providing information Objective
Quality
Compatibility Testing
Back-to-back testing

43. 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
Efficiency testing
Accessibility Testing
Mutation testing

44. Knows about the software and test - no proper plan
Black Box Testing / Functional Testing
exploratory testing
Keyword driven Testing
Depth Testing

45. Testing one particular module - functionality heavily
Defect
Fuzz Testing
Gorilla Testing
software testing

46. 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.
organisation structure
Maintenance testing
Defect
enough of testing

47. Black-box tests conducted once the software has been integrated
black box testing
High order tests
Invalid testing
GUI Testing

48. 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
Design based Testing
Gamma testing
Installation Testing
AUT

49. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
software testing
Testing best practice
Bottom-up Testing
Data-Driven Testing

50. Application Under Test
Authorization Testing
N+ Testing
Quality
AUT