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 service oriented architecture (SOA) is a design model which relies on a collection of loosely coupled self contained services that communicate with each other through the internet and can be called from multiple clients in a standard fashion
Equivalence Partitioning
Interoperability testing
Maintenance testing
SOA
2. A white box test design technique in which test cases are designed to execute branches.
Equivalence partition Testing
Code coverage
Branch testing
backend testing/database testing
3. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Decision condition testing
Development testing
Grey Box Testing
Data-Driven Testing
4. Provide critical information during project
providing information Objective
Localization Testing
Integration Testing
Acceptance Testing/User Acceptance Testing
5. The process of testing to determine the interoperability of a software product
Exploratory Testing
Equivalence partition Testing
Interoperability testing
Defect density
6. 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
Installation Testing
Defect
Load Testing
Code coverage
7. Knows about the software and test - no proper plan
exploratory testing
Component Testing
Coverage Testing
test coverage
8. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Integration Testing
Gamma testing
Load Testing
providing information Objective
9. 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
structural testing
white box testing
Concurrency Testing
Loop Testing
10. Can't see - test the functional testing - no access to code and testing is done on UI
black box testing
organisation structure
Quality
Basis Path Testing
11. Test case design
Logic coverage Testing / Logic driven Testing / Structural
Documentation Testing
Boundary value analysis/ testing
stop testing timing
12. 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+.
AUT
N+ Testing
Grey Box Testing
Statement coverage
13. 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
GUI Testing
Data flow Testing
Black Box Testing / Functional Testing
quality assurance process improvement
14. The percentage of executable statements that have been exercised by a test suite.
white box testing
Context Driven Testing
Alpha Testing
Statement coverage
15. 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.
QA
Maintenance testing
Alpha Testing
Fuzz Testing
16. Testing in which test cases are designed based on variable usage within the code.
stop testing timing
backend testing/database testing
Data flow Testing
Accessibility Testing
17. 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
Bottom-up Testing
Concurrency Testing
Beta Testing / Field Testing
18. 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
Endurance Testing
Gamma testing
Heuristic evaluations
Benchmark Testing
19. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
CAST
Accessibility Testing
Ad-hoc Testing
Exploratory Testing
20. 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
Depth Testing
Conversion Testing / Migration Testing
High order tests
Beta Testing / Field Testing
21. 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
Acceptance Testing/User Acceptance Testing
Isolation Testing
Gorilla Testing
Equivalence Class
22. A white box testing technique that exercises program loops
white box testing
Loop Testing
Authorization Testing
Coverage Testing
23. 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
Accessibility Testing
Equivalence Class
Loop Testing
24. 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
enough of testing
Testing best practice
organisation structure
Bugs
25. 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).
Equivalence Class
Statement coverage
SOA
Design based Testing
26. Testing one particular module - functionality heavily
organisation structure
Gorilla Testing
Development testing
Endurance Testing
27. The testing of individual software components.
enough of testing
Code coverage
Component Testing
Statement coverage
28. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Conformance Testing / Compliance Testing / Standards Testing
Interface Testing
Testing best practice
Breadth Testing
29. 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
Boundary value analysis/ testing
Big Bang Testing
Design based Testing
test coverage
30. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Boundary value analysis/ testing
Business process-based testing
Basis Path Testing
N+ 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.
Conformance Testing / Compliance Testing / Standards Testing
Depth Testing
Bugs
Defect
32. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Big Bang Testing
Quality
Branch coverage
Basis Path Testing
33. 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
Compatibility Testing
Equivalence partition Testing
Branch
Isolation Testing
34. 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)
Defect density
Branch testing
Compatibility Testing
Gamma testing
35. 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.
Code coverage
Model Based Testing
Development testing
Heuristic evaluations
36. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Code coverage
exploratory testing
white box testing
Decision table testing
37. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
Fault
QA
Mutation testing
38. Application Under Test
Accessibility Testing
Exploratory Testing
Black Box Testing / Functional Testing
AUT
39. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Breadth Testing
Bottom-up Testing
Equivalence Partitioning
Conversion Testing / Migration Testing
40. The percentage of decision outcomes that have been exercised by a test suite.
Basis Path Testing
Decision coverage
test coverage
Data-Driven Testing
41. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
GUI Testing
Business process-based testing
organisation structure
stop testing timing
42. Checks for memory leaks or other problems that may occur with prolonged execution
providing information - metric
Endurance Testing
Fuzz Testing
Fault
43. 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
Depth Testing
Coverage Testing
white box testing
Maintenance testing
44. This term refers to making software specifically designed for a specific locality
Benchmark Testing
Gorilla Testing
Branch coverage
Localization Testing
45. Testing whether the system is compatible with other systems with which it should communicate.
Branch coverage
Acceptance Testing/User Acceptance Testing
Compatibility Testing
Code coverage
46. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Interoperability testing
functional testing
Defect
backend testing/database testing
47. 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
Arc Testing / Branch Testing
Model Based Testing
Boundary value analysis/ testing
Data-Driven Testing
48. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Grey Box Testing
Model Based Testing
Invalid testing
Accessibility Testing
49. Testing concerned with the accuracy of documentation.
Fault
Benchmark Testing
Monkey Testing
Documentation Testing
50. 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
End-to-end Testing
CAST
architecure of SOA
software testing