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. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
alpha testing
error guessing
fault attack
contract acceptance testing
2. Increased load (transations) used to test behavior of system under high volume.
incident report
coverage
load testing
component
3. The smallest software item that can be tested in isolation.
coverage measurement tools
input specifications
component
test analysis & design tasks
4. Based on analysis of functional specifications of a system.
cyclomatic complexity
test condition
functional testing
defect density
5. Linear Code Sequence and Jump.
test tool deployment Success Factors
LCSAJ
ad hoc integration
cyclomatic complexity
6. An analysis that determines the portion of code on software executed by a set of test cases
waterfall model phases
impact
code coverage
debugging
7. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
incremental testing
experience-based techniques
LCSAJ testing
8. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
action
interoperability testing
ad hoc integration
cause-effect graphic testing
9. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
cause-effect graphic testing
Three main SW development models
waterfall model benefits
exit criteria
10. Process used to create a SW product from initial conception to public release
SW development model
debugging
IEEE test case specification template
decision table testing
11. Testing software in its operational environment
operational testing
input specifications
alpha testing
integration
12. 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.
driver
error guessing
bottom-up integration
component integration testing
13. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
functionality
decision coverage
business process-based testing
14. Combining components or sytems into larger structural units or subsystems.
cyclomatic complexity
load testing
integration
test implementation tasks
15. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
fault attack
monitor
iterative-incremental development models
nonfunctional requirements
16. Find defects in code while the software application being tested is running.
dynamic analysis tools
cyclomatic complexity
exhaustive testing
test log uses
17. 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
functional incremental integration
test data preparation tools
exhaustive testing
incident description subheadings
18. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
alpha testing
automation tools
equivalence partitions
driver
19. Testing an integrated system to validate it meets requirements
decision coverage
system testing
component testing
independence of testing
20. Occurrences that happen before and after an unexpected event
IEEE test case specification template
alpha testing
anomalous events
test condition
21. Used to test the functionality of software as mentioned in software requirement specifications.
action
environmental needs
data flow structure
functional testing tool
22. All possible combinations of input values and preconditions are tested.
exhaustive testing
functionality
impact analysis
iterative-incremental development models
23. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
test control Tasks
error
configuration management
decision testing
24. Tools used to identify and calculate coverage items in program code.
monitor
cause-effect graphic testing
coverage measurement tools
coverage
25. Ability of software to provide appropriate performance relative to amount of resources used.
impact analysis
efficiency
cyclomatic complexity
exploratory testing
26. Events that occurred during the testing process our investigation.
informal review
accuracy
Incidents
SW development model
27. Sequence in which data items are accessed or modified by code.
decision coverage
integration management tools
data flow structure
system testing
28. Allows storage of test input and expected results in one or more central data sources or databases.
data-driven testing
black-box testing
test implementation tasks
functional testing
29. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
functionality
decision testing
risk-based testing
30. Components are combined and tested in the order in which basic functionalities start working
defect
test planning Tasks
black-box testing
functional incremental integration
31. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
integration
incident description subheadings
condition coverage
resolution types
32. Examine changes made to an operational system cause defects.
impact analysis
data-driven testing
bottom-up integration
maintenance testing
33. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
contract acceptance testing
test execution tasks
accuracy
test implementation tasks
34. Input or combination of inputs required to test software.
incident life cycle phases
conditions
risk-based testing
test log uses
35. Tests interfaces between components and between integrated components and systems.
acceptance criteria
integration testing
integration management tools
configuration management tools
36. Components are integrated in the order in which they are developed
ad hoc integration
environmental needs
integration
error guessing
37. An event or item that can be tested using one or more test cases
test condition
functional testing
dynamic analysis tools
test analysis & design tasks
38. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
black-box testing
test condition
testing process phases
system testing
39. Informal testing technique in which test planning and execution run in parallel
action
exploratory testing
instrumentation
functional testing
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
test control Tasks
debugging
load testing
conditions
41. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
failure rate
multiple condition coverage
testing process phases
incident management tools
42. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
risk-based testing
interoperability testing
inspection
black-box testing
43. A task of maintaining and controlling changes to all entities of a system.
inspection
coverage measurement tools
load testing
configuration management
44. Severity - Priority
error
Impact subheadings
functionality
decision coverage
45. A table showing combinations of inputs and their associated actions.
debugging tools
system testing
decision table
test execution tasks
46. Used to replace a component that calls another component.
driver
cyclomatic complexity
fault attack
equivalence partitioning
47. Software products or applications designed to automate manual testing tasks.
operational testing
integration management tools
test analysis & design tasks
automation tools
48. 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.
impact analysis
inspection
decision table
maintenance testing
49. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
instrumentation
functional incremental integration
coverage
horizontal traceability
50. Record details of test cases executed Record order of execution record results
operational testing
resolution types
functional testing tool
test log uses