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. 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
exploratory testing
enough of testing
Accessibility Testing

2. 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
Code coverage
Acceptance Testing/User Acceptance Testing
Development testing
Installation Testing

3. A test suite that exercises the full functionality of a product but does not test features in detail
Interoperability testing
Authorization Testing
Acceptance Testing/User Acceptance Testing
Breadth Testing

4. Determine whether a system meets some specified standard. external organization as complying with the standard
Data-Driven Testing
Conformance Testing / Compliance Testing / Standards Testing
Decision table testing
Grey Box Testing

5. The expected results or performance characteristics that define whether the test cases passed or failed
Depth Testing
Black Box Testing / Functional Testing
Acceptance criteria
Decision testing

6. 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
Accessibility Testing
Bugs
Exploratory Testing

7. 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
Loop Testing
Acceptance Testing/User Acceptance Testing
test coverage
Equivalence partition Testing

8. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
AUT
Monkey Testing
Load Testing
Keyword driven Testing

9. The totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs." defined by ISO 8402 1986
Quality
Heuristic evaluations
Basis Path Testing
architecure of SOA

10. 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
Ad-hoc Testing
Quality
CAST

11. Provide critical information during project
Depth Testing
providing information Objective
Conformance Testing / Compliance Testing / Standards Testing
Integration Testing

12. 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.
Gorilla Testing
Context Driven Testing
AUT
Testing best practice

13. The process of testing to determine the interoperability of a software product
Coverage Testing
End-to-end Testing
Interoperability testing
N+ Testing

14. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Benchmark Testing
End-to-end Testing
Isolation Testing
AUT

15. Application Under Test
Decision coverage
Integration Testing
AUT
Load Testing

16. Knows about the software and test - no proper plan
exploratory testing
functional testing
white box testing
Benchmark Testing

17. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Installation Testing
Context Driven Testing
Testing best practice
Alpha Testing

18. This term refers to making software specifically designed for a specific locality
providing information - metric
Localization Testing
Breadth Testing
Incremental testing

19. 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
Fuzz Testing
Beta Testing / Field Testing
Keyword driven Testing
Dynamic Testing

20. 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
Defect density
enough of testing
Decision table testing
Arc Testing / Branch Testing

21. The percentage of executable statements that have been exercised by a test suite.
N+ Testing
Invalid testing
Bugs
Statement coverage

22. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Depth Testing
backend testing/database testing
Design based Testing
white box testing

23. Testing the changes to an operational system or the impact of a changed environment to an operational system
providing information - metric
Design based Testing
Acceptance Testing/User Acceptance Testing
Maintenance testing

24. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
AUT
Branch coverage
Business process-based testing
Bugs

25. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Gamma testing
providing information - metric
Dependency Testing
software testing

26. Checks for memory leaks or other problems that may occur with prolonged execution
Depth Testing
Endurance Testing
stop testing timing
QA

27. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Incremental testing
Grey Box Testing
organisation structure
Data flow Testing

28. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Maintainability Testing / Serviceability Testing
Equivalence Partitioning
Quality
Development testing

29. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Decision condition testing
Loop Testing
Fault
Localization Testing

30. Can't see - test the functional testing - no access to code and testing is done on UI
Equivalence Class
best practice
black box testing
High order tests

31. 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).
Decision condition testing
Design based Testing
Back-to-back testing
CAST

32. Testing concerned with the accuracy of documentation.
Dependency Testing
Code coverage
Documentation Testing
Heuristic evaluations

33. Black-box tests conducted once the software has been integrated
Boundary value analysis/ testing
High order tests
AUT
Branch

34. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Heuristic evaluations
test coverage
Equivalence partition Testing
Interoperability testing

35. 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.
Conversion Testing / Migration Testing
Bugs
Code coverage
exploratory testing

36. 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
Statement coverage
backend testing/database testing
Data-Driven Testing
software testing

37. 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
Basis Path Testing
Compatibility Testing
Concurrency Testing

38. Computer Aided Software Testing
CAST
Installation Testing
Maintenance testing
Big Bang Testing

39. 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
Back-to-back testing
Exhaustive Testing
Accessibility Testing
SOA

40. A test that exercises a feature of a product in full detail.
Fault
Decision testing
Business process-based testing
Depth Testing

41. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Conversion Testing / Migration Testing
Decision condition testing
Dependency Testing
Alpha Testing

42. 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.
software testing
Authorization Testing
stop testing timing
Context Driven Testing

43. Testing which covers all combinations of input values and preconditions for an element of the software under test
Exhaustive Testing
Big Bang Testing
Branch testing
Loop Testing

44. A basic block that can be selected for execution based on a program construct in which one of two or more alternative program path is available
Maintainability Testing / Serviceability Testing
Branch
Testing best practice
Big Bang Testing

45. Depends on the schedule and risk based - business impact follow the 20-80 rules
Acceptance Testing/User Acceptance Testing
quality assurance process improvement
Component Testing
stop testing timing

46. Test case design
Back-to-back testing
Logic coverage Testing / Logic driven Testing / Structural
Business process-based testing
exploratory testing

47. 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.
stop testing timing
Equivalence Class
Model Based Testing
Branch coverage

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

49. 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.
End-to-end Testing
Endurance Testing
Incremental testing
Coverage Testing

50. Testing using input values that should be rejected by the component or system
Invalid testing
Localization Testing
Integration Testing
exploratory testing