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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
Impact subheadings
condition coverage
decision table
2. A unique identifier for each incident report generated during test execution.
business process-based testing
load testing
automation tools
incident report identifier
3. Used to test the functionality of software as mentioned in software requirement specifications.
interoperability testing
Impact subheadings
functional testing tool
backbone integration
4. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
component
nonfunctional requirements
decision coverage
horizontal traceability
5. Software products or applications designed to automate manual testing tasks.
incident life cycle phases
agile software development model
automation tools
functional incremental integration
6. Black-box testing technique used to create groups of input conditions that create the same kind of output.
backbone integration
incident report
test planning Tasks
equivalence partitioning
7. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
functional incremental integration
documentation tools
component integration testing
interoperability
8. Tools used by developers to identify defects in programs.
incident description subheadings
SW development model
debugging tools
interoperability
9. Tools used to identify and calculate coverage items in program code.
risk-based testing
debugging
coverage measurement tools
test control Tasks
10. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
conformance testing tools
error guessing
maintainability testing
11. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
test levels
functionality
efficiency
incident report
12. A functional testing approach in which test cases are designed based on business processes.
business process-based testing
iterative-incremental development models
horizontal traceability
maintainability testing
13. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
cyclomatic complexity
IEEE test case specification template
conformance testing tools
14. Increased load (transations) used to test behavior of system under high volume.
test data preparation tools
maintenance testing
load testing
incident management tools
15. Examine changes made to an operational system cause defects.
maintenance testing
bottom-up integration
testing process phases
big-bang testing
16. Separation of testing responsibilities which encourages the accomplishment of objective testing
error
independence of testing
test analysis & design tasks
Three main SW development models
17. Allows storage of test input and expected results in one or more central data sources or databases.
data-driven testing
coverage
informal review
Incidents
18. Specific groups that represent a set of valid or invalid partitions for input conditions.
integration management tools
failure
equivalence partitions
automation tools
19. Severity - Priority
maintenance testing
incident report
Impact subheadings
driver
20. The capability of a software product to provide agreed and correct output with the required degree of precision
interoperability testing
load testing
test data preparation tools
accuracy
21. Testing an integrated system to validate it meets requirements
system testing
code coverage
integration testing
stub
22. Record details of test cases executed Record order of execution record results
test log uses
anomalous events
efficiency
nonfunctional requirements
23. 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.
test tool deployment Success Factors
component testing
bottom-up integration
failure rate
24. Linear Code Sequence and Jump.
LCSAJ
business process-based testing
boundary value analysis
testing process phases
25. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
failure
test control Tasks
equivalence partitions
test analysis & design tasks
26. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
test execution tasks
environmental needs
interoperability testing
27. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
SW development model
LCSAJ testing
incremental testing
anomalous events
28. Deviation of a software system from its expected delivery services or results
test data preparation tools
maintainability
failure
acceptance criteria
29. Response of the application to an input
business process-based testing
exit criteria
action
component
30. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
incident description subheadings
contract acceptance testing
component testing
31. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
acceptance testing
fault attack
load testing
32. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
test implementation tasks
keyword-driven testing
integration management tools
Impact subheadings
33. 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
driver
agile software development model
incident management tools
equivalence partitions
34. Integration approach components or subsystems are combined all at once rather than in stages.
component testing
efficiency
functionality
big-bang testing
35. 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 planning Tasks
actual result
environmental needs
error guessing
36. Find defects in code while the software application being tested is running.
business process-based testing
equivalence partitions
dynamic analysis tools
test control Tasks
37. Components are integrated in the order in which they are developed
ad hoc integration
integration testing
waterfall model phases
alpha testing
38. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
instrumentation
resolution types
driver
39. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
component integration testing
condition determination coverage
keyword-driven testing
incident report
40. The ratio between the number of defects found and the size of the component/system tested.
LCSAJ
defect density
error
failure rate
41. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
monitor
conformance testing tools
fault attack
maintainability testing
42. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
decision table testing
test planning Tasks
incident life cycle phases
business process-based testing
43. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
configuration management tools
horizontal traceability
anomalous events
44. Waterfall iterative-incremental "V"
test levels
functional testing tool
Three main SW development models
acceptance criteria
45. Operational testing performed at an _external_ site without involvement of the developing organization.
functional testing tool
horizontal traceability
beta testing
test management tool features
46. Informal testing technique in which test planning and execution run in parallel
exploratory testing
risk-based testing
impact
functional incremental integration
47. Events that occurred during the testing process our investigation.
driver
Incidents
independence of testing
test analysis & design tasks
48. 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
IEEE test case specification template
alpha testing
acceptance criteria
49. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
control flow structure
iterative-incremental development models
test log uses
test tool deployment Success Factors
50. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
failure rate
nonfunctional requirements
functionality
failure