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 carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
Business process-based testing
Endurance Testing
Branch testing
2. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
Basis Path Testing
Documentation Testing
Installation Testing
3. Testing in which test cases are designed based on variable usage within the code.
Decision testing
Development testing
Data flow Testing
Alpha Testing
4. Testing which covers all combinations of input values and preconditions for an element of the software under test
Exhaustive Testing
Installation Testing
Acceptance criteria
stop testing timing
5. Similar to black box testing - structure of test cases in order to find defects and its strutured
test coverage
Conversion Testing / Migration Testing
Accessibility Testing
functional testing
6. A white box test design technique in which test cases are designed to execute decision outcomes
Efficiency testing
Compatibility Testing
Documentation Testing
Decision testing
7. 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.
quality assurance process improvement
functional testing
Code coverage
Bottom-up Testing
8. 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
Gamma testing
Breadth Testing
Isolation Testing
Data-Driven Testing
9. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Equivalence partition Testing
Incremental testing
test coverage
Interoperability testing
10. 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
Maintenance testing
Monkey Testing
High order tests
SOA
11. Black-box tests conducted once the software has been integrated
Ad-hoc Testing
Localization Testing
Defect density
High order tests
12. An accidental condition that causes the failure of a component in the implementation model to perform its required behavior. A fault is the root cause of one or more defects identified by observing one or more failures.
SOA
architecure of SOA
Fault
Mutation testing
13. A white box testing technique that exercises program loops
Alpha Testing
Big Bang Testing
Loop Testing
Decision testing
14. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Dependency Testing
Coverage Testing
Alpha Testing
Depth Testing
15. A white box test design technique in which test cases are designed to execute branches.
Branch testing
black box testing
Dynamic Testing
SOA
16. Approach to doing something that generally give good results when applied appropriately and thoughfully
Basis Path Testing
Authorization Testing
Integration Testing
best practice
17. 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
providing information Objective
Concurrency Testing
Equivalence Class
Beta Testing / Field Testing
18. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Exploratory Testing
organisation structure
Branch testing
Isolation Testing
19. 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.
Grey Box Testing
Accessibility Testing
Arc Testing / Branch Testing
End-to-end Testing
20. 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
Business process-based testing
Boundary value analysis/ testing
Decision coverage
Integration Testing
21. A white box test case design techniques that uses the algorithmic flow of the program to design tests
software testing
Boundary value analysis/ testing
functional testing
Basis Path Testing
22. 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
organisation structure
Quality
Equivalence partition Testing
Accessibility Testing
23. Testing the changes to an operational system or the impact of a changed environment to an operational system
Maintenance testing
GUI Testing
Dependency Testing
Equivalence Partitioning
24. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Incremental testing
Beta Testing / Field Testing
Gamma testing
enough of testing
25. Root cause analyst - base of the problem - customer satisfaction report
quality assurance process improvement
Business process-based testing
Boundary value analysis/ testing
Model Based Testing
26. 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
Acceptance Testing/User Acceptance Testing
test coverage
CAST
SOA
27. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Concurrency Testing
backend testing/database testing
Heuristic evaluations
Gamma testing
28. Can't see - test the functional testing - no access to code and testing is done on UI
black box testing
Alpha Testing
enough of testing
Conversion Testing / Migration Testing
29. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Incremental testing
Component Testing
Defect
Documentation 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
enough of testing
exploratory testing
Equivalence partition Testing
SOA
31. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Big Bang Testing
Breadth Testing
Heuristic evaluations
Grey Box Testing
32. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Concurrency Testing
Gamma testing
Equivalence Partitioning
white box testing
33. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Testing best practice
Documentation Testing
backend testing/database testing
Fuzz Testing
34. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Endurance Testing
Testing best practice
Branch coverage
Accessibility Testing
35. Stakeholder stakeholder satisfaction with test results report
Code coverage
providing information - metric
Breadth Testing
Coverage Testing
36. 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
N+ Testing
Component Testing
Heuristic evaluations
Authorization Testing
37. A test suite that exercises the full functionality of a product but does not test features in detail
enough of testing
Acceptance criteria
Breadth Testing
Decision table testing
38. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Benchmark Testing
Dependency Testing
Business process-based testing
Gorilla Testing
39. It is a whole - is the whole process form review to plans strategy and whole thing
QA
Load Testing
Mutation testing
stop testing timing
40. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Decision condition testing
Heuristic evaluations
Arc Testing / Branch Testing
structural testing
41. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Acceptance Testing/User Acceptance Testing
backend testing/database testing
Equivalence partition Testing
Exploratory 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.
Code coverage
QA
Benchmark Testing
structural testing
43. 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).
GUI Testing
Equivalence partition Testing
Fault
Design based Testing
44. 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
Installation Testing
Efficiency testing
Keyword driven Testing
Beta Testing / Field Testing
45. The process of testing to determine the efficiency of a software product
Efficiency testing
Black Box Testing / Functional Testing
providing information Objective
Installation Testing
46. 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
Endurance Testing
Branch
Efficiency testing
providing information Objective
47. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Conversion Testing / Migration Testing
AUT
Branch
stop testing timing
48. 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.
Endurance Testing
Code coverage
Branch
Authorization Testing
49. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
SOA
Benchmark Testing
stop testing timing
enough of testing
50. Kind of unit testing - internal working of software
Interoperability testing
structural testing
Equivalence Class
Integration Testing