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. Software products or applications designed to automate manual testing tasks.
instrumentation
automation tools
test execution tasks
data flow structure
2. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
instrumentation
incident life cycle phases
black-box testing
debugging
3. 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.
risk-based testing
defect masking
exit criteria
inspection
4. The process of finding analyzing and removing causes of failure in a software product.
alpha testing
debugging
equivalence partitions
integration testing
5. Specific groups that represent a set of valid or invalid partitions for input conditions.
actual result
equivalence partitions
control flow structure
interoperability
6. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
SW development model
risk-based testing
actual result
cause-effect graphic testing
7. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
decision table
interoperability testing
test execution tasks
coverage measurement tools
8. Human action that generates an incorrect result.
error
impact analysis
test data preparation tools
load testing
9. Deviation of a software system from its expected delivery services or results
fault attack
debugging
failure
cyclomatic complexity
10. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
impact analysis
acceptance criteria
monitor
fault attack
11. Used to replace a component that calls another component.
keyword-driven testing
functional testing tool
driver
environmental needs
12. Based on analysis of functional specifications of a system.
system testing
ad hoc integration
functional testing
black-box testing
13. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test analysis & design tasks
action
test log uses
decision testing
14. Testing performed to determine whether the system meets acceptance criteria
equivalence partitions
configuration management
acceptance testing
Three main SW development models
15. Components are integrated in the order in which they are developed
SW development model
test analysis & design tasks
decision coverage
ad hoc integration
16. Process used to create a SW product from initial conception to public release
maintenance testing
maintainability testing
SW development model
impact analysis
17. Tests interfaces between components and between integrated components and systems.
integration testing
data flow structure
action
equivalence partitions
18. Actual inputs required to execute a test case
interoperability
interoperability testing
cause-effect graphic testing
input specifications
19. Severity - Priority
component
IEEE test case specification template
informal review
Impact subheadings
20. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
environmental needs
test log uses
cyclomatic complexity
agile software development model
21. 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
informal review
defect
agile software development model
backbone integration
22. Calculates the number of executed branch outcomes in code.
functional requirements
test control Tasks
decision coverage
stub
23. Testing software in its operational environment
beta testing
Impact subheadings
operational testing
configuration management tools
24. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons
exit criteria
test tool deployment Success Factors
inspection
component testing
25. A table showing combinations of inputs and their associated actions.
functional testing
decision table
backbone integration
driver
26. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
decision testing
functional testing tool
condition coverage
dynamic analysis tools
27. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
exploratory testing
operational testing
nonfunctional requirements
documentation tools
28. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
dynamic analysis tools
decision table testing
LCSAJ testing
COTS
29. Combining components or sytems into larger structural units or subsystems.
integration
big-bang testing
risk-based testing
defect
30. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
maintainability testing
IEEE test case specification template
impact analysis
test planning Tasks
31. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
environmental needs
resolution types
component integration testing
integration management tools
32. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
decision testing
Impact subheadings
cause-effect graphic testing
independence of testing
33. 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).
business process-based testing
resolution types
configuration management tools
acceptance criteria
34. Record details of test cases executed Record order of execution record results
ad hoc integration
incident report identifier
load testing
test log uses
35. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
multiple condition coverage
environmental needs
bottom-up integration
36. Occurrences that happen before and after an unexpected event
maintainability testing
component testing
test implementation tasks
anomalous events
37. Linear Code Sequence and Jump.
test planning Tasks
iterative-incremental development models
integration testing
LCSAJ
38. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
defect
interoperability
accuracy
39. All possible combinations of input values and preconditions are tested.
inspection
exhaustive testing
IEEE test case specification template
system testing
40. An event or item that can be tested using one or more test cases
informal review
waterfall model benefits
test condition
acceptance testing
41. Ability of software to provide appropriate performance relative to amount of resources used.
error
beta testing
SW development model
efficiency
42. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template
conditions
test management tool features
risk-based testing
test data preparation tools
43. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
big-bang testing
integration
functionality
debugging
44. A unique identifier for each incident report generated during test execution.
dynamic analysis tools
environmental needs
incident report identifier
coverage measurement tools
45. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
conditions
instrumentation
coverage measurement tools
experience-based techniques
46. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
contract acceptance testing
interoperability
nonfunctional requirements
keyword-driven testing
47. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
conditions
debugging tools
keyword-driven testing
driver
48. Measures amount of testing performed by a collection of test cases
impact
coverage
functional incremental integration
incremental testing
49. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
configuration management tools
defect masking
black-box testing
impact
50. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
functional testing tool
test levels
beta testing