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. executing the software
software testing
Basis Path Testing
white box testing
Authorization Testing
2. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
GUI Testing
Gamma testing
Branch coverage
Conversion Testing / Migration Testing
3. 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
Decision condition testing
Development testing
High order tests
4. 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.
Code coverage
Design based Testing
Dependency Testing
Isolation Testing
5. Knows about the software and test - no proper plan
Statement coverage
exploratory testing
quality assurance process improvement
Decision table testing
6. 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
Data flow Testing
Localization Testing
Exhaustive Testing
Black Box Testing / Functional Testing
7. Defined as any testing that occurs outside of the development environment. installed on. simply appear to be to run a setup program - can be used with confidence
enough of testing
Conversion Testing / Migration Testing
Installation Testing
SOA
8. Root cause analyst - base of the problem - customer satisfaction report
Installation Testing
quality assurance process improvement
Conformance Testing / Compliance Testing / Standards Testing
Bottom-up Testing
9. Determine whether a system meets some specified standard. external organization as complying with the standard
Conformance Testing / Compliance Testing / Standards Testing
Beta Testing / Field Testing
Component Testing
Localization Testing
10. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Authorization Testing
Dynamic Testing
Agile Testing
Logic coverage Testing / Logic driven Testing / Structural
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.
Boundary value analysis/ testing
Acceptance criteria
SOA
Dependency Testing
12. 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.
Fuzz Testing
Branch testing
Development testing
Bugs
13. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
N+ Testing
Gamma testing
Decision coverage
Development testing
14. The percentage of executable statements that have been exercised by a test suite.
End-to-end Testing
Decision coverage
functional testing
Statement coverage
15. 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.
functional testing
Business process-based testing
Keyword driven Testing
architecure of SOA
16. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
Authorization Testing
CAST
Basis Path Testing
17. A white box test case design techniques that uses the algorithmic flow of the program to design tests
software testing
Acceptance criteria
Basis Path Testing
Interoperability testing
18. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Grey Box Testing
Development testing
Interface Testing
Context Driven Testing
19. 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.
Data-Driven Testing
Acceptance criteria
architecure of SOA
Authorization Testing
20. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
providing information Objective
Maintenance testing
Exploratory Testing
enough of testing
21. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Depth Testing
Gamma testing
Accessibility Testing
Decision testing
22. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Exploratory Testing
providing information - metric
Equivalence Partitioning
Basis Path Testing
23. A white box test design technique in which test cases are designed to execute branches.
Localization Testing
Exploratory Testing
Branch testing
Defect
24. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Statement coverage
backend testing/database testing
Keyword driven Testing
Isolation Testing
25. 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.
AUT
High order tests
Conversion Testing / Migration Testing
Model Based Testing
26. 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
Exploratory Testing
Branch
Alpha Testing
Invalid testing
27. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Incremental testing
Depth Testing
Beta Testing / Field Testing
Documentation Testing
28. 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
architecure of SOA
Development testing
Basis Path Testing
29. 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.
GUI Testing
quality assurance process improvement
enough of testing
Context Driven Testing
30. It is a whole - is the whole process form review to plans strategy and whole thing
Maintenance testing
Integration Testing
Gorilla Testing
QA
31. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Conversion Testing / Migration Testing
Ad-hoc Testing
Equivalence partition Testing
Monkey Testing
32. 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
Loop Testing
Beta Testing / Field Testing
Component Testing
software testing
33. 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
Compatibility Testing
Ad-hoc Testing
Bugs
Branch coverage
34. 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
Compatibility Testing
AUT
Breadth Testing
Quality
35. 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
Breadth Testing
Authorization Testing
Component Testing
Coverage Testing
36. Test case design
Coverage Testing
Logic coverage Testing / Logic driven Testing / Structural
Accessibility Testing
Gamma 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
Isolation Testing
Concurrency Testing
Defect
Incremental testing
38. Testing whether the system meets its specified objectives for maintainability.
test coverage
Data-Driven Testing
Localization Testing
Maintainability Testing / Serviceability Testing
39. The process of testing to determine the interoperability of a software product
backend testing/database testing
Interoperability testing
CAST
Equivalence Class
40. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Concurrency Testing
organisation structure
Load Testing
best practice
41. The percentage of decision outcomes that have been exercised by a test suite.
exploratory testing
Decision coverage
Back-to-back testing
Invalid testing
42. Testing concerned with the accuracy of documentation.
Bugs
Equivalence Class
Installation Testing
Documentation Testing
43. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Branch coverage
Installation Testing
Accessibility Testing
Business process-based testing
44. 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
Branch
Decision coverage
Equivalence Class
Mutation testing
45. 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
Context Driven Testing
Invalid testing
backend testing/database testing
Integration Testing
46. 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.
Equivalence Class
Endurance Testing
Arc Testing / Branch Testing
Defect density
47. Approach to doing something that generally give good results when applied appropriately and thoughfully
best practice
Interoperability testing
N+ Testing
functional testing
48. Testing whether the system is compatible with other systems with which it should communicate.
Loop Testing
structural testing
Compatibility Testing
organisation structure
49. 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
Basis Path Testing
Monkey Testing
structural testing
Branch
50. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Concurrency Testing
Code coverage
Alpha Testing
Heuristic evaluations