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. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
exploratory testing
Equivalence partition Testing
Installation Testing
black box testing

2. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)
Maintenance testing
Context Driven Testing
Defect density
Agile Testing

3. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Back-to-back testing
Acceptance criteria
Benchmark Testing
Localization Testing

4. 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.
Logic coverage Testing / Logic driven Testing / Structural
Context Driven Testing
Efficiency testing
Beta Testing / Field Testing

5. A test that exercises a feature of a product in full detail.
Depth Testing
End-to-end Testing
Localization Testing
Monkey Testing

6. 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+.
N+ Testing
Decision testing
Localization Testing
Gamma testing

7. Kind of unit testing - internal working of software
Dynamic Testing
structural testing
software testing
Keyword driven Testing

8. 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.
providing information - metric
Installation Testing
Authorization Testing
backend testing/database testing

9. 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.
Defect density
Fault
Documentation Testing
Fuzz Testing

10. 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
Exploratory Testing
Interface Testing
Interoperability testing

11. 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.
Compatibility Testing
Arc Testing / Branch Testing
Interface Testing
Basis Path Testing

12. Determine whether a system meets some specified standard. external organization as complying with the standard
black box testing
Branch coverage
Conformance Testing / Compliance Testing / Standards Testing
Exhaustive Testing

13. 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.
Gorilla Testing
End-to-end Testing
Dependency Testing
Logic coverage Testing / Logic driven Testing / Structural

14. It is a whole - is the whole process form review to plans strategy and whole thing
Equivalence Class
Decision table testing
AUT
QA

15. The percentage of decision outcomes that have been exercised by a test suite.
Design based Testing
Decision testing
Decision coverage
Endurance 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
Development testing
Authorization Testing
Concurrency Testing
Decision table testing

17. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
backend testing/database testing
Efficiency testing
stop testing timing
Grey Box Testing

18. 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.
Dependency Testing
Testing best practice
Heuristic evaluations
Model Based Testing

19. 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
Branch testing
Heuristic evaluations
Decision condition testing
providing information Objective

20. 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.
QA
Keyword driven Testing
Component Testing
Boundary value analysis/ testing

21. 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.
enough of testing
Defect
CAST
Isolation Testing

22. A test suite that exercises the full functionality of a product but does not test features in detail
AUT
Testing best practice
stop testing timing
Breadth Testing

23. Testing which covers all combinations of input values and preconditions for an element of the software under test
End-to-end Testing
Exhaustive Testing
Testing best practice
best practice

24. A white box test design technique in which test cases are designed to execute decision outcomes
Model Based Testing
Bottom-up Testing
Decision testing
Arc Testing / Branch Testing

25. 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
Maintainability Testing / Serviceability Testing
Decision testing
Equivalence partition Testing
architecure of SOA

26. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Compatibility Testing
Breadth Testing
Ad-hoc Testing
Logic coverage Testing / Logic driven Testing / Structural

27. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
functional testing
Heuristic evaluations
Loop Testing

28. 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
Quality
Data-Driven Testing
Decision condition testing
Gorilla Testing

29. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Branch coverage
CAST
structural testing
Accessibility Testing

30. 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).
Design based Testing
Fuzz Testing
Data flow Testing
Data-Driven Testing

31. 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.
Interoperability testing
quality assurance process improvement
white box testing
Boundary value analysis/ testing

32. A white box testing technique that exercises program loops
Model Based Testing
Equivalence Partitioning
Integration Testing
Loop Testing

33. 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
Incremental testing
Logic coverage Testing / Logic driven Testing / Structural
Quality
Grey Box Testing

34. Testing the changes to an operational system or the impact of a changed environment to an operational system
Concurrency Testing
Maintenance testing
best practice
Branch testing

35. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
Acceptance criteria
Grey Box Testing
Equivalence Class

36. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Model Based Testing
Bottom-up Testing
Incremental testing
Localization Testing

37. 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
Data flow Testing
Maintenance testing
Bugs
Branch

38. Knows about the software and test - no proper plan
CAST
Ad-hoc Testing
Business process-based testing
exploratory testing

39. Checks for memory leaks or other problems that may occur with prolonged execution
Incremental testing
Isolation Testing
Back-to-back testing
Endurance Testing

40. Testing software through executing it.
organisation structure
Data flow Testing
Agile Testing
Dynamic Testing

41. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Interoperability testing
Decision table testing
exploratory testing
Basis Path Testing

42. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Depth Testing
End-to-end Testing
Equivalence partition Testing
white box testing

43. 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
Endurance Testing
Acceptance Testing/User Acceptance Testing
Compatibility Testing
Agile Testing

44. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Equivalence Partitioning
Fuzz Testing
Big Bang Testing
enough of testing

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

46. Similar to black box testing - structure of test cases in order to find defects and its strutured
Coverage Testing
white box testing
Data flow Testing
functional testing

47. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Exhaustive Testing
Alpha Testing
Testing best practice
Decision testing

48. Computer Aided Software Testing
quality assurance process improvement
stop testing timing
Authorization Testing
CAST

49. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
End-to-end Testing
Interface Testing
Gorilla Testing
Maintenance testing

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
software testing
Coverage Testing
Monkey Testing
Big Bang Testing