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. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Decision condition testing
Testing best practice
Boundary value analysis/ testing
Alpha Testing
2. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Boundary value analysis/ testing
GUI Testing
exploratory testing
Accessibility Testing
3. Once the alpha phase is complete development enters the beta phase. Versions of the software known as beta-versions are released to a limited audience outside of the company to ensure that the product has few faults or bugs. black box
Testing best practice
Incremental testing
Fuzz Testing
Beta Testing / Field Testing
4. Testing in which test cases are designed based on variable usage within the code.
Compatibility Testing
Localization Testing
Data flow Testing
Acceptance Testing/User Acceptance Testing
5. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Incremental testing
Equivalence partition Testing
Authorization Testing
Statement coverage
6. Black-box tests conducted once the software has been integrated
High order tests
Endurance Testing
structural testing
Compatibility Testing
7. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Concurrency Testing
Testing best practice
Mutation testing
Equivalence Partitioning
8. Testing whether the system meets its specified objectives for maintainability.
Gorilla Testing
Defect
structural testing
Maintainability Testing / Serviceability Testing
9. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
N+ Testing
Boundary value analysis/ testing
Testing best practice
10. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Maintainability Testing / Serviceability Testing
Branch coverage
Keyword driven Testing
SOA
11. 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.
Boundary value analysis/ testing
Coverage Testing
Equivalence Class
AUT
12. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
organisation structure
SOA
Incremental testing
Development testing
13. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Concurrency Testing
Acceptance criteria
black box testing
Business process-based testing
14. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Integration Testing
Endurance Testing
white box testing
Decision table testing
15. Kind of unit testing - internal working of software
Defect
Logic coverage Testing / Logic driven Testing / Structural
structural testing
Maintenance testing
16. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
SOA
Decision condition testing
Gamma testing
Accessibility Testing
17. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Compatibility Testing
Decision testing
enough of testing
Integration Testing
18. 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
Efficiency testing
best practice
test coverage
End-to-end Testing
19. The expected results or performance characteristics that define whether the test cases passed or failed
End-to-end Testing
Acceptance criteria
Bottom-up Testing
Coverage Testing
20. Root cause analyst - base of the problem - customer satisfaction report
quality assurance process improvement
Maintainability Testing / Serviceability Testing
Business process-based testing
Invalid testing
21. executing the software
Incremental testing
Dependency Testing
software testing
Mutation testing
22. Testing the changes to an operational system or the impact of a changed environment to an operational system
Boundary value analysis/ testing
Exploratory Testing
Maintenance testing
Branch
23. 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
architecure of SOA
organisation structure
Efficiency testing
Boundary value analysis/ testing
24. 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
Acceptance criteria
Concurrency Testing
Interface Testing
Dependency Testing
25. The testing of individual software components.
Component Testing
Agile Testing
Testing best practice
SOA
26. A test suite that exercises the full functionality of a product but does not test features in detail
Load Testing
Alpha Testing
Breadth Testing
Basis Path Testing
27. 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
QA
Interface Testing
GUI Testing
Black Box Testing / Functional Testing
28. 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)
Decision coverage
Monkey Testing
Defect density
Load Testing
29. 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
Fault
Integration Testing
Component Testing
Decision coverage
30. 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
Interoperability testing
test coverage
Acceptance Testing/User Acceptance Testing
AUT
31. Application Under Test
Maintainability Testing / Serviceability Testing
Decision table testing
AUT
functional testing
32. 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
Defect
Exhaustive Testing
Back-to-back testing
Model Based Testing
33. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Load Testing
Exhaustive Testing
Business process-based testing
Data flow Testing
34. Can't see - test the functional testing - no access to code and testing is done on UI
Basis Path Testing
software testing
black box testing
Invalid 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).
Context Driven Testing
Design based Testing
Ad-hoc Testing
Bottom-up Testing
36. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Alpha Testing
Equivalence Partitioning
Integration Testing
Model Based Testing
37. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Localization Testing
Development testing
High order tests
Mutation testing
38. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Exploratory Testing
Conformance Testing / Compliance Testing / Standards Testing
Interface Testing
white box testing
39. 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
SOA
Business process-based testing
Data flow Testing
Black Box Testing / Functional Testing
40. 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
backend testing/database testing
Decision table testing
GUI Testing
Defect
41. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Maintainability Testing / Serviceability Testing
Isolation Testing
Statement coverage
Context Driven 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.
Development testing
SOA
Code coverage
QA
43. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Benchmark Testing
Keyword driven Testing
Documentation Testing
black box testing
44. Testing using input values that should be rejected by the component or system
Interoperability testing
Maintenance testing
backend testing/database testing
Invalid testing
45. 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
Gamma testing
test coverage
Authorization Testing
Installation Testing
46. Stakeholder stakeholder satisfaction with test results report
Monkey Testing
providing information - metric
QA
Coverage Testing
47. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Branch testing
Agile Testing
Fault
Arc Testing / Branch Testing
48. It is a whole - is the whole process form review to plans strategy and whole thing
QA
Grey Box Testing
best practice
architecure of SOA
49. Testing one particular module - functionality heavily
Bottom-up Testing
Gorilla Testing
Conversion Testing / Migration Testing
End-to-end Testing
50. The percentage of decision outcomes that have been exercised by a test suite.
Decision coverage
Load Testing
Coverage Testing
Equivalence partition Testing