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. Testing whether the system meets its specified objectives for maintainability.
Exploratory Testing
Efficiency testing
Maintainability Testing / Serviceability Testing
backend testing/database testing
2. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Isolation Testing
architecure of SOA
white box testing
providing information Objective
3. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Grey Box Testing
providing information Objective
Big Bang Testing
GUI Testing
4. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Concurrency Testing
Interface Testing
Data-Driven Testing
Loop Testing
5. The testing of individual software components.
Branch
Acceptance criteria
Load Testing
Component Testing
6. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Authorization Testing
Keyword driven Testing
Installation Testing
Branch coverage
7. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Model Based Testing
Equivalence Partitioning
N+ Testing
Equivalence Class
8. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
Monkey Testing
providing information - metric
Alpha Testing
9. 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.
Model Based Testing
Gamma testing
Defect density
Mutation testing
10. 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.
Documentation Testing
Arc Testing / Branch Testing
Fault
best practice
11. 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+.
N+ Testing
Installation Testing
High order tests
Data-Driven Testing
12. 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.
High order tests
Authorization Testing
Loop Testing
Component Testing
13. The percentage of executable statements that have been exercised by a test suite.
architecure of SOA
Exploratory Testing
Statement coverage
Mutation testing
14. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Documentation Testing
Benchmark Testing
Big Bang Testing
Efficiency testing
15. Root cause analyst - base of the problem - customer satisfaction report
Benchmark Testing
Ad-hoc Testing
Branch testing
quality assurance process improvement
16. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Concurrency Testing
Context Driven Testing
enough of testing
Keyword driven Testing
17. Testing using input values that should be rejected by the component or system
Benchmark Testing
Business process-based testing
Invalid testing
test coverage
18. 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
Interface Testing
stop testing timing
Acceptance Testing/User Acceptance Testing
providing information - metric
19. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
Decision condition testing
Installation Testing
Big Bang Testing
20. 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
architecure of SOA
Coverage Testing
providing information - metric
Testing best practice
21. Testing whether the system is compatible with other systems with which it should communicate.
Bottom-up Testing
Grey Box Testing
Compatibility Testing
SOA
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.
Fuzz Testing
Boundary value analysis/ testing
Branch testing
white box testing
23. The percentage of decision outcomes that have been exercised by a test suite.
Context Driven Testing
Decision table testing
Bugs
Decision coverage
24. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Dependency Testing
High order tests
Conversion Testing / Migration Testing
Equivalence Class
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).
Design based Testing
Conversion Testing / Migration Testing
Heuristic evaluations
providing information Objective
26. The process of testing to determine the interoperability of a software product
N+ Testing
Ad-hoc Testing
Gamma testing
Interoperability testing
27. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
functional testing
Ad-hoc Testing
Defect
Accessibility Testing
28. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Black Box Testing / Functional Testing
Incremental testing
Integration Testing
Heuristic evaluations
29. Application Under Test
Concurrency Testing
AUT
enough of testing
CAST
30. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Data flow Testing
providing information - metric
Agile Testing
organisation structure
31. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Efficiency testing
Load Testing
Maintainability Testing / Serviceability Testing
Installation Testing
32. 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
Integration Testing
Model Based Testing
SOA
Gamma testing
33. Approach to doing something that generally give good results when applied appropriately and thoughfully
best practice
Conversion Testing / Migration Testing
AUT
black box testing
34. The process of testing to determine the efficiency of a software product
Back-to-back testing
Endurance Testing
Efficiency testing
Benchmark Testing
35. 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
Depth Testing
Accessibility Testing
Endurance Testing
SOA
36. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Business process-based testing
Installation Testing
Branch
exploratory testing
37. Testing software through executing it.
Mutation testing
Dynamic Testing
Agile Testing
Monkey Testing
38. Provide critical information during project
Branch coverage
stop testing timing
providing information Objective
Alpha Testing
39. Determine whether a system meets some specified standard. external organization as complying with the standard
Arc Testing / Branch Testing
Conformance Testing / Compliance Testing / Standards Testing
CAST
providing information Objective
40. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Beta Testing / Field Testing
Exhaustive Testing
Exploratory Testing
Dependency Testing
41. Test case design
Branch
Conformance Testing / Compliance Testing / Standards Testing
Loop Testing
Logic coverage Testing / Logic driven Testing / Structural
42. Knows about the software and test - no proper plan
Conformance Testing / Compliance Testing / Standards Testing
exploratory testing
Development testing
Gamma testing
43. A white box testing technique that exercises program loops
Bugs
Interface Testing
Loop Testing
Breadth Testing
44. This term refers to making software specifically designed for a specific locality
Load Testing
Quality
Localization Testing
test coverage
45. 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.
providing information Objective
Efficiency testing
Boundary value analysis/ testing
Quality
46. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Loop Testing
Agile Testing
Equivalence Class
architecure of SOA
47. Testing concerned with the accuracy of documentation.
Branch coverage
Back-to-back testing
Documentation Testing
software testing
48. Black-box tests conducted once the software has been integrated
Coverage Testing
architecure of SOA
Equivalence Partitioning
High order tests
49. 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.
Keyword driven Testing
Dependency Testing
End-to-end Testing
architecure of SOA
50. Can't see - test the functional testing - no access to code and testing is done on UI
Load Testing
black box testing
Benchmark Testing
Monkey Testing