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. 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
Black Box Testing / Functional Testing
N+ Testing
Logic coverage Testing / Logic driven Testing / Structural
black box testing

2. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
Agile Testing
test coverage
functional testing

3. The percentage of decision outcomes that have been exercised by a test suite.
Decision coverage
N+ Testing
Depth Testing
Efficiency testing

4. Root cause analyst - base of the problem - customer satisfaction report
quality assurance process improvement
Code coverage
exploratory testing
Mutation testing

5. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared and analyzed in cases of discrepancies
Decision testing
Back-to-back testing
AUT
Acceptance Testing/User Acceptance Testing

6. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
exploratory testing
enough of testing
Fault
Depth Testing

7. Testing in which test cases are designed based on variable usage within the code.
Development testing
Compatibility Testing
Data flow Testing
Agile Testing

8. A black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table
Logic coverage Testing / Logic driven Testing / Structural
Conversion Testing / Migration Testing
Decision table testing
Coverage Testing

9. 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.
quality assurance process improvement
Acceptance Testing/User Acceptance Testing
Fault
Business process-based testing

10. Checks for memory leaks or other problems that may occur with prolonged execution
Endurance Testing
exploratory testing
End-to-end Testing
Load Testing

11. 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.
Authorization Testing
N+ Testing
Concurrency Testing
Big Bang Testing

12. executing the software
Data flow Testing
N+ Testing
software testing
Load Testing

13. 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
Agile Testing
architecure of SOA
Load Testing
Data flow Testing

14. 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
CAST
SOA
Documentation Testing
Decision table testing

15. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Branch testing
Acceptance criteria
Decision condition testing
Back-to-back testing

16. 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
Equivalence Partitioning
Bugs
QA
SOA

17. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Big Bang Testing
Decision coverage
Statement coverage
Defect density

18. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Defect
backend testing/database testing
Equivalence Class
Code coverage

19. 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
Breadth Testing
Equivalence Class
QA
Agile Testing

20. Application Under Test
Data flow Testing
AUT
Invalid testing
Branch coverage

21. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Black Box Testing / Functional Testing
Concurrency Testing
Beta Testing / Field Testing
organisation structure

22. Similar to black box testing - structure of test cases in order to find defects and its strutured
Authorization Testing
quality assurance process improvement
AUT
functional testing

23. 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
Integration Testing
Localization Testing
Keyword driven Testing
Data-Driven Testing

24. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Equivalence Partitioning
Data flow Testing
Dependency Testing
Isolation Testing

25. The percentage of executable statements that have been exercised by a test suite.
Statement coverage
Invalid testing
Basis Path Testing
GUI Testing

26. 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
Monkey Testing
Data-Driven Testing
Conversion Testing / Migration Testing
Boundary value analysis/ testing

27. 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.
black box testing
Dependency Testing
Code coverage
Back-to-back testing

28. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Load Testing
stop testing timing
Localization Testing
Efficiency testing

29. A white box testing technique that exercises program loops
Loop Testing
Mutation testing
white box testing
Maintainability Testing / Serviceability Testing

30. 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
Dynamic Testing
Bottom-up Testing
Coverage Testing
GUI Testing

31. The expected results or performance characteristics that define whether the test cases passed or failed
Mutation testing
Acceptance criteria
Fuzz Testing
Arc Testing / Branch Testing

32. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
Dependency Testing
Mutation testing
Ad-hoc Testing

33. Testing whether the system meets its specified objectives for maintainability.
Maintainability Testing / Serviceability Testing
Conformance Testing / Compliance Testing / Standards Testing
Ad-hoc Testing
Incremental testing

34. Provide critical information during project
Beta Testing / Field Testing
Exhaustive Testing
providing information Objective
Data-Driven Testing

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

36. Testing one particular module - functionality heavily
Gorilla Testing
Quality
Beta Testing / Field Testing
Model Based Testing

37. Approach to doing something that generally give good results when applied appropriately and thoughfully
Development testing
Context Driven Testing
best practice
Component Testing

38. Knows about the software and test - no proper plan
best practice
backend testing/database testing
exploratory testing
stop testing timing

39. Determine whether a system meets some specified standard. external organization as complying with the standard
Maintainability Testing / Serviceability Testing
Conformance Testing / Compliance Testing / Standards Testing
Quality
Statement coverage

40. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Accessibility Testing
Isolation Testing
QA
Grey Box Testing

41. Computer Aided Software Testing
Load Testing
CAST
Acceptance Testing/User Acceptance Testing
Boundary value analysis/ testing

42. 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
Back-to-back testing
Arc Testing / Branch Testing
Dependency Testing
Installation Testing

43. The process of testing to determine the interoperability of a software product
Arc Testing / Branch Testing
N+ Testing
Mutation testing
Interoperability testing

44. It is a whole - is the whole process form review to plans strategy and whole thing
QA
Interface Testing
Isolation Testing
Dependency Testing

45. 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.
Accessibility Testing
Statement coverage
End-to-end Testing
Code coverage

46. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
CAST
Concurrency Testing
Branch coverage
Alpha Testing

47. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Development testing
Quality
exploratory testing
Equivalence Partitioning

48. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Agile Testing
Branch
Maintenance testing
Design based Testing

49. Stakeholder stakeholder satisfaction with test results report
functional testing
providing information - metric
Code coverage
best practice

50. Depends on the schedule and risk based - business impact follow the 20-80 rules
Business process-based testing
stop testing timing
best practice
Equivalence Class