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. A set of conditions that a system needs to meet in order to be accepted by end users
error guessing
exploratory testing
acceptance criteria
beta testing
2. A review not based on a formal documented procedure
informal review
business process-based testing
waterfall model benefits
agile software development model
3. An analysis that determines the portion of code on software executed by a set of test cases
conformance testing tools
code coverage
test execution tasks
driver
4. The ratio between the number of defects found and the size of the component/system tested.
driver
defect density
beta testing
impact
5. The capability of a software product to provide agreed and correct output with the required degree of precision
test management tool features
horizontal traceability
alpha testing
accuracy
6. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
black-box testing
system testing
functionality
agile software development model
7. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
driver
component integration testing
cyclomatic complexity
anomalous events
8. Tests interfaces between components and between integrated components and systems.
Incidents
stub
integration testing
incident report identifier
9. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
defect
test management tool features
experience-based techniques
testing process phases
10. Testing an integrated system to validate it meets requirements
equivalence partitions
system testing
actual result
conditions
11. Increased load (transations) used to test behavior of system under high volume.
load testing
test levels
black-box testing
impact
12. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact
waterfall model phases
impact analysis
failure
13. A component of the incident report that determines the actual effect of the incident on the software and its users.
monitor
impact
accuracy
condition determination coverage
14. A functional testing approach in which test cases are designed based on business processes.
impact
informal review
fault attack
business process-based testing
15. Examine changes made to an operational system cause defects.
informal review
business process-based testing
nonfunctional requirements
maintenance testing
16. A document that provides the structure for writing test cases.
IEEE test case specification template
keyword-driven testing
incident description subheadings
integration testing
17. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
inspection
incremental testing
decision testing
data-driven testing
18. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
cyclomatic complexity
contract acceptance testing
incident report
component
19. A unique identifier for each incident report generated during test execution.
failure
incident report identifier
functional testing
boundary value analysis
20. 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.
functional requirements
debugging tools
bottom-up integration
waterfall model phases
21. 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
test tool deployment Success Factors
agile software development model
keyword-driven testing
ad hoc integration
22. Special-purpose software used to simulate a component called by the component under test
stub
big-bang testing
configuration management
decision coverage
23. Used to replace a component that calls another component.
driver
efficiency
informal review
SW development model
24. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
code coverage
incident management tools
resolution types
waterfall model phases
25. 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.
error guessing
exploratory testing
inspection
operational testing
26. Informal testing technique in which test planning and execution run in parallel
system testing
error
exploratory testing
test log uses
27. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
control flow structure
anomalous events
defect
28. Operational testing performed at an _external_ site without involvement of the developing organization.
entry criteria
beta testing
configuration management tools
equivalence partitions
29. Sequence in which instructions are executed through a component or system
informal review
operational testing
IEEE test case specification template
control flow structure
30. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
Impact subheadings
testing process phases
maintainability
test analysis & design tasks
31. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
LCSAJ testing
risk-based testing
operational testing
condition coverage
32. All possible combinations of input values and preconditions are tested.
dynamic analysis tools
defect masking
exhaustive testing
IEEE test case specification template
33. Used to test the functionality of software as mentioned in software requirement specifications.
functional incremental integration
incremental testing
functional testing tool
cause-effect graphic testing
34. Specific groups that represent a set of valid or invalid partitions for input conditions.
boundary value analysis
condition coverage
coverage measurement tools
equivalence partitions
35. Ability of software to provide appropriate performance relative to amount of resources used.
failure
efficiency
IEEE test case specification template
incident report
36. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
automation tools
control flow structure
integration
test management tool features
37. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
functionality
operational testing
test control Tasks
component integration testing
38. Special additions or changes to the environment required to run a test case.
documentation tools
informal review
maintainability testing
environmental needs
39. Human action that generates an incorrect result.
test management tool features
error
iterative-incremental development models
stub
40. Tools used to store and manage incidents return phone defects failures or anomalies.
documentation tools
incident management tools
equivalence partitioning
action
41. An event or item that can be tested using one or more test cases
configuration management tools
test condition
exit criteria
keyword-driven testing
42. Combining components or sytems into larger structural units or subsystems.
maintainability testing
accuracy
test data preparation tools
integration
43. Integration approach components or subsystems are combined all at once rather than in stages.
nonfunctional requirements
defect
big-bang testing
system testing
44. Record details of test cases executed Record order of execution record results
test log uses
defect masking
coverage
resolution types
45. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
debugging tools
exit criteria
SW development model
configuration management tools
46. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
coverage measurement tools
functionality
waterfall model phases
47. 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
condition coverage
boundary value analysis
interoperability
48. The smallest software item that can be tested in isolation.
component
contract acceptance testing
component integration testing
functional testing
49. Occurrences that happen before and after an unexpected event
alpha testing
acceptance criteria
anomalous events
functional testing tool
50. Testing software components that are separately testable. Also module program and unit testing.
driver
component testing
business process-based testing
big-bang testing