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
integration
test management tool features
acceptance criteria
maintainability testing
2. An event or item that can be tested using one or more test cases
integration testing
test levels
decision coverage
test condition
3. Testing performed to determine whether the system meets acceptance criteria
error guessing
black-box testing
acceptance testing
error
4. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
backbone integration
functional testing
beta testing
5. Components are integrated in the order in which they are developed
coverage
ad hoc integration
error
Three main SW development models
6. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
automation tools
impact analysis
defect masking
7. Combining components or sytems into larger structural units or subsystems.
test data preparation tools
integration
COTS
defect density
8. A table showing combinations of inputs and their associated actions.
waterfall model phases
configuration management
decision table
horizontal traceability
9. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
environmental needs
iterative-incremental development models
fault attack
stub
10. 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.
decision table testing
iterative-incremental development models
business process-based testing
bottom-up integration
11. The capability of a software product to provide agreed and correct output with the required degree of precision
functional testing
decision testing
driver
accuracy
12. Deviation of a software system from its expected delivery services or results
failure
impact
independence of testing
integration management tools
13. Used to replace a component that calls another component.
horizontal traceability
beta testing
entry criteria
driver
14. A review not based on a formal documented procedure
data-driven testing
big-bang testing
control flow structure
informal review
15. Conditions required to begin testing activities.
Impact subheadings
integration
entry criteria
documentation tools
16. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
entry criteria
IEEE incident report template
coverage measurement tools
documentation tools
17. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
exit criteria
entry criteria
impact analysis
component
18. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
maintenance testing
defect
decision testing
cyclomatic complexity
19. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ
interoperability
acceptance criteria
LCSAJ testing
20. Sequence in which data items are accessed or modified by code.
experience-based techniques
iterative-incremental development models
acceptance testing
data flow structure
21. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
LCSAJ
functionality
interoperability
maintainability testing
22. Informal testing technique in which test planning and execution run in parallel
environmental needs
exploratory testing
Three main SW development models
multiple condition coverage
23. Testing software components that are separately testable. Also module program and unit testing.
component testing
condition coverage
documentation tools
monitor
24. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect
test data preparation tools
experience-based techniques
functionality
25. 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
monitor
incident report identifier
testing process phases
26. A technique used to improve testing coverage by deliberately introducing faults in code.
decision coverage
actual result
waterfall model benefits
fault attack
27. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
coverage measurement tools
multiple condition coverage
failure rate
keyword-driven testing
28. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
iterative-incremental development models
exit criteria
documentation tools
functional requirements
29. 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
impact analysis
test data preparation tools
test execution tasks
30. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
COTS
dynamic analysis tools
fault attack
alpha testing
31. Response of the application to an input
failure rate
action
fault attack
impact
32. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
system testing
integration management tools
functional requirements
33. Waterfall iterative-incremental "V"
interoperability
Three main SW development models
conformance testing tools
integration
34. A task of maintaining and controlling changes to all entities of a system.
incident report identifier
configuration management
condition coverage
functional requirements
35. Tests interfaces between components and between integrated components and systems.
code coverage
actual result
integration testing
dynamic analysis tools
36. 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
operational testing
alpha testing
LCSAJ
37. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
coverage
test execution tasks
IEEE test case specification template
conformance testing tools
38. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
conformance testing tools
horizontal traceability
incremental testing
testing process phases
39. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
input specifications
waterfall model phases
fault attack
bottom-up integration
40. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
IEEE test case specification template
decision testing
incremental testing
risk-based testing
41. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
contract acceptance testing
agile software development model
configuration management tools
experience-based techniques
42. Events that occurred during the testing process our investigation.
condition coverage
automation tools
conditions
Incidents
43. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
test execution tasks
defect
error guessing
action
44. Black-box test design technique - test cases are designed from a decision table.
component testing
defect
Incidents
decision table testing
45. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
cyclomatic complexity
alpha testing
code coverage
multiple condition coverage
46. The smallest software item that can be tested in isolation.
component
waterfall model phases
test log uses
load testing
47. Integrate different kinds of tools to make test management more efficient and simple.
nonfunctional requirements
integration management tools
debugging tools
test analysis & design tasks
48. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
interoperability testing
test management tool features
input specifications
independence of testing
49. Testing software in its operational environment
integration
black-box testing
driver
operational testing
50. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
fault attack
conditions
test log uses