SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
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
Efficiency testing
Gorilla Testing
High order tests
Component Testing
2. Approach to doing something that generally give good results when applied appropriately and thoughfully
best practice
Ad-hoc Testing
Fault
test coverage
3. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Equivalence Class
Load Testing
Dependency Testing
structural testing
4. 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
Maintainability Testing / Serviceability Testing
Authorization Testing
Integration Testing
5. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Gorilla Testing
backend testing/database testing
Data flow Testing
Accessibility Testing
6. Kind of unit testing - internal working of software
Arc Testing / Branch Testing
structural testing
Back-to-back testing
Context Driven Testing
7. The expected results or performance characteristics that define whether the test cases passed or failed
software testing
Quality
Decision condition testing
Acceptance criteria
8. 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
Alpha Testing
Decision testing
Decision table testing
Branch
9. Testing whether the system is compatible with other systems with which it should communicate.
Gorilla Testing
Context Driven Testing
Conversion Testing / Migration Testing
Compatibility Testing
10. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Design based Testing
Acceptance criteria
Fuzz Testing
Branch coverage
11. 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.
structural testing
Fuzz Testing
Back-to-back testing
Breadth Testing
12. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Interface Testing
Big Bang Testing
Efficiency testing
Monkey Testing
13. The testing of individual software components.
GUI Testing
Component Testing
Quality
architecure of SOA
14. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
test coverage
enough of testing
Component Testing
Development testing
15. 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
organisation structure
CAST
stop testing timing
Decision table testing
16. 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
Dynamic Testing
Logic coverage Testing / Logic driven Testing / Structural
Efficiency testing
Data-Driven Testing
17. Knows about the software and test - no proper plan
exploratory testing
Testing best practice
test coverage
Incremental testing
18. 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
Gorilla Testing
Incremental testing
Basis Path Testing
Black Box Testing / Functional Testing
19. Black-box tests conducted once the software has been integrated
Incremental testing
High order tests
test coverage
Branch
20. An anomaly or flaw in a delivered work product. found during early lifecycle phases A defect can be any kind of issue you want tracked and resolved.
Defect
Big Bang Testing
Fault
enough of testing
21. 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
enough of testing
providing information - metric
Localization Testing
22. Similar to black box testing - structure of test cases in order to find defects and its strutured
functional testing
backend testing/database testing
Design based Testing
Defect density
23. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
End-to-end Testing
Equivalence Class
GUI Testing
Gorilla Testing
24. A white box test design technique in which test cases are designed to execute branches.
Conversion Testing / Migration Testing
End-to-end Testing
Branch testing
Monkey Testing
25. This term refers to making software specifically designed for a specific locality
Data flow Testing
Branch coverage
Acceptance criteria
Localization Testing
26. 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.
Monkey Testing
Model Based Testing
Conformance Testing / Compliance Testing / Standards Testing
Big Bang Testing
27. Testing the changes to an operational system or the impact of a changed environment to an operational system
Back-to-back testing
Endurance Testing
Concurrency Testing
Maintenance testing
28. 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
Installation Testing
Bugs
Model Based Testing
29. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
providing information Objective
Compatibility Testing
Conversion Testing / Migration Testing
Agile Testing
30. Computer Aided Software Testing
CAST
Interoperability testing
Data flow Testing
Localization Testing
31. 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
Conformance Testing / Compliance Testing / Standards Testing
best practice
Concurrency Testing
Boundary value analysis/ testing
32. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Load Testing
Maintainability Testing / Serviceability Testing
CAST
Branch coverage
33. Determine whether a system meets some specified standard. external organization as complying with the standard
AUT
Boundary value analysis/ testing
End-to-end Testing
Conformance Testing / Compliance Testing / Standards Testing
34. Test case design
Breadth Testing
Equivalence Class
Logic coverage Testing / Logic driven Testing / Structural
Black Box Testing / Functional Testing
35. 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.
Boundary value analysis/ testing
Documentation Testing
Authorization Testing
Localization Testing
36. executing the software
Keyword driven Testing
Fault
best practice
software testing
37. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Data flow Testing
Big Bang Testing
Loop Testing
enough of testing
38. Root cause analyst - base of the problem - customer satisfaction report
Arc Testing / Branch Testing
Compatibility Testing
Keyword driven Testing
quality assurance process improvement
39. Testing whether the system meets its specified objectives for maintainability.
Maintainability Testing / Serviceability Testing
Coverage Testing
Bottom-up Testing
Black Box Testing / Functional Testing
40. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Interoperability testing
organisation structure
Defect density
Design based Testing
41. 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 condition testing
Isolation Testing
providing information Objective
Bottom-up Testing
42. 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.
Quality
Back-to-back testing
Code coverage
SOA
43. 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
functional testing
Bottom-up Testing
Defect density
44. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Decision table testing
Depth Testing
N+ Testing
Grey Box Testing
45. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Efficiency testing
Testing best practice
Ad-hoc Testing
Load Testing
46. Testing which covers all combinations of input values and preconditions for an element of the software under test
Conversion Testing / Migration Testing
Conformance Testing / Compliance Testing / Standards Testing
High order tests
Exhaustive Testing
47. A test that exercises a feature of a product in full detail.
white box testing
Benchmark Testing
Depth Testing
Defect
48. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Black Box Testing / Functional Testing
Alpha Testing
backend testing/database testing
Monkey Testing
49. 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
Load Testing
Business process-based testing
SOA
Boundary value analysis/ testing
50. Can't see - test the functional testing - no access to code and testing is done on UI
Gamma testing
Breadth Testing
black box testing
Equivalence partition Testing