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. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Branch coverage
Testing best practice
Decision table testing
GUI Testing
2. 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
Documentation Testing
Efficiency testing
Quality
Interoperability testing
3. 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.
Beta Testing / Field Testing
Fault
Conformance Testing / Compliance Testing / Standards Testing
Incremental testing
4. Testing whether the system is compatible with other systems with which it should communicate.
Business process-based testing
Decision coverage
white box testing
Compatibility Testing
5. Approach to doing something that generally give good results when applied appropriately and thoughfully
best practice
Loop Testing
Interface Testing
Equivalence partition Testing
6. Black-box tests conducted once the software has been integrated
Bottom-up Testing
Breadth Testing
High order tests
Equivalence partition Testing
7. 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
Black Box Testing / Functional Testing
Quality
Depth Testing
Code coverage
8. Testing the changes to an operational system or the impact of a changed environment to an operational system
SOA
Statement coverage
Maintenance testing
Defect density
9. 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
Invalid testing
Agile Testing
Decision table testing
Beta Testing / Field Testing
10. 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
Back-to-back testing
Context Driven Testing
Decision table testing
QA
11. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Decision table testing
Dependency Testing
Interface Testing
Component Testing
12. 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
Endurance Testing
Authorization Testing
Mutation testing
Maintainability Testing / Serviceability Testing
13. Provide critical information during project
providing information Objective
Load Testing
Decision condition testing
Fuzz Testing
14. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
High order tests
Ad-hoc Testing
organisation structure
architecure of SOA
15. Testing software through executing it.
Invalid testing
Dynamic Testing
Defect
architecure of SOA
16. A white box test design technique in which test cases are designed to execute branches.
Arc Testing / Branch Testing
Accessibility Testing
Testing best practice
Branch testing
17. 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.
Fault
Boundary value analysis/ testing
Dependency Testing
Ad-hoc Testing
18. The process of testing to determine the efficiency of a software product
Data-Driven Testing
Efficiency testing
Exploratory Testing
enough of 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.
Decision condition testing
Fault
Arc Testing / Branch Testing
Dependency Testing
20. Testing concerned with the accuracy of documentation.
Documentation Testing
providing information - metric
End-to-end Testing
Invalid testing
21. 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
Logic coverage Testing / Logic driven Testing / Structural
Acceptance Testing/User Acceptance Testing
Gamma testing
structural testing
22. 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
Heuristic evaluations
Branch testing
Acceptance Testing/User Acceptance Testing
End-to-end Testing
23. 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
Loop Testing
Design based Testing
Monkey Testing
Accessibility Testing
24. A test that exercises a feature of a product in full detail.
Depth Testing
providing information Objective
Conversion Testing / Migration Testing
Code coverage
25. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
backend testing/database testing
Grey Box Testing
Invalid testing
Basis Path Testing
26. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
Load Testing
Benchmark Testing
architecure of SOA
27. Testing using input values that should be rejected by the component or system
providing information Objective
Decision coverage
Invalid testing
Conformance Testing / Compliance Testing / Standards Testing
28. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
AUT
Efficiency testing
Branch coverage
Beta Testing / Field 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
Incremental testing
Conversion Testing / Migration Testing
N+ Testing
Integration Testing
30. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
AUT
Branch
Alpha Testing
Keyword driven Testing
31. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Data-Driven Testing
Authorization Testing
Basis Path Testing
Conversion Testing / Migration Testing
32. 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.
Authorization Testing
structural testing
enough of testing
best practice
33. 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.
Equivalence partition Testing
SOA
End-to-end Testing
Loop Testing
34. executing the software
Loop Testing
software testing
Integration Testing
Authorization Testing
35. 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.
Installation Testing
Model Based Testing
Bottom-up Testing
exploratory testing
36. 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
Interoperability testing
Branch
providing information Objective
Keyword driven Testing
37. Depends on the schedule and risk based - business impact follow the 20-80 rules
Basis Path Testing
Grey Box Testing
Equivalence Partitioning
stop testing timing
38. Stakeholder stakeholder satisfaction with test results report
Interoperability testing
Alpha Testing
Exploratory Testing
providing information - metric
39. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Context Driven Testing
Code coverage
Equivalence Partitioning
Agile Testing
40. 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
Big Bang Testing
Concurrency Testing
structural testing
best practice
41. Test case design
providing information Objective
Logic coverage Testing / Logic driven Testing / Structural
Acceptance criteria
Boundary value analysis/ testing
42. Testing whether the system meets its specified objectives for maintainability.
Maintenance testing
stop testing timing
Invalid testing
Maintainability Testing / Serviceability Testing
43. Root cause analyst - base of the problem - customer satisfaction report
Back-to-back testing
quality assurance process improvement
Dynamic Testing
Maintainability Testing / Serviceability Testing
44. 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.
Acceptance criteria
Fuzz Testing
Statement coverage
Concurrency Testing
45. 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
Quality
Interoperability testing
architecure of SOA
Documentation Testing
46. Kind of unit testing - internal working of software
white box testing
Bugs
structural testing
Business process-based testing
47. 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
Localization Testing
Business process-based testing
Back-to-back testing
Model Based Testing
48. 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
Maintainability Testing / Serviceability Testing
Code coverage
Data-Driven Testing
Decision coverage
49. Similar to black box testing - structure of test cases in order to find defects and its strutured
Defect
functional testing
Branch
Benchmark Testing
50. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Ad-hoc Testing
Isolation Testing
Fuzz Testing
Documentation Testing