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 white box test design technique in which test cases are designed to execute branches.
Branch testing
best practice
Breadth Testing
Accessibility Testing
2. 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
white box testing
Invalid testing
Isolation Testing
Concurrency Testing
3. 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.
Authorization Testing
Heuristic evaluations
Decision testing
Data flow Testing
4. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
Branch
Testing best practice
QA
5. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Grey Box Testing
Testing best practice
Maintenance testing
Dependency Testing
6. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
test coverage
Dependency Testing
organisation structure
Incremental testing
7. The process of testing to determine the efficiency of a software product
High order tests
Decision coverage
enough of testing
Efficiency testing
8. Testing in which test cases are designed based on variable usage within the code.
Mutation testing
Concurrency Testing
Development testing
Data flow Testing
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.
organisation structure
Development testing
Conversion Testing / Migration Testing
Arc Testing / Branch Testing
10. 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
Loop Testing
Beta Testing / Field Testing
Data flow Testing
11. Provide critical information during project
Interoperability testing
Business process-based testing
Arc Testing / Branch Testing
providing information Objective
12. 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
QA
software testing
Quality
Component Testing
13. 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.
Interface Testing
SOA
Bottom-up Testing
Alpha Testing
14. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared and analyzed in cases of discrepancies
Decision condition testing
Back-to-back testing
Isolation Testing
Dependency Testing
15. It is a whole - is the whole process form review to plans strategy and whole thing
Component Testing
Localization Testing
QA
Documentation Testing
16. Testing concerned with the accuracy of documentation.
Concurrency Testing
black box testing
Documentation Testing
test coverage
17. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Decision coverage
Monkey Testing
Heuristic evaluations
Benchmark Testing
18. The process of testing to determine the interoperability of a software product
black box testing
Fuzz Testing
Branch testing
Interoperability testing
19. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
Ad-hoc Testing
Interface Testing
Logic coverage Testing / Logic driven Testing / Structural
20. 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
Incremental testing
Bugs
Ad-hoc Testing
Heuristic evaluations
21. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Agile Testing
Exploratory Testing
Efficiency testing
Decision coverage
22. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
GUI Testing
Endurance Testing
High order tests
Decision testing
23. Determine whether a system meets some specified standard. external organization as complying with the standard
Benchmark Testing
Conformance Testing / Compliance Testing / Standards Testing
Fuzz Testing
Compatibility Testing
24. 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
Maintainability Testing / Serviceability Testing
Keyword driven Testing
Load Testing
25. Similar to black box testing - structure of test cases in order to find defects and its strutured
functional testing
CAST
backend testing/database testing
Accessibility Testing
26. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Equivalence partition Testing
Keyword driven Testing
best practice
Interface Testing
27. 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).
Code coverage
Context Driven Testing
Quality
Design based Testing
28. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
AUT
CAST
Conversion Testing / Migration Testing
Defect density
29. 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.
Decision coverage
Breadth Testing
Keyword driven Testing
Fuzz Testing
30. The expected results or performance characteristics that define whether the test cases passed or failed
Equivalence partition Testing
Acceptance criteria
Ad-hoc Testing
Decision testing
31. 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
Mutation testing
Statement coverage
best practice
32. Depends on the schedule and risk based - business impact follow the 20-80 rules
Breadth Testing
stop testing timing
Bugs
Branch coverage
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.
stop testing timing
Testing best practice
providing information Objective
Code coverage
34. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Dependency Testing
Ad-hoc Testing
black box testing
backend testing/database testing
35. The testing of individual software components.
Depth Testing
Component Testing
quality assurance process improvement
structural testing
36. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Isolation Testing
Exploratory Testing
Maintainability Testing / Serviceability Testing
Localization Testing
37. Kind of unit testing - internal working of software
Keyword driven Testing
structural testing
Conformance Testing / Compliance Testing / Standards Testing
Localization Testing
38. 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
quality assurance process improvement
best practice
Conversion Testing / Migration Testing
Integration Testing
39. 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
Back-to-back testing
SOA
test coverage
Model Based Testing
40. 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
Fault
QA
Equivalence Class
Acceptance Testing/User Acceptance Testing
41. 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
Branch
Loop Testing
Defect
Maintenance testing
42. 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
High order tests
Logic coverage Testing / Logic driven Testing / Structural
Data-Driven Testing
Equivalence Class
43. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Incremental testing
Interoperability testing
providing information - metric
High order tests
44. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Compatibility Testing
Ad-hoc Testing
Gorilla Testing
Mutation testing
45. 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
Coverage Testing
Branch coverage
Installation Testing
Alpha Testing
46. Testing whether the system meets its specified objectives for maintainability.
End-to-end Testing
CAST
Incremental testing
Maintainability Testing / Serviceability Testing
47. 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.
Component Testing
Fuzz Testing
Installation Testing
SOA
48. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Equivalence Partitioning
Design based Testing
Mutation testing
Isolation Testing
49. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Gamma testing
Interface Testing
Isolation Testing
Decision coverage
50. This term refers to making software specifically designed for a specific locality
Localization Testing
Decision condition testing
High order tests
stop testing timing