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. Testing whether the system is compatible with other systems with which it should communicate.
GUI Testing
Monkey Testing
backend testing/database testing
Compatibility Testing
2. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
architecure of SOA
Acceptance Testing/User Acceptance Testing
Design based Testing
3. 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.
Decision condition testing
Conversion Testing / Migration Testing
Fault
Alpha Testing
4. 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.
Loop Testing
Keyword driven Testing
Business process-based testing
Defect
5. Testing using input values that should be rejected by the component or system
Basis Path Testing
Accessibility Testing
Invalid testing
Interoperability testing
6. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Branch coverage
Equivalence Partitioning
Compatibility Testing
Conversion Testing / Migration Testing
7. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Exploratory Testing
N+ Testing
Component Testing
Alpha Testing
8. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Bugs
GUI Testing
organisation structure
providing information Objective
9. 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
Heuristic evaluations
Decision condition testing
white box testing
10. A white box test design technique in which test cases are designed to execute branches.
Accessibility Testing
Branch testing
Branch coverage
Decision condition testing
11. 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
Bottom-up Testing
test coverage
Quality
Bugs
12. A test suite that exercises the full functionality of a product but does not test features in detail
Equivalence Partitioning
Breadth Testing
Data flow Testing
End-to-end Testing
13. 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
organisation structure
Agile Testing
Load Testing
Concurrency Testing
14. The process of testing to determine the interoperability of a software product
Black Box Testing / Functional Testing
Interoperability testing
Decision table testing
Keyword driven Testing
15. 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.
Installation Testing
GUI Testing
Boundary value analysis/ testing
stop testing timing
16. 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
Fuzz Testing
enough of testing
architecure of SOA
Equivalence Class
17. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
SOA
Branch coverage
Decision table testing
Dependency Testing
18. Depends on the schedule and risk based - business impact follow the 20-80 rules
Benchmark Testing
Isolation Testing
stop testing timing
Conversion Testing / Migration Testing
19. The process of testing to determine the efficiency of a software product
Fault
Efficiency testing
architecure of SOA
Development testing
20. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Component Testing
exploratory testing
Business process-based testing
Dependency Testing
21. The percentage of decision outcomes that have been exercised by a test suite.
Ad-hoc Testing
organisation structure
Branch testing
Decision coverage
22. 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)
Design based Testing
Defect density
Quality
Defect
23. 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.
Decision coverage
Bottom-up Testing
Conformance Testing / Compliance Testing / Standards Testing
Beta Testing / Field Testing
24. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Beta Testing / Field Testing
Maintenance testing
Dependency Testing
N+ Testing
25. 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
Maintenance testing
Accessibility Testing
Acceptance Testing/User Acceptance Testing
Interface Testing
26. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Boundary value analysis/ testing
Interface Testing
Monkey Testing
End-to-end Testing
27. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Black Box Testing / Functional Testing
Equivalence Partitioning
Load Testing
Incremental testing
28. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Exhaustive Testing
Loop Testing
enough of testing
Alpha Testing
29. Application Under Test
Boundary value analysis/ testing
enough of testing
High order tests
AUT
30. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Business process-based testing
Decision condition testing
Defect density
Authorization Testing
31. Test case design
Data flow Testing
Conversion Testing / Migration Testing
Business process-based testing
Logic coverage Testing / Logic driven Testing / Structural
32. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
High order tests
Bugs
Heuristic evaluations
Grey Box Testing
33. 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
Alpha Testing
structural testing
providing information Objective
34. The percentage of executable statements that have been exercised by a test suite.
Statement coverage
Boundary value analysis/ testing
Equivalence Class
exploratory testing
35. 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
Basis Path Testing
Branch
Installation Testing
Interface Testing
36. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Branch
N+ Testing
Incremental testing
GUI Testing
37. 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
Black Box Testing / Functional Testing
Concurrency Testing
Logic coverage Testing / Logic driven Testing / Structural
Depth Testing
38. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
functional testing
GUI Testing
Dependency Testing
Ad-hoc Testing
39. 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
N+ Testing
Integration Testing
Accessibility Testing
QA
40. Testing one particular module - functionality heavily
Gorilla Testing
Context Driven Testing
enough of testing
Maintainability Testing / Serviceability Testing
41. Testing software through executing it.
Efficiency testing
Dynamic Testing
architecure of SOA
Invalid testing
42. 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.
Model Based Testing
exploratory testing
Acceptance criteria
Gorilla Testing
43. 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.
Context Driven Testing
Arc Testing / Branch Testing
Bugs
Acceptance Testing/User Acceptance Testing
44. 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
Quality
architecure of SOA
Defect
Concurrency Testing
45. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Code coverage
Accessibility Testing
Gorilla Testing
functional testing
46. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Equivalence partition Testing
Agile Testing
Decision table testing
Monkey Testing
47. 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+.
providing information - metric
Statement coverage
Load Testing
N+ Testing
48. Black-box tests conducted once the software has been integrated
Documentation Testing
SOA
High order tests
Interoperability testing
49. Approach to doing something that generally give good results when applied appropriately and thoughfully
Design based Testing
Decision coverage
Development testing
best practice
50. Provide critical information during project
providing information Objective
Equivalence partition Testing
Big Bang Testing
Exploratory Testing