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 where no incremental testing takes place prior to all the system's components being combined to form the system.
Big Bang Testing
Documentation Testing
Isolation Testing
Exploratory Testing

2. 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.
Depth Testing
Defect
Decision coverage
Data flow Testing

3. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
architecure of SOA
Acceptance criteria
Testing best practice

4. The process of testing to determine the interoperability of a software product
providing information Objective
Bugs
Interoperability testing
enough of testing

5. A test suite that exercises the full functionality of a product but does not test features in detail
End-to-end Testing
white box testing
Data flow Testing
Breadth Testing

6. 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
Agile Testing
Integration Testing
Code coverage

7. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Decision condition testing
Incremental testing
Equivalence Partitioning
Black Box Testing / Functional Testing

8. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Benchmark Testing
Ad-hoc Testing
Concurrency Testing
Branch testing

9. 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
Gamma testing
Logic coverage Testing / Logic driven Testing / Structural
Breadth Testing
Monkey Testing

10. 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.
Branch testing
Monkey Testing
Context Driven Testing
SOA

11. 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.
Exploratory Testing
Boundary value analysis/ testing
Dynamic Testing
Localization Testing

12. Provide critical information during project
Equivalence partition Testing
structural testing
End-to-end Testing
providing information Objective

13. 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
Beta Testing / Field Testing
Agile Testing
Interface Testing
Equivalence Class

14. Determine whether a system meets some specified standard. external organization as complying with the standard
Conformance Testing / Compliance Testing / Standards Testing
End-to-end Testing
Ad-hoc Testing
Load Testing

15. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
Gorilla Testing
QA
Data-Driven Testing

16. 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
Breadth Testing
Decision coverage
AUT
Concurrency Testing

17. Test case design
test coverage
organisation structure
Logic coverage Testing / Logic driven Testing / Structural
Keyword driven Testing

18. 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
backend testing/database testing
Ad-hoc Testing
Design based Testing

19. 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.
Installation Testing
Boundary value analysis/ testing
Fuzz Testing
Testing best practice

20. A white box testing technique that exercises program loops
Loop Testing
Load Testing
Concurrency Testing
Coverage Testing

21. Checks for memory leaks or other problems that may occur with prolonged execution
Exhaustive Testing
Efficiency testing
Equivalence Class
Endurance Testing

22. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Quality
Defect density
Grey Box Testing
Conversion Testing / Migration Testing

23. Depends on the schedule and risk based - business impact follow the 20-80 rules
stop testing timing
functional testing
Defect density
quality assurance process improvement

24. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
Conversion Testing / Migration Testing
providing information - metric
Development testing

25. executing the software
software testing
Testing best practice
Documentation Testing
Load Testing

26. 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.
Big Bang Testing
Loop Testing
Endurance Testing
Arc Testing / Branch Testing

27. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Business process-based testing
Gamma testing
Testing best practice
End-to-end Testing

28. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Breadth Testing
Exploratory Testing
Isolation Testing
stop testing timing

29. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Authorization Testing
white box testing
Bottom-up Testing
Exploratory Testing

30. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Benchmark Testing
Ad-hoc Testing
Business process-based testing
Compatibility Testing

31. 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
Business process-based testing
Bugs
Integration Testing
CAST

32. A white box test case design techniques that uses the algorithmic flow of the program to design tests
software testing
Basis Path Testing
test coverage
Branch

33. 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
Logic coverage Testing / Logic driven Testing / Structural
Design based Testing
Acceptance Testing/User Acceptance Testing
Equivalence Class

34. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Context Driven Testing
Branch testing
Exploratory Testing
Loop Testing

35. 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
Heuristic evaluations
Efficiency testing
Alpha Testing
Decision table testing

36. Approach to doing something that generally give good results when applied appropriately and thoughfully
Acceptance Testing/User Acceptance Testing
best practice
Design based Testing
Branch

37. Testing in which test cases are designed based on variable usage within the code.
Heuristic evaluations
Ad-hoc Testing
Data flow Testing
Localization Testing

38. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Accessibility Testing
Decision testing
Depth Testing
Fault

39. 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
Ad-hoc Testing
Efficiency testing
Beta Testing / Field Testing
stop testing timing

40. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
Quality
Conversion Testing / Migration Testing
Decision coverage

41. 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.
Bugs
Model Based Testing
SOA
Fault

42. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Bugs
Decision condition testing
Acceptance criteria
Statement coverage

43. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Agile Testing
Installation Testing
structural testing
backend testing/database testing

44. Application Under Test
Statement coverage
Conformance Testing / Compliance Testing / Standards Testing
Concurrency Testing
AUT

45. It is a whole - is the whole process form review to plans strategy and whole thing
stop testing timing
Boundary value analysis/ testing
Keyword driven Testing
QA

46. Testing whether the system meets its specified objectives for maintainability.
Maintainability Testing / Serviceability Testing
Back-to-back testing
backend testing/database testing
CAST

47. Testing concerned with the accuracy of documentation.
Equivalence partition Testing
Branch testing
Incremental testing
Documentation Testing

48. 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
Logic coverage Testing / Logic driven Testing / Structural
Benchmark Testing
Breadth Testing

49. Stakeholder stakeholder satisfaction with test results report
Monkey Testing
Decision condition testing
AUT
providing information - metric

50. 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
Keyword driven Testing
backend testing/database testing
Isolation Testing
Data-Driven Testing