SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
Software Testing And Qa
Start Test
Study First
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 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
backend testing/database testing
Mutation testing
AUT
Fault
2. 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
Keyword driven Testing
Decision table testing
Endurance Testing
QA
3. 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
Loop Testing
AUT
Back-to-back testing
4. Testing software through executing it.
Back-to-back testing
Isolation Testing
architecure of SOA
Dynamic Testing
5. The process of testing to determine the interoperability of a software product
quality assurance process improvement
Interoperability testing
Dynamic Testing
Equivalence Partitioning
6. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
Accessibility Testing
Component Testing
Development testing
7. A white box test design technique in which test cases are designed to execute decision outcomes
Acceptance Testing/User Acceptance Testing
Decision testing
backend testing/database testing
High order tests
8. 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.
Agile Testing
providing information Objective
Decision coverage
Bottom-up Testing
9. Provide critical information during project
Integration Testing
CAST
Model Based Testing
providing information Objective
10. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Data-Driven Testing
Gamma testing
Conversion Testing / Migration Testing
Big Bang Testing
11. 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
Basis Path Testing
Bottom-up Testing
exploratory testing
Quality
12. Kind of unit testing - internal working of software
Basis Path Testing
Gamma testing
structural testing
best practice
13. 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
Data-Driven Testing
High order tests
Code coverage
Interface Testing
14. This term refers to making software specifically designed for a specific locality
QA
Model Based Testing
stop testing timing
Localization Testing
15. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Branch
test coverage
Equivalence Partitioning
QA
16. Similar to black box testing - structure of test cases in order to find defects and its strutured
Exploratory Testing
black box testing
functional testing
Decision table testing
17. A white box test design technique in which test cases are designed to execute branches.
Integration Testing
enough of testing
Branch testing
quality assurance process improvement
18. 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
test coverage
providing information - metric
Context Driven Testing
19. 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).
Business process-based testing
Design based Testing
best practice
Ad-hoc Testing
20. Stakeholder stakeholder satisfaction with test results report
backend testing/database testing
providing information - metric
Documentation Testing
Endurance Testing
21. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Statement coverage
Isolation Testing
Logic coverage Testing / Logic driven Testing / Structural
Keyword driven Testing
22. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Maintainability Testing / Serviceability Testing
Dynamic Testing
Interoperability testing
Gamma testing
23. 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.
Conformance Testing / Compliance Testing / Standards Testing
Conversion Testing / Migration Testing
Context Driven Testing
Fuzz Testing
24. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Heuristic evaluations
Integration Testing
Big Bang Testing
Interoperability testing
25. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Branch
Development testing
Data-Driven Testing
Dynamic Testing
26. 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
Monkey Testing
white box testing
Efficiency testing
Model Based Testing
27. 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
Arc Testing / Branch Testing
Development testing
Data-Driven Testing
Beta Testing / Field Testing
28. 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
black box testing
Defect
Integration Testing
29. Testing using input values that should be rejected by the component or system
Invalid testing
Alpha Testing
providing information - metric
Statement coverage
30. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Mutation testing
Equivalence partition Testing
Loop Testing
Branch coverage
31. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Defect
Localization Testing
Decision testing
organisation structure
32. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Branch coverage
End-to-end Testing
quality assurance process improvement
Exploratory Testing
33. 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.
Beta Testing / Field Testing
Context Driven Testing
Code coverage
CAST
34. 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.
Defect
test coverage
Ad-hoc Testing
Grey Box Testing
35. Black-box tests conducted once the software has been integrated
N+ Testing
Conversion Testing / Migration Testing
structural testing
High order tests
36. 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
Efficiency testing
Ad-hoc Testing
Accessibility Testing
37. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
End-to-end Testing
Code coverage
Interface Testing
Gorilla Testing
38. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Bugs
Exploratory Testing
Acceptance Testing/User Acceptance Testing
Load Testing
39. 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)
black box testing
organisation structure
Keyword driven Testing
Defect density
40. 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
Endurance Testing
Black Box Testing / Functional Testing
End-to-end Testing
Depth Testing
41. A white box testing technique that exercises program loops
Model Based Testing
QA
Loop Testing
black box testing
42. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Decision table testing
Data flow Testing
Grey Box Testing
functional testing
43. Application Under Test
Ad-hoc Testing
AUT
structural testing
Efficiency testing
44. executing the software
Dynamic Testing
software testing
Defect density
Maintenance testing
45. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
QA
Agile Testing
Localization Testing
Alpha Testing
46. Testing one particular module - functionality heavily
Localization Testing
Basis Path Testing
Gorilla Testing
N+ Testing
47. 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.
Exhaustive Testing
Boundary value analysis/ testing
Documentation Testing
Gorilla Testing
48. 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
Black Box Testing / Functional Testing
Coverage Testing
Breadth Testing
GUI Testing
49. 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
Equivalence Class
Development testing
Installation Testing
Business process-based testing
50. 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.
Data flow Testing
Context Driven Testing
Fuzz Testing
test coverage