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. Requirements that determine the functionality of a software system.
functional requirements
incident life cycle phases
test control Tasks
test execution tasks
2. Actual inputs required to execute a test case
Impact subheadings
component
SW development model
input specifications
3. A set of conditions that a system needs to meet in order to be accepted by end users
big-bang testing
fault attack
acceptance criteria
LCSAJ testing
4. Tests interfaces between components and between integrated components and systems.
resolution types
integration testing
black-box testing
incremental testing
5. Waterfall iterative-incremental "V"
test condition
functionality
resolution types
Three main SW development models
6. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect
defect masking
condition determination coverage
multiple condition coverage
7. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
COTS
incident report identifier
keyword-driven testing
actual result
8. Special additions or changes to the environment required to run a test case.
environmental needs
load testing
contract acceptance testing
component testing
9. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
accuracy
data flow structure
incident life cycle phases
test analysis & design tasks
10. 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
exploratory testing
maintenance testing
acceptance testing
11. Linear Code Sequence and Jump.
defect
LCSAJ
data flow structure
Incidents
12. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
decision table
control flow structure
functionality
13. 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.
inspection
ad hoc integration
nonfunctional requirements
Impact subheadings
14. Black-box test design technique - test cases are designed from a decision table.
coverage measurement tools
maintainability
Incidents
decision table testing
15. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
system testing
functional requirements
backbone integration
16. Input or combination of inputs required to test software.
automation tools
independence of testing
configuration management
conditions
17. 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
maintenance testing
stub
integration management tools
test planning Tasks
18. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
alpha testing
acceptance testing
cyclomatic complexity
impact
19. Events that occurred during the testing process our investigation.
operational testing
defect
Incidents
test levels
20. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
instrumentation
big-bang testing
test levels
testing process phases
21. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
incident management tools
test control Tasks
multiple condition coverage
testing process phases
22. Process used to create a SW product from initial conception to public release
environmental needs
risk-based testing
SW development model
incident management tools
23. Testing an integrated system to validate it meets requirements
defect masking
system testing
data flow structure
Impact subheadings
24. 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
test data preparation tools
decision table testing
defect
dynamic analysis tools
25. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
load testing
error guessing
iterative-incremental development models
horizontal traceability
26. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
instrumentation
test tool deployment Success Factors
interoperability testing
data flow structure
27. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
interoperability
keyword-driven testing
failure
big-bang testing
28. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
bottom-up integration
functionality
Impact subheadings
nonfunctional requirements
29. A document that provides the structure for writing test cases.
impact analysis
defect masking
backbone integration
IEEE test case specification template
30. Components are integrated in the order in which they are developed
code coverage
control flow structure
entry criteria
ad hoc integration
31. Integration approach components or subsystems are combined all at once rather than in stages.
resolution types
big-bang testing
IEEE test case specification template
black-box testing
32. Conditions required to begin testing activities.
entry criteria
code coverage
interoperability testing
Impact subheadings
33. A component of the incident report that determines the actual effect of the incident on the software and its users.
input specifications
entry criteria
multiple condition coverage
impact
34. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).
control flow structure
configuration management tools
iterative-incremental development models
test levels
35. Record details of test cases executed Record order of execution record results
data flow structure
dynamic analysis tools
stub
test log uses
36. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
condition coverage
test implementation tasks
agile software development model
incident report identifier
37. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
condition coverage
multiple condition coverage
load testing
LCSAJ testing
38. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
IEEE test case specification template
documentation tools
failure
incident life cycle phases
39. Special-purpose software used to simulate a component that calls the component under test
driver
integration
black-box testing
cause-effect graphic testing
40. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
beta testing
functional requirements
load testing
test management tool features
41. Human action that generates an incorrect result.
risk-based testing
interoperability testing
error
accuracy
42. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
conditions
iterative-incremental development models
multiple condition coverage
test levels
43. A review not based on a formal documented procedure
big-bang testing
informal review
test management tool features
LCSAJ testing
44. 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
impact
agile software development model
fault attack
decision table
45. Testing software in its operational environment
test management tool features
incident description subheadings
integration management tools
operational testing
46. Measures amount of testing performed by a collection of test cases
data flow structure
coverage
exhaustive testing
functional testing
47. Based on analysis of functional specifications of a system.
functional testing
debugging tools
operational testing
test implementation tasks
48. A document that records the description of each event that occurs during the testing process and that requires further investigation
instrumentation
incident report
big-bang testing
error guessing
49. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
independence of testing
exhaustive testing
integration testing
experience-based techniques
50. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
business process-based testing
informal review
risk-based testing
alpha testing