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 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.
Maintenance testing
Testing best practice
Boundary value analysis/ testing
test coverage
2. 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.
Decision testing
providing information Objective
Context Driven Testing
Acceptance criteria
3. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Exploratory Testing
Fault
QA
Ad-hoc Testing
4. The testing of individual software components.
Dependency Testing
functional testing
Component Testing
Alpha Testing
5. 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
organisation structure
Interface Testing
Conformance Testing / Compliance Testing / Standards Testing
6. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Component Testing
End-to-end Testing
Load Testing
Alpha Testing
7. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Isolation Testing
Design based Testing
Big Bang Testing
High order tests
8. 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
Acceptance Testing/User Acceptance Testing
Breadth Testing
Development testing
Quality
9. 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
Equivalence Partitioning
software testing
Decision condition testing
10. The process of testing to determine the efficiency of a software product
backend testing/database testing
Efficiency testing
Beta Testing / Field Testing
Dependency Testing
11. 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
Equivalence Class
enough of testing
Back-to-back testing
Interface Testing
12. 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
Alpha Testing
Compatibility Testing
Acceptance criteria
Coverage Testing
13. A test that exercises a feature of a product in full detail.
Maintainability Testing / Serviceability Testing
black box testing
Depth Testing
Mutation testing
14. Can't see - test the functional testing - no access to code and testing is done on UI
Mutation testing
Exploratory Testing
Compatibility Testing
black box testing
15. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Interoperability testing
Endurance Testing
Model Based Testing
white box testing
16. Determine whether a system meets some specified standard. external organization as complying with the standard
Incremental testing
Benchmark Testing
Keyword driven Testing
Conformance Testing / Compliance Testing / Standards Testing
17. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Basis Path Testing
Ad-hoc Testing
quality assurance process improvement
Bottom-up Testing
18. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
Coverage Testing
Isolation Testing
Mutation testing
19. The percentage of decision outcomes that have been exercised by a test suite.
Branch coverage
Concurrency Testing
Decision coverage
providing information - metric
20. 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
Black Box Testing / Functional Testing
Data-Driven Testing
Development testing
High order tests
21. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Equivalence partition Testing
quality assurance process improvement
Dynamic Testing
architecure of SOA
22. A white box test design technique in which test cases are designed to execute decision outcomes
Decision testing
Accessibility Testing
Interoperability testing
Fault
23. 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
architecure of SOA
Mutation testing
Benchmark Testing
Concurrency Testing
24. This term refers to making software specifically designed for a specific locality
Accessibility Testing
Bugs
Localization Testing
Code coverage
25. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
GUI Testing
Compatibility Testing
Accessibility Testing
exploratory testing
26. 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.
enough of testing
Branch testing
End-to-end Testing
Arc Testing / Branch Testing
27. Testing whether the system meets its specified objectives for maintainability.
Maintainability Testing / Serviceability Testing
enough of testing
Interface Testing
Quality
28. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
AUT
Defect
providing information Objective
29. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Defect
Authorization Testing
Big Bang Testing
End-to-end Testing
30. 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
Statement coverage
Concurrency Testing
Localization Testing
Quality
31. Computer Aided Software Testing
Branch coverage
CAST
Endurance Testing
SOA
32. 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
Gorilla Testing
Equivalence Partitioning
Maintainability Testing / Serviceability Testing
Bugs
33. Application Under Test
Interface Testing
Conversion Testing / Migration Testing
AUT
providing information - metric
34. Kind of unit testing - internal working of software
black box testing
exploratory testing
structural testing
Benchmark Testing
35. Checks for memory leaks or other problems that may occur with prolonged execution
Endurance Testing
Efficiency testing
High order tests
Defect density
36. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Basis Path Testing
quality assurance process improvement
Equivalence partition Testing
Dependency Testing
37. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Quality
Ad-hoc Testing
Branch testing
Testing best practice
38. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Agile Testing
Incremental testing
Installation Testing
Invalid testing
39. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
providing information Objective
Integration Testing
enough of testing
Compatibility Testing
40. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
Decision condition testing
Data flow Testing
Endurance Testing
41. Testing one particular module - functionality heavily
Gorilla Testing
quality assurance process improvement
Acceptance criteria
Documentation Testing
42. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
enough of testing
structural testing
Business process-based testing
Mutation testing
43. 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.
Big Bang Testing
quality assurance process improvement
Defect density
Defect
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
Equivalence Class
Load Testing
Acceptance Testing/User Acceptance Testing
test coverage
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
Heuristic evaluations
Statement coverage
Integration Testing
Branch
46. 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
Defect
Efficiency testing
47. Testing using input values that should be rejected by the component or system
Breadth Testing
Invalid testing
Statement coverage
enough of testing
48. 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.
providing information Objective
enough of testing
N+ Testing
Bottom-up Testing
49. 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
Component Testing
test coverage
Code coverage
Data-Driven Testing
50. The percentage of executable statements that have been exercised by a test suite.
Statement coverage
Quality
Design based Testing
Concurrency Testing