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.
Defect
Branch
Accessibility Testing
Exploratory Testing
2. Approach to doing something that generally give good results when applied appropriately and thoughfully
Localization Testing
Testing best practice
best practice
Loop Testing
3. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Alpha Testing
Conversion Testing / Migration Testing
providing information - metric
Context Driven Testing
4. 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
Defect density
Monkey Testing
exploratory testing
Decision condition testing
5. 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
black box testing
Localization Testing
QA
Quality
6. 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.
Branch coverage
Bugs
Model Based Testing
Benchmark Testing
7. 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
Big Bang Testing
Heuristic evaluations
Incremental testing
Localization Testing
8. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Decision testing
backend testing/database testing
structural testing
Benchmark Testing
9. It is a whole - is the whole process form review to plans strategy and whole thing
Integration Testing
Accessibility Testing
Decision condition testing
QA
10. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Loop Testing
Development testing
architecure of SOA
Decision testing
11. 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
Fault
Installation Testing
Decision condition testing
Gorilla Testing
12. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
test coverage
Branch testing
Testing best practice
Decision condition testing
13. The process of testing to determine the efficiency of a software product
Defect density
High order tests
Efficiency testing
Quality
14. 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.
Equivalence partition Testing
Fault
Development testing
architecure of SOA
15. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Invalid testing
Basis Path Testing
Endurance Testing
Context Driven Testing
16. Computer Aided Software Testing
Branch coverage
functional testing
CAST
test coverage
17. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Loop Testing
Decision table testing
Interface Testing
Model Based Testing
18. 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.
Basis Path Testing
Alpha Testing
best practice
End-to-end Testing
19. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
white box testing
Boundary value analysis/ testing
Acceptance Testing/User Acceptance Testing
Depth Testing
20. The testing of individual software components.
providing information - metric
Boundary value analysis/ testing
Maintenance testing
Component Testing
21. The percentage of decision outcomes that have been exercised by a test suite.
Decision coverage
Dynamic Testing
N+ Testing
structural testing
22. Testing whether the system is compatible with other systems with which it should communicate.
Compatibility Testing
Gorilla Testing
Maintainability Testing / Serviceability Testing
Monkey Testing
23. 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.
Beta Testing / Field Testing
Documentation Testing
Defect
N+ Testing
24. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
white box testing
Big Bang Testing
Coverage Testing
Quality
25. 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
Development testing
Efficiency testing
black box testing
Coverage Testing
26. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
Arc Testing / Branch Testing
Branch testing
test coverage
27. A test suite that exercises the full functionality of a product but does not test features in detail
Development testing
Branch
Breadth Testing
quality assurance process improvement
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).
Beta Testing / Field Testing
Design based Testing
Quality
Decision testing
29. Testing one particular module - functionality heavily
End-to-end Testing
Gorilla Testing
Exhaustive Testing
test coverage
30. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
SOA
providing information - metric
Business process-based testing
architecure of SOA
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
Concurrency Testing
GUI Testing
Decision testing
Compatibility Testing
32. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.
Context Driven Testing
Acceptance criteria
QA
Development testing
33. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices
Installation Testing
Data-Driven Testing
Business process-based testing
architecure of SOA
34. Can't see - test the functional testing - no access to code and testing is done on UI
Keyword driven Testing
Code coverage
Equivalence Partitioning
black box testing
35. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Dependency Testing
SOA
Equivalence partition Testing
Model Based Testing
36. 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
Accessibility Testing
Acceptance Testing/User Acceptance Testing
Ad-hoc Testing
37. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Exhaustive Testing
Acceptance criteria
Agile Testing
Interface Testing
38. 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
Equivalence Class
Bugs
Ad-hoc Testing
Statement coverage
39. A test that exercises a feature of a product in full detail.
Depth Testing
Integration Testing
Branch
Conformance Testing / Compliance Testing / Standards Testing
40. Depends on the schedule and risk based - business impact follow the 20-80 rules
stop testing timing
Development testing
Acceptance criteria
Authorization Testing
41. 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
quality assurance process improvement
Exploratory Testing
Black Box Testing / Functional Testing
Incremental testing
42. This term refers to making software specifically designed for a specific locality
Localization Testing
Maintenance testing
SOA
Interoperability testing
43. A white box test design technique in which test cases are designed to execute decision outcomes
Boundary value analysis/ testing
Development testing
Conversion Testing / Migration Testing
Decision testing
44. 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.
Coverage Testing
End-to-end Testing
Bottom-up Testing
Fault
45. Checks for memory leaks or other problems that may occur with prolonged execution
Exploratory Testing
Back-to-back testing
Basis Path Testing
Endurance Testing
46. 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
Branch coverage
Acceptance Testing/User Acceptance Testing
Gorilla Testing
Isolation Testing
47. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Accessibility Testing
functional testing
Concurrency Testing
Grey Box Testing
48. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
Branch coverage
white box testing
High order tests
backend testing/database testing
49. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
GUI Testing
Gorilla Testing
Defect density
Documentation Testing
50. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
Defect
Monkey Testing
Data-Driven Testing