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. Separation of testing responsibilities which encourages the accomplishment of objective testing
test tool deployment Success Factors
independence of testing
load testing
conformance testing tools
2. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
incident life cycle phases
independence of testing
interoperability testing
defect masking
3. Develop & proiroitize test cases Create groups of test cases Set up test environment
test condition
equivalence partitions
test implementation tasks
condition coverage
4. Requirements that determine the functionality of a software system.
contract acceptance testing
functional requirements
operational testing
test log uses
5. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
conditions
conformance testing tools
cause-effect graphic testing
functional requirements
6. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
coverage
failure
functional testing tool
defect
7. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
functional requirements
independence of testing
horizontal traceability
COTS
8. Software products or applications designed to automate manual testing tasks.
automation tools
exploratory testing
keyword-driven testing
condition coverage
9. Input or combination of inputs required to test software.
alpha testing
conditions
test planning Tasks
incident report identifier
10. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
environmental needs
cause-effect graphic testing
incident report identifier
11. Calculates the number of executed branch outcomes in code.
input specifications
multiple condition coverage
decision coverage
interoperability
12. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
impact analysis
test analysis & design tasks
failure
multiple condition coverage
13. Components are combined and tested in the order in which basic functionalities start working
waterfall model phases
inspection
functional incremental integration
beta testing
14. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
testing process phases
interoperability testing
system testing
15. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
contract acceptance testing
alpha testing
code coverage
documentation tools
16. Events that occurred during the testing process our investigation.
integration management tools
Incidents
functional requirements
test levels
17. A technique used to improve testing coverage by deliberately introducing faults in code.
environmental needs
fault attack
incident report identifier
condition coverage
18. Operational testing performed at an _external_ site without involvement of the developing organization.
incident description subheadings
system testing
beta testing
efficiency
19. Tools used to store and manage incidents return phone defects failures or anomalies.
waterfall model phases
incident management tools
independence of testing
test data preparation tools
20. Response of the application to an input
input specifications
instrumentation
inspection
action
21. Actual inputs required to execute a test case
IEEE test case specification template
test management tool features
input specifications
conditions
22. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
environmental needs
maintenance testing
input specifications
multiple condition coverage
23. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
LCSAJ testing
error
test execution tasks
24. Testing performed to determine whether the system meets acceptance criteria
documentation tools
acceptance testing
test levels
IEEE test case specification template
25. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
acceptance testing
failure
test log uses
26. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
Impact subheadings
resolution types
equivalence partitions
LCSAJ testing
27. 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
test implementation tasks
failure
component testing
28. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
decision coverage
documentation tools
failure
entry criteria
29. Ability of software to provide appropriate performance relative to amount of resources used.
interoperability testing
efficiency
debugging tools
component integration testing
30. Find defects in code while the software application being tested is running.
stub
test tool deployment Success Factors
failure
dynamic analysis tools
31. All possible combinations of input values and preconditions are tested.
test management tool features
test execution tasks
exhaustive testing
documentation tools
32. Allows storage of test input and expected results in one or more central data sources or databases.
stub
functional requirements
keyword-driven testing
data-driven testing
33. Special-purpose software used to simulate a component called by the component under test
test execution tasks
stub
resolution types
beta testing
34. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
equivalence partitions
horizontal traceability
test data preparation tools
boundary value analysis
35. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
component testing
waterfall model benefits
impact
36. Informal testing technique in which test planning and execution run in parallel
exploratory testing
SW development model
decision testing
inspection
37. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
error guessing
impact analysis
horizontal traceability
bottom-up integration
38. Record details of test cases executed Record order of execution record results
resolution types
alpha testing
test log uses
action
39. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
anomalous events
functional incremental integration
test management tool features
condition coverage
40. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
nonfunctional requirements
inspection
test analysis & design tasks
test control Tasks
41. 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
dynamic analysis tools
cyclomatic complexity
automation tools
42. The ratio between the number of defects found and the size of the component/system tested.
maintainability testing
defect density
input specifications
load testing
43. Tests interfaces between components and between integrated components and systems.
contract acceptance testing
component testing
integration testing
data-driven testing
44. Increased load (transations) used to test behavior of system under high volume.
load testing
component testing
test levels
big-bang testing
45. A document that records the description of each event that occurs during the testing process and that requires further investigation
control flow structure
ad hoc integration
component integration testing
incident report
46. Specific groups that represent a set of valid or invalid partitions for input conditions.
functional incremental integration
accuracy
equivalence partitions
debugging
47. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
system testing
coverage measurement tools
test levels
error guessing
48. A table showing combinations of inputs and their associated actions.
functionality
environmental needs
debugging
decision table
49. A task of maintaining and controlling changes to all entities of a system.
configuration management
incident description subheadings
test condition
functional testing
50. An analysis that determines the portion of code on software executed by a set of test cases
exhaustive testing
data-driven testing
code coverage
functional requirements