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 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+.
Equivalence Class
Accessibility Testing
Acceptance Testing/User Acceptance Testing
N+ Testing
2. 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
Coverage Testing
Branch
architecure of SOA
Loop Testing
3. Stakeholder stakeholder satisfaction with test results report
Exhaustive Testing
providing information - metric
Acceptance criteria
Loop Testing
4. Testing whether the system meets its specified objectives for maintainability.
software testing
Exploratory Testing
Maintainability Testing / Serviceability Testing
Statement coverage
5. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
GUI Testing
Business process-based testing
stop testing timing
Breadth Testing
6. Test case design
Logic coverage Testing / Logic driven Testing / Structural
Concurrency Testing
white box testing
Context Driven Testing
7. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Decision coverage
Testing best practice
Code coverage
Back-to-back testing
8. 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).
Integration Testing
Design based Testing
Decision table testing
Grey Box Testing
9. 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
Decision testing
Fuzz Testing
Equivalence Class
structural testing
10. Determine whether a system meets some specified standard. external organization as complying with the standard
Maintenance testing
white box testing
providing information - metric
Conformance Testing / Compliance Testing / Standards Testing
11. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
Equivalence Class
enough of testing
Interface Testing
Accessibility Testing
12. 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
Quality
Load Testing
Fault
Data flow Testing
13. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Conversion Testing / Migration Testing
Exhaustive Testing
Ad-hoc Testing
Breadth Testing
14. A test suite that exercises the full functionality of a product but does not test features in detail
Breadth Testing
Invalid testing
Code coverage
Arc Testing / Branch Testing
15. executing the software
black box testing
software testing
GUI Testing
Boundary value analysis/ testing
16. 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
Isolation Testing
Compatibility Testing
Branch testing
architecure of SOA
17. Testing software through executing it.
Gamma testing
Defect
Dynamic Testing
Acceptance criteria
18. A white box test design technique in which test cases are designed to execute branches.
Acceptance criteria
architecure of SOA
Conformance Testing / Compliance Testing / Standards Testing
Branch testing
19. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Conformance Testing / Compliance Testing / Standards Testing
functional testing
Code coverage
Grey Box Testing
20. 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
Boundary value analysis/ testing
Interface Testing
Bugs
test coverage
21. Application Under Test
Equivalence partition Testing
Conversion Testing / Migration Testing
AUT
Big Bang Testing
22. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Alpha Testing
Documentation Testing
Data-Driven Testing
backend testing/database testing
23. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
Coverage Testing
Efficiency testing
Authorization Testing
24. 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.
Gamma testing
Localization Testing
Model Based Testing
Back-to-back testing
25. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Breadth Testing
Compatibility Testing
Big Bang Testing
Invalid testing
26. Depends on the schedule and risk based - business impact follow the 20-80 rules
stop testing timing
Testing best practice
structural testing
High order tests
27. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Development testing
Exhaustive Testing
Dynamic Testing
Back-to-back testing
28. 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
Benchmark Testing
Maintenance testing
High order tests
Installation Testing
29. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Maintenance testing
Ad-hoc Testing
functional testing
quality assurance process improvement
30. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Dynamic Testing
Boundary value analysis/ testing
Load Testing
Branch
31. 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.
Concurrency Testing
Maintenance testing
Authorization Testing
Logic coverage Testing / Logic driven Testing / Structural
32. Black-box tests conducted once the software has been integrated
functional testing
Boundary value analysis/ testing
Localization Testing
High order tests
33. Provide critical information during project
Testing best practice
CAST
providing information Objective
Component Testing
34. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
white box testing
functional testing
Decision coverage
Branch
35. 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
providing information Objective
Black Box Testing / Functional Testing
Mutation testing
36. 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
Bugs
Model Based Testing
black box testing
Decision table testing
37. Kind of unit testing - internal working of software
Decision condition testing
Bugs
GUI Testing
structural testing
38. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Boundary value analysis/ testing
Logic coverage Testing / Logic driven Testing / Structural
Conformance Testing / Compliance Testing / Standards Testing
Basis Path Testing
39. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
providing information - metric
Conformance Testing / Compliance Testing / Standards Testing
Benchmark Testing
exploratory testing
40. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Component Testing
Business process-based testing
Incremental testing
Branch coverage
41. A white box testing technique that exercises program loops
Branch
Loop Testing
Maintainability Testing / Serviceability Testing
Conversion Testing / Migration Testing
42. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Equivalence Class
Heuristic evaluations
Bottom-up Testing
Branch coverage
43. The expected results or performance characteristics that define whether the test cases passed or failed
Black Box Testing / Functional Testing
Acceptance criteria
Maintainability Testing / Serviceability Testing
Dynamic Testing
44. 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
Grey Box Testing
Black Box Testing / Functional Testing
N+ Testing
Concurrency Testing
45. 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.
Component Testing
Dynamic Testing
Defect
Integration Testing
46. Approach to doing something that generally give good results when applied appropriately and thoughfully
Quality
Interface Testing
Isolation Testing
best practice
47. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Compatibility Testing
Concurrency Testing
Gorilla Testing
Dependency Testing
48. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Business process-based testing
Decision testing
Branch testing
AUT
49. 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
Coverage Testing
Gorilla Testing
backend testing/database testing
Maintainability Testing / Serviceability Testing
50. 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
best practice
Breadth Testing
Interface Testing
Monkey Testing