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. 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
Grey Box Testing
Equivalence Class
QA
Documentation Testing
2. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Basis Path Testing
Quality
providing information Objective
Testing best practice
3. Testing using input values that should be rejected by the component or system
Acceptance criteria
Depth Testing
Compatibility Testing
Invalid testing
4. 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)
Conformance Testing / Compliance Testing / Standards Testing
Design based Testing
Defect density
GUI Testing
5. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Decision testing
Alpha Testing
best practice
Fault
6. 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
exploratory testing
Development testing
Fuzz Testing
7. 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
Data-Driven Testing
Gamma testing
Exploratory Testing
8. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Component Testing
Keyword driven Testing
Concurrency Testing
white box testing
9. 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.
Acceptance criteria
Benchmark Testing
Bottom-up Testing
Integration Testing
10. 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
Localization Testing
black box testing
Design based Testing
Installation Testing
11. A test that exercises a feature of a product in full detail.
best practice
Depth Testing
Decision coverage
Isolation Testing
12. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Incremental testing
Boundary value analysis/ testing
Data flow Testing
Code coverage
13. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Load Testing
Integration Testing
Incremental testing
Dynamic Testing
14. The expected results or performance characteristics that define whether the test cases passed or failed
white box testing
Data-Driven Testing
Interface Testing
Acceptance criteria
15. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
CAST
Branch coverage
Equivalence Partitioning
End-to-end Testing
16. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Invalid testing
Decision condition testing
Dynamic Testing
quality assurance process improvement
17. A white box test design technique in which test cases are designed to execute decision outcomes
Monkey Testing
Invalid testing
Boundary value analysis/ testing
Decision testing
18. Black-box tests conducted once the software has been integrated
High order tests
Equivalence Class
software testing
Loop Testing
19. 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.
Dynamic Testing
best practice
Authorization Testing
Code coverage
20. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Testing best practice
Equivalence Class
Isolation Testing
black box testing
21. 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
providing information - metric
Gamma testing
Branch
Grey Box Testing
22. 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.
Concurrency Testing
Arc Testing / Branch Testing
Breadth Testing
Equivalence Class
23. Test case design
Logic coverage Testing / Logic driven Testing / Structural
Exhaustive Testing
Localization Testing
architecure of SOA
24. 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
Decision testing
Dynamic Testing
Bugs
Integration Testing
25. The testing of individual software components.
Component Testing
Exhaustive Testing
Gorilla Testing
Grey Box Testing
26. Testing which covers all combinations of input values and preconditions for an element of the software under test
Exhaustive Testing
Depth Testing
Design based Testing
Defect
27. Testing one particular module - functionality heavily
Bottom-up Testing
Gorilla Testing
Big Bang Testing
Efficiency testing
28. 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
High order tests
Bugs
Statement coverage
enough of testing
29. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Equivalence Class
Gorilla Testing
Alpha Testing
Benchmark Testing
30. 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.
Concurrency Testing
Code coverage
Alpha Testing
structural testing
31. A white box test design technique in which test cases are designed to execute branches.
Monkey Testing
Branch testing
Maintainability Testing / Serviceability Testing
Interface Testing
32. Computer Aided Software Testing
CAST
Component Testing
Basis Path Testing
Acceptance criteria
33. 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
software testing
Context Driven Testing
test coverage
AUT
34. 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
Maintainability Testing / Serviceability Testing
Dynamic Testing
Documentation Testing
Decision table testing
35. 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).
Installation Testing
Branch
Design based Testing
Equivalence partition Testing
36. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
GUI Testing
backend testing/database testing
Business process-based testing
Conversion Testing / Migration Testing
37. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Bugs
Decision table testing
Development testing
CAST
38. Testing the changes to an operational system or the impact of a changed environment to an operational system
Logic coverage Testing / Logic driven Testing / Structural
Maintenance testing
Keyword driven Testing
Data flow Testing
39. Testing in which test cases are designed based on variable usage within the code.
Code coverage
Invalid testing
Quality
Data flow Testing
40. Similar to black box testing - structure of test cases in order to find defects and its strutured
providing information - metric
functional testing
GUI Testing
Bottom-up Testing
41. A test suite that exercises the full functionality of a product but does not test features in detail
Code coverage
Context Driven Testing
Ad-hoc Testing
Breadth Testing
42. Determine whether a system meets some specified standard. external organization as complying with the standard
Acceptance Testing/User Acceptance Testing
Conformance Testing / Compliance Testing / Standards Testing
Boundary value analysis/ testing
Equivalence Partitioning
43. 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
Breadth Testing
Keyword driven Testing
Mutation testing
Alpha Testing
44. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Accessibility Testing
Localization Testing
black box testing
Loop Testing
45. 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
Decision table testing
Dynamic Testing
SOA
Fuzz Testing
46. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
backend testing/database testing
Data-Driven Testing
Black Box Testing / Functional Testing
Localization Testing
47. 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
Installation Testing
End-to-end Testing
Concurrency Testing
Decision condition testing
48. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Dependency Testing
Acceptance criteria
Equivalence Class
Data flow Testing
49. Depends on the schedule and risk based - business impact follow the 20-80 rules
providing information Objective
Acceptance Testing/User Acceptance Testing
stop testing timing
Loop Testing
50. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Invalid testing
Alpha Testing
Compatibility Testing
Business process-based testing