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. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Integration Testing
Exploratory Testing
best practice
Branch coverage
2. A white box test design technique in which test cases are designed to execute branches.
Branch testing
Basis Path Testing
providing information Objective
Alpha Testing
3. 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
Statement coverage
Fault
Bugs
Maintainability Testing / Serviceability Testing
4. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Exploratory Testing
Maintenance testing
Agile Testing
providing information Objective
5. 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
Heuristic evaluations
Statement coverage
Efficiency testing
white box testing
6. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Equivalence Partitioning
Testing best practice
Interface Testing
Benchmark Testing
7. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
CAST
Equivalence partition Testing
white box testing
Heuristic evaluations
8. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
backend testing/database testing
Dynamic Testing
Basis Path Testing
Equivalence Partitioning
9. 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
Installation Testing
Data-Driven Testing
Keyword driven Testing
10. A test that exercises a feature of a product in full detail.
High order tests
Depth Testing
exploratory testing
quality assurance process improvement
11. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Decision condition testing
software testing
Development testing
Compatibility Testing
12. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
Gorilla Testing
Boundary value analysis/ testing
Beta Testing / Field Testing
13. Can't see - test the functional testing - no access to code and testing is done on UI
Defect density
black box testing
Equivalence Class
Concurrency Testing
14. 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
Decision condition testing
Installation Testing
Alpha Testing
software testing
15. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
SOA
Acceptance criteria
Alpha Testing
GUI Testing
16. Testing in which test cases are designed based on variable usage within the code.
Fuzz Testing
Invalid testing
Data flow Testing
Load Testing
17. 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
Big Bang Testing
Model Based Testing
Interoperability testing
18. It is a whole - is the whole process form review to plans strategy and whole thing
Gorilla Testing
SOA
structural testing
QA
19. The process of testing to determine the efficiency of a software product
N+ Testing
Efficiency testing
Documentation Testing
Grey Box Testing
20. 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.
Gamma testing
Loop Testing
Model Based Testing
Data-Driven Testing
21. 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.
Accessibility Testing
functional testing
Mutation testing
Context Driven Testing
22. 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
Back-to-back testing
Dependency Testing
Interoperability testing
providing information Objective
23. 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
Agile Testing
Exhaustive Testing
architecure of SOA
Integration Testing
24. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
software testing
GUI Testing
exploratory testing
Endurance Testing
25. Testing which covers all combinations of input values and preconditions for an element of the software under test
Exhaustive Testing
Design based Testing
Isolation Testing
Endurance Testing
26. 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+.
exploratory testing
Incremental testing
N+ Testing
GUI Testing
27. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
backend testing/database testing
CAST
Branch testing
Big Bang Testing
28. The testing of individual software components.
Dependency Testing
Coverage Testing
quality assurance process improvement
Component Testing
29. 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
Model Based Testing
Gamma testing
Beta Testing / Field Testing
Localization Testing
30. Root cause analyst - base of the problem - customer satisfaction report
Grey Box Testing
SOA
Defect
quality assurance process improvement
31. Computer Aided Software Testing
Conformance Testing / Compliance Testing / Standards Testing
CAST
Isolation Testing
Code coverage
32. The percentage of decision outcomes that have been exercised by a test suite.
Acceptance criteria
Decision coverage
Alpha Testing
architecure of SOA
33. 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
Data-Driven Testing
Data flow Testing
structural testing
functional testing
34. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Big Bang Testing
Basis Path Testing
Compatibility Testing
Decision condition testing
35. 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.
Dynamic Testing
Fault
Context Driven Testing
QA
36. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
backend testing/database testing
Fuzz Testing
software testing
37. Checks for memory leaks or other problems that may occur with prolonged execution
Localization Testing
Interface Testing
Endurance Testing
Loop Testing
38. Depends on the schedule and risk based - business impact follow the 20-80 rules
Basis Path Testing
enough of testing
Mutation testing
stop testing timing
39. 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
Development testing
Authorization Testing
architecure of SOA
Defect density
40. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Interface Testing
Branch
Grey Box Testing
Gamma testing
41. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Quality
Depth Testing
Grey Box Testing
Concurrency Testing
42. 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
Monkey Testing
Acceptance Testing/User Acceptance Testing
Fault
white box testing
43. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Equivalence Partitioning
providing information - metric
Fault
Dependency Testing
44. 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
Logic coverage Testing / Logic driven Testing / Structural
GUI Testing
Dynamic Testing
Mutation testing
45. 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
Efficiency testing
Logic coverage Testing / Logic driven Testing / Structural
Arc Testing / Branch Testing
Equivalence Class
46. 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).
Decision testing
architecure of SOA
backend testing/database testing
Design based Testing
47. executing the software
software testing
white box testing
Gorilla Testing
stop testing timing
48. Application Under Test
Accessibility Testing
AUT
Fault
Arc Testing / Branch Testing
49. Testing the changes to an operational system or the impact of a changed environment to an operational system
Invalid testing
End-to-end Testing
Maintenance testing
Compatibility Testing
50. Provide critical information during project
Model Based Testing
providing information Objective
Data-Driven Testing
Integration Testing