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. 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
AUT
Installation Testing
Equivalence Partitioning
2. Similar to black box testing - structure of test cases in order to find defects and its strutured
functional testing
Conversion Testing / Migration Testing
Isolation Testing
Logic coverage Testing / Logic driven Testing / Structural
3. A test suite that exercises the full functionality of a product but does not test features in detail
Breadth Testing
Fuzz Testing
Alpha Testing
Maintenance testing
4. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Alpha Testing
Beta Testing / Field Testing
white box testing
Component Testing
5. 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
best practice
Concurrency Testing
Integration Testing
Bugs
6. Determine whether a system meets some specified standard. external organization as complying with the standard
Heuristic evaluations
Acceptance criteria
Data-Driven Testing
Conformance Testing / Compliance Testing / Standards 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
Ad-hoc Testing
Code coverage
Conversion Testing / Migration Testing
Installation Testing
8. 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
Monkey Testing
Localization Testing
test coverage
backend testing/database testing
9. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Fuzz Testing
Defect
Branch coverage
functional testing
10. 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
Exploratory Testing
Back-to-back testing
N+ Testing
11. 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.
Big Bang Testing
Heuristic evaluations
Business process-based testing
Context Driven Testing
12. 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
Endurance Testing
software testing
best practice
13. 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)
Alpha Testing
Compatibility Testing
Incremental testing
Defect density
14. 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
Beta Testing / Field Testing
Depth Testing
Heuristic evaluations
Coverage Testing
15. The percentage of executable statements that have been exercised by a test suite.
best practice
Model Based Testing
End-to-end Testing
Statement coverage
16. 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+.
Localization Testing
Logic coverage Testing / Logic driven Testing / Structural
Gorilla Testing
N+ Testing
17. executing the software
Alpha Testing
Data flow Testing
software testing
End-to-end Testing
18. 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
Grey Box Testing
Model Based Testing
19. Computer Aided Software Testing
Decision testing
Localization Testing
Grey Box Testing
CAST
20. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Incremental testing
Exploratory Testing
Fuzz Testing
Isolation Testing
21. 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
Branch testing
Dynamic Testing
Defect
22. 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.
Bottom-up Testing
Fuzz Testing
Basis Path Testing
Design based Testing
23. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Gamma testing
black box testing
Alpha Testing
functional testing
24. Testing software through executing it.
Dynamic Testing
Loop Testing
software testing
Decision coverage
25. 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.
Alpha Testing
Arc Testing / Branch Testing
Depth Testing
AUT
26. A white box test case design techniques that uses the algorithmic flow of the program to design tests
enough of testing
QA
Basis Path Testing
Black Box Testing / Functional Testing
27. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
Statement coverage
GUI Testing
Business process-based testing
28. The percentage of decision outcomes that have been exercised by a test suite.
Decision coverage
Bugs
Efficiency testing
Code coverage
29. 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
Acceptance Testing/User Acceptance Testing
Data-Driven Testing
Fuzz Testing
Basis Path Testing
30. Testing using input values that should be rejected by the component or system
Efficiency testing
Ad-hoc Testing
Equivalence partition Testing
Invalid testing
31. 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.
Statement coverage
enough of testing
SOA
Boundary value analysis/ testing
32. A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations
Equivalence Partitioning
Mutation testing
AUT
Development 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
Bugs
structural testing
Black Box Testing / Functional Testing
End-to-end Testing
34. The process of testing to determine the efficiency of a software product
Business process-based testing
Efficiency testing
Defect
Bottom-up Testing
35. A white box test design technique in which test cases are designed to execute branches.
Big Bang Testing
Model Based Testing
Branch testing
Fuzz Testing
36. Testing whether the system meets its specified objectives for maintainability.
Interoperability testing
Testing best practice
Beta Testing / Field Testing
Maintainability Testing / Serviceability Testing
37. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
SOA
Conversion Testing / Migration Testing
quality assurance process improvement
Black Box Testing / Functional Testing
38. 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).
Basis Path Testing
Acceptance criteria
Arc Testing / Branch Testing
Design based Testing
39. 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
Load Testing
Efficiency testing
Equivalence Class
Black Box Testing / Functional Testing
40. 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
Mutation testing
architecure of SOA
Invalid testing
Code coverage
41. 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
providing information Objective
Load Testing
Data-Driven Testing
Coverage Testing
42. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
structural testing
Big Bang Testing
test coverage
Load Testing
43. Testing one particular module - functionality heavily
Gorilla Testing
Compatibility Testing
software testing
Authorization Testing
44. The testing of individual software components.
Component Testing
Bugs
QA
Big Bang Testing
45. The process of testing to determine the interoperability of a software product
Gorilla Testing
Load Testing
Interoperability testing
Monkey Testing
46. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Arc Testing / Branch Testing
Business process-based testing
Compatibility Testing
Isolation Testing
47. Knows about the software and test - no proper plan
exploratory testing
Quality
Agile Testing
architecure of SOA
48. The expected results or performance characteristics that define whether the test cases passed or failed
Installation Testing
Acceptance criteria
Equivalence Partitioning
Documentation Testing
49. Depends on the schedule and risk based - business impact follow the 20-80 rules
Isolation Testing
stop testing timing
Dependency Testing
Maintainability Testing / Serviceability Testing
50. 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 table testing
Loop Testing
Bottom-up Testing
Accessibility Testing