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. The process of testing to determine the efficiency of a software product
Grey Box Testing
Efficiency testing
AUT
Localization Testing
2. Can't see - test the functional testing - no access to code and testing is done on UI
black box testing
End-to-end Testing
Decision table testing
Ad-hoc Testing
3. 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.
Data flow Testing
Branch testing
Keyword driven Testing
GUI Testing
4. Computer Aided Software Testing
Testing best practice
GUI Testing
CAST
Bottom-up Testing
5. A white box test design technique in which test cases are designed to execute branches.
Design based Testing
Branch testing
stop testing timing
Authorization Testing
6. 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
backend testing/database testing
N+ Testing
Development testing
7. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.
backend testing/database testing
Agile Testing
Development testing
End-to-end Testing
8. Black-box tests conducted once the software has been integrated
High order tests
Documentation Testing
Load Testing
Boundary value analysis/ testing
9. Kind of unit testing - internal working of software
Conversion Testing / Migration Testing
structural testing
Branch
Data flow Testing
10. Application Under Test
Arc Testing / Branch Testing
Concurrency Testing
test coverage
AUT
11. Approach to doing something that generally give good results when applied appropriately and thoughfully
providing information - metric
best practice
Statement coverage
Bugs
12. Testing using input values that should be rejected by the component or system
Invalid testing
Breadth Testing
AUT
Beta Testing / Field Testing
13. 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.
High order tests
Boundary value analysis/ testing
Invalid testing
Equivalence partition Testing
14. executing the software
End-to-end Testing
software testing
white box testing
CAST
15. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
black box testing
Business process-based testing
Basis Path Testing
structural testing
16. 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
N+ Testing
Interoperability testing
Logic coverage Testing / Logic driven Testing / Structural
17. It is a whole - is the whole process form review to plans strategy and whole thing
Gamma testing
exploratory testing
QA
Decision testing
18. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Ad-hoc Testing
white box testing
Branch testing
Fault
19. This term refers to making software specifically designed for a specific locality
test coverage
Localization Testing
High order tests
AUT
20. Test case design
Breadth Testing
Logic coverage Testing / Logic driven Testing / Structural
Basis Path Testing
Business process-based testing
21. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
CAST
Bottom-up Testing
Breadth Testing
Load Testing
22. 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.
Context Driven Testing
Bottom-up Testing
Component Testing
Compatibility Testing
23. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
best practice
Heuristic evaluations
Interoperability testing
Exploratory Testing
24. The percentage of decision outcomes that have been exercised by a test suite.
Concurrency Testing
organisation structure
Endurance Testing
Decision coverage
25. Knows about the software and test - no proper plan
Branch testing
Efficiency testing
enough of testing
exploratory testing
26. Testing whether the system is compatible with other systems with which it should communicate.
Dependency Testing
Compatibility Testing
black box testing
Logic coverage Testing / Logic driven Testing / Structural
27. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Statement coverage
Endurance Testing
Big Bang Testing
Compatibility Testing
28. Depends on the schedule and risk based - business impact follow the 20-80 rules
stop testing timing
Dependency Testing
Conversion Testing / Migration Testing
quality assurance process improvement
29. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Endurance Testing
Isolation Testing
Fuzz Testing
black box testing
30. 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
Monkey Testing
Bugs
SOA
AUT
31. Testing concerned with the accuracy of documentation.
Design based Testing
Documentation Testing
Alpha Testing
Agile Testing
32. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Alpha Testing
Business process-based testing
Defect
stop testing timing
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
Statement coverage
Acceptance criteria
Decision coverage
34. Testing whether the system meets its specified objectives for maintainability.
Maintainability Testing / Serviceability Testing
structural testing
Equivalence Class
Coverage Testing
35. A test that exercises a feature of a product in full detail.
Isolation Testing
Coverage Testing
white box testing
Depth Testing
36. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Data flow Testing
Bugs
Decision condition testing
Development testing
37. The expected results or performance characteristics that define whether the test cases passed or failed
functional testing
Agile Testing
backend testing/database testing
Acceptance criteria
38. Checks for memory leaks or other problems that may occur with prolonged execution
Incremental testing
Endurance Testing
Component Testing
Quality
39. The testing of individual software components.
Equivalence Class
Defect density
Benchmark Testing
Component Testing
40. A white box testing technique that exercises program loops
Quality
functional testing
Equivalence Class
Loop Testing
41. Testing in which test cases are designed based on variable usage within the code.
CAST
Efficiency testing
Invalid testing
Data flow Testing
42. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Fault
QA
Incremental testing
Equivalence Class
43. 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.
Statement coverage
Logic coverage Testing / Logic driven Testing / Structural
Business process-based testing
Bottom-up Testing
44. 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+.
Conformance Testing / Compliance Testing / Standards Testing
Back-to-back testing
Ad-hoc Testing
N+ Testing
45. 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
Benchmark Testing
Exhaustive Testing
Concurrency Testing
46. Testing which covers all combinations of input values and preconditions for an element of the software under test
Big Bang Testing
Exhaustive Testing
Decision condition testing
Dependency Testing
47. 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.
Integration Testing
providing information - metric
providing information Objective
Model Based Testing
48. 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
Grey Box Testing
Maintainability Testing / Serviceability Testing
Equivalence Partitioning
Back-to-back testing
49. 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
Quality
white box testing
Benchmark Testing
Decision coverage
50. A test suite that exercises the full functionality of a product but does not test features in detail
Arc Testing / Branch Testing
Ad-hoc Testing
functional testing
Breadth Testing