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. Severity - Priority
Impact subheadings
inspection
action
defect
2. Waterfall iterative-incremental "V"
test log uses
Three main SW development models
condition coverage
coverage measurement tools
3. A document that provides the structure for writing test cases.
integration management tools
IEEE test case specification template
test analysis & design tasks
debugging
4. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
IEEE test case specification template
incremental testing
failure
5. Informal testing technique in which test planning and execution run in parallel
nonfunctional requirements
exploratory testing
test analysis & design tasks
waterfall model benefits
6. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
iterative-incremental development models
big-bang testing
driver
7. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
big-bang testing
test management tool features
LCSAJ
8. Deviation of a software system from its expected delivery services or results
failure
big-bang testing
iterative-incremental development models
condition determination coverage
9. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
documentation tools
incident description subheadings
horizontal traceability
component testing
10. Occurrences that happen before and after an unexpected event
anomalous events
ad hoc integration
control flow structure
condition determination coverage
11. Integrate different kinds of tools to make test management more efficient and simple.
acceptance testing
efficiency
automation tools
integration management tools
12. Tools used by developers to identify defects in programs.
debugging tools
error guessing
system testing
backbone integration
13. 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
waterfall model benefits
incident life cycle phases
coverage measurement tools
equivalence partitions
14. 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
test planning Tasks
keyword-driven testing
test log uses
15. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
incident description subheadings
defect
business process-based testing
16. Software products or applications designed to automate manual testing tasks.
functional testing tool
business process-based testing
efficiency
automation tools
17. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
equivalence partitions
error guessing
test analysis & design tasks
documentation tools
18. Used to replace a component that calls another component.
condition determination coverage
alpha testing
driver
acceptance testing
19. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
defect masking
functional testing tool
incident life cycle phases
keyword-driven testing
20. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
IEEE test case specification template
contract acceptance testing
exhaustive testing
21. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
debugging
incident report identifier
monitor
Impact subheadings
22. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
test execution tasks
functional requirements
functionality
23. Tests interfaces between components and between integrated components and systems.
defect masking
integration testing
iterative-incremental development models
error guessing
24. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
data-driven testing
functionality
functional incremental integration
conformance testing tools
25. Develop & proiroitize test cases Create groups of test cases Set up test environment
IEEE incident report template
test implementation tasks
data flow structure
test execution tasks
26. Behavior or response of a software application that you observe when you execute the action steps in the test case.
decision table testing
actual result
conditions
acceptance testing
27. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
control flow structure
backbone integration
test execution tasks
driver
28. Based on analysis of functional specifications of a system.
defect density
agile software development model
test condition
functional testing
29. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
conditions
exit criteria
incident report identifier
boundary value analysis
30. 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.
incident management tools
keyword-driven testing
inspection
data flow structure
31. 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.
business process-based testing
stub
instrumentation
bottom-up integration
32. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
equivalence partitioning
horizontal traceability
exhaustive testing
LCSAJ
33. A table showing combinations of inputs and their associated actions.
decision table
acceptance testing
incident life cycle phases
informal review
34. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
LCSAJ testing
test execution tasks
failure rate
35. Calculates the number of executed branch outcomes in code.
inspection
decision coverage
coverage measurement tools
contract acceptance testing
36. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
conformance testing tools
multiple condition coverage
actual result
contract acceptance testing
37. Integration approach components or subsystems are combined all at once rather than in stages.
equivalence partitioning
operational testing
big-bang testing
component integration testing
38. A document that records the description of each event that occurs during the testing process and that requires further investigation
risk-based testing
error guessing
incident report
IEEE test case specification template
39. Components are combined and tested in the order in which basic functionalities start working
condition determination coverage
acceptance testing
Three main SW development models
functional incremental integration
40. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
automation tools
alpha testing
testing process phases
functional requirements
41. A set of conditions that a system needs to meet in order to be accepted by end users
LCSAJ testing
agile software development model
driver
acceptance criteria
42. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
IEEE incident report template
failure
impact analysis
test control Tasks
43. 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
test tool deployment Success Factors
driver
test planning Tasks
accuracy
44. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incident management tools
incremental testing
cyclomatic complexity
conditions
45. Record details of test cases executed Record order of execution record results
test control Tasks
test log uses
acceptance testing
test condition
46. Components are integrated in the order in which they are developed
system testing
ad hoc integration
business process-based testing
test implementation tasks
47. Testing software in its operational environment
operational testing
equivalence partitioning
incident report identifier
IEEE test case specification template
48. Black-box test design technique - test cases are designed from a decision table.
test tool deployment Success Factors
condition coverage
incident report identifier
decision table testing
49. Special-purpose software used to simulate a component called by the component under test
stub
failure
component integration testing
test management tool features
50. Input or combination of inputs required to test software.
equivalence partitions
Impact subheadings
conditions
testing process phases