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. An event or item that can be tested using one or more test cases
Incidents
test condition
informal review
test management tool features
2. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
conformance testing tools
documentation tools
test management tool features
3. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities
horizontal traceability
test planning Tasks
decision table
test analysis & design tasks
4. A document that records the description of each event that occurs during the testing process and that requires further investigation
test implementation tasks
functional requirements
inspection
incident report
5. 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
Incidents
agile software development model
decision coverage
inspection
6. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
debugging
anomalous events
maintenance testing
7. White-box design technique used to design test cases for a software component using LCSAJ.
COTS
test levels
IEEE incident report template
LCSAJ testing
8. 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
functional requirements
test tool deployment Success Factors
system testing
documentation tools
9. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
test management tool features
independence of testing
input specifications
10. Behavior or response of a software application that you observe when you execute the action steps in the test case.
debugging
informal review
conditions
actual result
11. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
multiple condition coverage
debugging
experience-based techniques
12. Integrate different kinds of tools to make test management more efficient and simple.
waterfall model benefits
defect density
condition coverage
integration management tools
13. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
accuracy
agile software development model
boundary value analysis
14. Increased load (transations) used to test behavior of system under high volume.
risk-based testing
SW development model
load testing
integration management tools
15. Testing an integrated system to validate it meets requirements
boundary value analysis
system testing
test tool deployment Success Factors
waterfall model benefits
16. Tools used to identify and calculate coverage items in program code.
interoperability
coverage measurement tools
driver
stub
17. Find defects in code while the software application being tested is running.
dynamic analysis tools
conditions
component integration testing
acceptance criteria
18. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
decision table testing
failure rate
incident report identifier
experience-based techniques
19. Waterfall iterative-incremental "V"
driver
Three main SW development models
integration management tools
error
20. 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
backbone integration
test data preparation tools
data-driven testing
waterfall model benefits
21. 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
system testing
test data preparation tools
condition determination coverage
test execution tasks
22. Occurrences that happen before and after an unexpected event
component integration testing
anomalous events
configuration management
test log uses
23. An analysis that determines the portion of code on software executed by a set of test cases
defect masking
test analysis & design tasks
code coverage
load testing
24. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
fault attack
test levels
alpha testing
component integration testing
25. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
incident life cycle phases
multiple condition coverage
cause-effect graphic testing
resolution types
26. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.
COTS
environmental needs
beta testing
bottom-up integration
27. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
conformance testing tools
keyword-driven testing
documentation tools
test log uses
28. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
contract acceptance testing
data-driven testing
test execution tasks
exit criteria
29. Tests interfaces between components and between integrated components and systems.
LCSAJ
Three main SW development models
decision table
integration testing
30. A unique identifier for each incident report generated during test execution.
integration
operational testing
incident report identifier
automation tools
31. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
IEEE test case specification template
decision testing
efficiency
contract acceptance testing
32. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
iterative-incremental development models
integration testing
big-bang testing
experience-based techniques
33. Allows storage of test input and expected results in one or more central data sources or databases.
test log uses
error
data-driven testing
integration
34. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
incident life cycle phases
system testing
multiple condition coverage
35. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
defect
multiple condition coverage
IEEE incident report template
36. Severity - Priority
IEEE test case specification template
Impact subheadings
functional requirements
defect
37. Requirements that determine the functionality of a software system.
bottom-up integration
component testing
system testing
functional requirements
38. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
incremental testing
exploratory testing
environmental needs
conformance testing tools
39. The ratio between the number of defects found and the size of the component/system tested.
defect density
exit criteria
environmental needs
component testing
40. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
documentation tools
incident description subheadings
incident report identifier
41. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
beta testing
maintainability
boundary value analysis
impact analysis
42. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
waterfall model phases
input specifications
keyword-driven testing
acceptance testing
43. Actual inputs required to execute a test case
input specifications
integration management tools
exploratory testing
error
44. Testing software in its operational environment
test analysis & design tasks
functional requirements
black-box testing
operational testing
45. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
test control Tasks
testing process phases
inspection
input specifications
46. Testing software components that are separately testable. Also module program and unit testing.
integration management tools
iterative-incremental development models
action
component testing
47. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
agile software development model
conditions
cause-effect graphic testing
48. Operational testing performed at an _external_ site without involvement of the developing organization.
configuration management
multiple condition coverage
beta testing
test implementation tasks
49. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
experience-based techniques
functionality
risk-based testing
50. 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.
defect
anomalous events
incremental testing
inspection