SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
CTFL
Start Test
Study First
Subjects
:
certifications
,
ctfl
,
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 code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
incident report
exploratory testing
cyclomatic complexity
component testing
2. Allows storage of test input and expected results in one or more central data sources or databases.
interoperability testing
waterfall model phases
data-driven testing
big-bang testing
3. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
keyword-driven testing
black-box testing
ad hoc integration
4. Tools used to identify and calculate coverage items in program code.
monitor
Three main SW development models
coverage
coverage measurement tools
5. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
equivalence partitions
equivalence partitioning
waterfall model phases
LCSAJ
6. Events that occurred during the testing process our investigation.
data flow structure
Impact subheadings
Incidents
test levels
7. A table showing combinations of inputs and their associated actions.
decision table
functional incremental integration
informal review
alpha testing
8. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
equivalence partitions
environmental needs
conditions
9. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
actual result
data flow structure
condition determination coverage
test execution tasks
10. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations
agile software development model
decision testing
decision table
defect density
11. Sequence in which instructions are executed through a component or system
control flow structure
iterative-incremental development models
acceptance testing
maintainability testing
12. The capability of a software product to provide agreed and correct output with the required degree of precision
functional incremental integration
accuracy
control flow structure
component
13. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
fault attack
maintainability testing
independence of testing
decision testing
14. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
code coverage
test analysis & design tasks
decision coverage
load testing
15. Severity - Priority
contract acceptance testing
Impact subheadings
interoperability testing
documentation tools
16. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
integration testing
contract acceptance testing
error guessing
risk-based testing
17. All possible combinations of input values and preconditions are tested.
decision testing
beta testing
exhaustive testing
LCSAJ testing
18. Waterfall iterative-incremental "V"
entry criteria
risk-based testing
incident life cycle phases
Three main SW development models
19. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
iterative-incremental development models
conditions
maintainability
20. Linear Code Sequence and Jump.
test data preparation tools
black-box testing
LCSAJ
testing process phases
21. Actual inputs required to execute a test case
operational testing
backbone integration
functionality
input specifications
22. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
test planning Tasks
ad hoc integration
maintainability
exit criteria
23. Components are combined and tested in the order in which basic functionalities start working
code coverage
Incidents
functional incremental integration
driver
24. Human action that generates an incorrect result.
error
functionality
functional requirements
testing process phases
25. Record details of test cases executed Record order of execution record results
incident report
test log uses
configuration management
functional testing
26. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
condition coverage
data-driven testing
functionality
anomalous events
27. A component of the incident report that determines the actual effect of the incident on the software and its users.
contract acceptance testing
boundary value analysis
configuration management
impact
28. White-box design technique used to design test cases for a software component using LCSAJ.
decision testing
maintainability testing
inspection
LCSAJ testing
29. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
integration testing
conformance testing tools
defect
keyword-driven testing
30. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
black-box testing
dynamic analysis tools
failure rate
load testing
31. A technique used to improve testing coverage by deliberately introducing faults in code.
load testing
Incidents
fault attack
test analysis & design tasks
32. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
entry criteria
incident report
failure rate
33. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
failure
failure rate
integration
34. Integration approach components or subsystems are combined all at once rather than in stages.
action
incident description subheadings
automation tools
big-bang testing
35. The process of finding analyzing and removing causes of failure in a software product.
Impact subheadings
defect
debugging
agile software development model
36. Tools used by developers to identify defects in programs.
interoperability testing
horizontal traceability
debugging tools
incident report
37. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
actual result
black-box testing
defect
integration management tools
38. Requirements that determine the functionality of a software system.
functional requirements
incident description subheadings
driver
load testing
39. Testing performed to determine whether the system meets acceptance criteria
acceptance testing
interoperability
contract acceptance testing
test analysis & design tasks
40. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.
coverage
inspection
entry criteria
alpha testing
41. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
system testing
horizontal traceability
experience-based techniques
driver
42. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
contract acceptance testing
condition coverage
actual result
entry criteria
43. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
maintainability testing
entry criteria
maintenance testing
44. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
Three main SW development models
dynamic analysis tools
incident description subheadings
maintainability testing
45. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
functional testing tool
nonfunctional requirements
fault attack
beta testing
46. Examine changes made to an operational system cause defects.
maintenance testing
test management tool features
Impact subheadings
incident report identifier
47. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).
acceptance testing
configuration management tools
control flow structure
impact analysis
48. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
component testing
acceptance criteria
driver
COTS
49. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
component integration testing
entry criteria
action
50. Separation of testing responsibilities which encourages the accomplishment of objective testing
environmental needs
data flow structure
backbone integration
independence of testing