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.
Big Bang Testing
Exploratory Testing
Breadth Testing
Compatibility Testing
2. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Documentation Testing
Development testing
Data-Driven Testing
Fuzz Testing
3. Testing which covers all combinations of input values and preconditions for an element of the software under test
SOA
Exhaustive Testing
Maintainability Testing / Serviceability Testing
Testing best practice
4. 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
Maintainability Testing / Serviceability Testing
Endurance Testing
Quality
5. 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
Integration Testing
Testing best practice
Back-to-back testing
test coverage
6. 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
Decision condition testing
Endurance Testing
Model Based Testing
7. The process of testing to determine the interoperability of a software product
Interoperability testing
Defect density
QA
Equivalence Partitioning
8. 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)
providing information Objective
Branch coverage
Defect density
structural testing
9. Checks for memory leaks or other problems that may occur with prolonged execution
GUI Testing
Development testing
Branch coverage
Endurance Testing
10. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
Interface Testing
Localization Testing
Branch coverage
11. A black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table
Heuristic evaluations
Exhaustive Testing
Decision table testing
Big Bang Testing
12. The percentage of executable statements that have been exercised by a test suite.
quality assurance process improvement
Basis Path Testing
Context Driven Testing
Statement coverage
13. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Concurrency Testing
GUI Testing
SOA
Gamma testing
14. 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
functional testing
Black Box Testing / Functional Testing
Monkey Testing
Data-Driven Testing
15. 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
Documentation Testing
Back-to-back testing
Fuzz Testing
Model Based Testing
16. A white box test design technique in which test cases are designed to execute decision outcomes
Decision testing
Documentation Testing
Load Testing
SOA
17. The testing of individual software components.
Component Testing
Decision coverage
Exploratory Testing
Isolation Testing
18. A white box test case design techniques that uses the algorithmic flow of the program to design tests
CAST
Basis Path Testing
test coverage
Fuzz Testing
19. 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
Development testing
High order tests
GUI Testing
20. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Maintainability Testing / Serviceability Testing
Dependency Testing
Gorilla Testing
Big Bang Testing
21. Testing whether the system is compatible with other systems with which it should communicate.
Alpha Testing
best practice
Compatibility Testing
Branch
22. Knows about the software and test - no proper plan
Big Bang Testing
Arc Testing / Branch Testing
Conformance Testing / Compliance Testing / Standards Testing
exploratory testing
23. A test suite that exercises the full functionality of a product but does not test features in detail
Agile Testing
Endurance Testing
Breadth Testing
Boundary value analysis/ testing
24. It is a whole - is the whole process form review to plans strategy and whole thing
Branch testing
software testing
QA
structural testing
25. 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.
providing information - metric
Invalid testing
Authorization Testing
Gorilla Testing
26. Testing concerned with the accuracy of documentation.
Invalid testing
Documentation Testing
providing information - metric
Decision condition testing
27. 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
Acceptance Testing/User Acceptance Testing
Fault
Fuzz Testing
Bugs
28. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Defect
enough of testing
Invalid testing
black box testing
29. 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.
Model Based Testing
Boundary value analysis/ testing
Endurance Testing
Isolation Testing
30. Testing software through executing it.
Agile Testing
Code coverage
Dynamic Testing
Breadth Testing
31. Testing using input values that should be rejected by the component or system
Load Testing
Invalid testing
N+ Testing
Branch coverage
32. 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
Concurrency Testing
Defect density
Business process-based testing
QA
33. 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.
Statement coverage
Code coverage
organisation structure
Depth Testing
34. The expected results or performance characteristics that define whether the test cases passed or failed
Maintenance testing
Installation Testing
Dependency Testing
Acceptance criteria
35. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Isolation Testing
black box testing
test coverage
Design based Testing
36. 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
Exhaustive Testing
Branch testing
Breadth Testing
Quality
37. Approach to doing something that generally give good results when applied appropriately and thoughfully
white box testing
best practice
SOA
Interoperability testing
38. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Branch
Breadth Testing
white box testing
Gamma testing
39. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Development testing
Bugs
Decision testing
Incremental testing
40. Provide critical information during project
Dependency Testing
providing information Objective
Branch testing
software testing
41. 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.
Arc Testing / Branch Testing
quality assurance process improvement
Back-to-back testing
Model Based Testing
42. 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
backend testing/database testing
Beta Testing / Field Testing
SOA
providing information Objective
43. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
backend testing/database testing
architecure of SOA
End-to-end Testing
Equivalence Class
44. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Code coverage
Testing best practice
Load Testing
Beta Testing / Field Testing
45. 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.
Dynamic Testing
stop testing timing
Fuzz Testing
Logic coverage Testing / Logic driven Testing / Structural
46. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Endurance Testing
providing information - metric
Exploratory Testing
Equivalence Partitioning
47. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
white box testing
Benchmark Testing
stop testing timing
functional testing
48. 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.
Equivalence Class
Keyword driven Testing
Arc Testing / Branch Testing
Interoperability testing
49. 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 testing
Exhaustive Testing
Bottom-up Testing
SOA
50. 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
Defect
Heuristic evaluations
Branch
Ad-hoc Testing