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. 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
conditions
agile software development model
component integration testing
driver
2. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
cyclomatic complexity
backbone integration
maintainability testing
test levels
3. Component - Integration - System - Acceptance
stub
test levels
agile software development model
IEEE test case specification template
4. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
functional testing
decision testing
fault attack
defect masking
5. Separation of testing responsibilities which encourages the accomplishment of objective testing
equivalence partitioning
decision table
waterfall model phases
independence of testing
6. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
configuration management
waterfall model phases
Incidents
7. White-box design technique used to design test cases for a software component using LCSAJ.
dynamic analysis tools
component testing
equivalence partitioning
LCSAJ testing
8. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
equivalence partitioning
COTS
waterfall model phases
defect
9. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
failure
cyclomatic complexity
condition determination coverage
actual result
10. 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).
data-driven testing
configuration management tools
beta testing
configuration management
11. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
fault attack
ad hoc integration
operational testing
test management tool features
12. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables
debugging tools
decision coverage
boundary value analysis
waterfall model benefits
13. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
testing process phases
exhaustive testing
interoperability testing
14. A review not based on a formal documented procedure
test levels
IEEE test case specification template
informal review
defect
15. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
conformance testing tools
COTS
test tool deployment Success Factors
independence of testing
16. Occurrences that happen before and after an unexpected event
anomalous events
incident life cycle phases
incident description subheadings
exhaustive testing
17. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
interoperability testing
load testing
black-box testing
impact analysis
18. An event or item that can be tested using one or more test cases
big-bang testing
fault attack
condition coverage
test condition
19. 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
stub
resolution types
waterfall model phases
test tool deployment Success Factors
20. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
error
load testing
incident report identifier
21. Events that occurred during the testing process our investigation.
LCSAJ testing
actual result
condition coverage
Incidents
22. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
defect density
IEEE incident report template
decision table
incident description subheadings
23. Testing an integrated system to validate it meets requirements
system testing
test levels
resolution types
inspection
24. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
monitor
alpha testing
coverage
IEEE test case specification template
25. Behavior or response of a software application that you observe when you execute the action steps in the test case.
resolution types
actual result
waterfall model benefits
acceptance criteria
26. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
condition coverage
testing process phases
acceptance criteria
interoperability testing
27. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
equivalence partitions
interoperability testing
test execution tasks
beta testing
28. 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
test data preparation tools
test implementation tasks
decision testing
business process-based testing
29. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
risk-based testing
experience-based techniques
error guessing
testing process phases
30. A set of conditions that a system needs to meet in order to be accepted by end users
functional requirements
incident report identifier
acceptance criteria
maintainability
31. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
interoperability
debugging tools
input specifications
32. The ratio between the number of defects found and the size of the component/system tested.
integration management tools
test implementation tasks
defect density
failure
33. Human action that generates an incorrect result.
error
Three main SW development models
functionality
control flow structure
34. Develop & proiroitize test cases Create groups of test cases Set up test environment
test levels
decision table testing
test implementation tasks
exit criteria
35. Black-box test design technique - test cases are designed from a decision table.
decision table testing
dynamic analysis tools
experience-based techniques
integration
36. Actual inputs required to execute a test case
SW development model
equivalence partitions
backbone integration
input specifications
37. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
risk-based testing
independence of testing
data flow structure
IEEE test case specification template
38. Special additions or changes to the environment required to run a test case.
environmental needs
conditions
component testing
accuracy
39. Process used to create a SW product from initial conception to public release
system testing
alpha testing
functional testing
SW development model
40. Severity - Priority
stub
Impact subheadings
waterfall model phases
functionality
41. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
impact
iterative-incremental development models
agile software development model
test planning Tasks
42. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
waterfall model benefits
action
maintainability testing
stub
43. The smallest software item that can be tested in isolation.
component
coverage measurement tools
defect density
configuration management tools
44. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functional testing tool
functionality
ad hoc integration
entry criteria
45. Examine changes made to an operational system cause defects.
maintenance testing
decision table
experience-based techniques
efficiency
46. 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.
inspection
environmental needs
agile software development model
beta testing
47. One defect prevents the detection of another.
defect masking
test execution tasks
black-box testing
IEEE test case specification template
48. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
SW development model
interoperability
configuration management tools
49. Response of the application to an input
maintenance testing
integration management tools
action
test execution tasks
50. A task of maintaining and controlling changes to all entities of a system.
maintainability
backbone integration
configuration management
impact