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. 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.
QA
Fuzz Testing
Bugs
Arc Testing / Branch Testing

2. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
best practice
stop testing timing
white box testing
Benchmark Testing

3. 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
Back-to-back testing
Efficiency testing
QA
Model Based Testing

4. 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.
Fault
Documentation Testing
Invalid testing
Accessibility Testing

5. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
white box testing
Data flow Testing
Interoperability testing
Exploratory Testing

6. A white box test design technique in which test cases are designed to execute branches.
Branch testing
Boundary value analysis/ testing
Keyword driven Testing
Loop Testing

7. It is a whole - is the whole process form review to plans strategy and whole thing
quality assurance process improvement
QA
Gamma testing
SOA

8. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
Quality
QA
functional testing

9. Testing whether the system meets its specified objectives for maintainability.
Installation Testing
SOA
Data-Driven Testing
Maintainability Testing / Serviceability Testing

10. 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.
Grey Box Testing
Branch coverage
Model Based Testing
Decision condition testing

11. 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.
High order tests
organisation structure
Defect
AUT

12. 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
Accessibility Testing
Acceptance Testing/User Acceptance Testing
Data-Driven Testing
Beta Testing / Field Testing

13. 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
Mutation testing
Decision table testing
Load Testing
Equivalence Partitioning

14. 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
Installation Testing
Compatibility Testing
Decision coverage

15. The percentage of executable statements that have been exercised by a test suite.
Logic coverage Testing / Logic driven Testing / Structural
Statement coverage
SOA
Depth 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
Interoperability testing
Localization Testing
Bugs
Integration Testing

17. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Installation Testing
Code coverage
Development testing
quality assurance process improvement

18. Black-box tests conducted once the software has been integrated
Code coverage
Endurance Testing
High order tests
enough of testing

19. Testing concerned with the accuracy of documentation.
enough of testing
Acceptance criteria
Documentation Testing
Basis Path Testing

20. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Basis Path Testing
Black Box Testing / Functional Testing
Interface Testing
End-to-end Testing

21. Stakeholder stakeholder satisfaction with test results report
best practice
providing information - metric
Maintainability Testing / Serviceability Testing
Agile Testing

22. 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.
Statement coverage
QA
End-to-end Testing
Branch testing

23. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Heuristic evaluations
Incremental testing
white box testing
Loop Testing

24. 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
Invalid testing
Acceptance criteria
test coverage
Installation Testing

25. Knows about the software and test - no proper plan
providing information Objective
exploratory testing
Boundary value analysis/ testing
Fuzz Testing

26. Provide critical information during project
Loop Testing
providing information Objective
Gamma testing
organisation structure

27. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
organisation structure
Context Driven Testing
Localization Testing
Mutation testing

28. 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.
Interface Testing
Branch coverage
Monkey Testing
Boundary value analysis/ testing

29. Similar to black box testing - structure of test cases in order to find defects and its strutured
Fuzz Testing
functional testing
Conformance Testing / Compliance Testing / Standards Testing
Quality

30. Testing the changes to an operational system or the impact of a changed environment to an operational system
Maintenance testing
architecure of SOA
Decision coverage
Beta Testing / Field Testing

31. 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
Endurance Testing
Concurrency Testing
Dynamic Testing
Branch coverage

32. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Acceptance criteria
Maintainability Testing / Serviceability Testing
Localization Testing
enough of testing

33. Checks for memory leaks or other problems that may occur with prolonged execution
Endurance Testing
providing information Objective
Load Testing
Gorilla Testing

34. Testing one particular module - functionality heavily
CAST
Depth Testing
Gorilla Testing
Monkey Testing

35. 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
Component Testing
quality assurance process improvement
Gamma testing

36. The percentage of decision outcomes that have been exercised by a test suite.
Back-to-back testing
Defect density
Decision coverage
QA

37. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Testing best practice
Incremental testing
organisation structure
Endurance Testing

38. A white box testing technique that exercises program loops
Testing best practice
Loop Testing
Depth Testing
Model Based Testing

39. Depends on the schedule and risk based - business impact follow the 20-80 rules
Depth Testing
Coverage Testing
stop testing timing
best practice

40. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Decision table testing
Bugs
Business process-based testing
Logic coverage Testing / Logic driven Testing / Structural

41. The process of testing to determine the interoperability of a software product
SOA
exploratory testing
Data flow Testing
Interoperability testing

42. Kind of unit testing - internal working of software
structural testing
Loop Testing
Monkey Testing
software testing

43. Application Under Test
Authorization Testing
Integration Testing
AUT
Grey Box Testing

44. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
AUT
GUI Testing
Logic coverage Testing / Logic driven Testing / Structural
Bugs

45. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Installation Testing
white box testing
Testing best practice
Loop Testing

46. Testing which covers all combinations of input values and preconditions for an element of the software under test
Dependency Testing
Integration Testing
Incremental testing
Exhaustive Testing

47. The expected results or performance characteristics that define whether the test cases passed or failed
End-to-end Testing
Acceptance criteria
Design based Testing
Logic coverage Testing / Logic driven Testing / Structural

48. 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
Basis Path Testing
structural testing
Exploratory Testing

49. 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
Interoperability testing
architecure of SOA
Design based Testing
test coverage

50. 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
Back-to-back testing
Data flow Testing
Coverage Testing
Decision condition testing