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. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
acceptance testing
exhaustive testing
IEEE incident report template
2. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
testing process phases
maintainability testing
conformance testing tools
contract acceptance testing
3. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
dynamic analysis tools
impact
test data preparation tools
alpha testing
4. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
accuracy
decision coverage
interoperability
5. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
conformance testing tools
component integration testing
decision table
resolution types
6. Tools used by developers to identify defects in programs.
acceptance criteria
informal review
debugging tools
boundary value analysis
7. A document that provides the structure for writing test cases.
entry criteria
IEEE test case specification template
contract acceptance testing
LCSAJ testing
8. A functional testing approach in which test cases are designed based on business processes.
efficiency
IEEE test case specification template
business process-based testing
cyclomatic complexity
9. Incident Report - Identifier - Summary - Incident - Description - Impact
conditions
functional testing tool
test condition
IEEE incident report template
10. Special additions or changes to the environment required to run a test case.
instrumentation
error
environmental needs
COTS
11. Human action that generates an incorrect result.
error
monitor
business process-based testing
backbone integration
12. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
configuration management
stub
multiple condition coverage
test implementation tasks
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.
impact analysis
LCSAJ testing
debugging
inspection
14. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
conditions
load testing
coverage measurement tools
15. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
business process-based testing
automation tools
control flow structure
16. Testing software components that are separately testable. Also module program and unit testing.
component testing
driver
test condition
decision table testing
17. 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).
exploratory testing
test analysis & design tasks
cause-effect graphic testing
configuration management tools
18. Based on analysis of functional specifications of a system.
inspection
system testing
functional testing
incident report
19. Measures amount of testing performed by a collection of test cases
configuration management
stub
decision table
coverage
20. Actual inputs required to execute a test case
maintainability
failure rate
input specifications
condition determination coverage
21. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons
test log uses
entry criteria
resolution types
test tool deployment Success Factors
22. Tests interfaces between components and between integrated components and systems.
action
informal review
integration testing
conditions
23. Occurrences that happen before and after an unexpected event
anomalous events
bottom-up integration
test analysis & design tasks
incident life cycle phases
24. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
data-driven testing
maintenance testing
test implementation tasks
cyclomatic complexity
25. Examine changes made to an operational system cause defects.
waterfall model benefits
bottom-up integration
maintenance testing
component integration testing
26. All possible combinations of input values and preconditions are tested.
Impact subheadings
test control Tasks
exhaustive testing
alpha testing
27. Black-box testing technique used to create groups of input conditions that create the same kind of output.
test condition
equivalence partitioning
operational testing
iterative-incremental development models
28. Integrate different kinds of tools to make test management more efficient and simple.
equivalence partitioning
configuration management tools
exhaustive testing
integration management tools
29. The smallest software item that can be tested in isolation.
incident report
impact
interoperability testing
component
30. Waterfall iterative-incremental "V"
beta testing
Three main SW development models
instrumentation
resolution types
31. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
environmental needs
decision table
LCSAJ testing
backbone integration
32. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
incident life cycle phases
coverage measurement tools
horizontal traceability
driver
33. 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
driver
component testing
code coverage
34. Linear Code Sequence and Jump.
incident report
cyclomatic complexity
LCSAJ
beta testing
35. Find defects in code while the software application being tested is running.
impact
debugging
dynamic analysis tools
iterative-incremental development models
36. A review not based on a formal documented procedure
SW development model
informal review
input specifications
monitor
37. 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.
incident description subheadings
Three main SW development models
bottom-up integration
coverage measurement tools
38. 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
nonfunctional requirements
test implementation tasks
functional testing tool
agile software development model
39. A set of conditions that a system needs to meet in order to be accepted by end users
interoperability testing
impact analysis
acceptance criteria
functional requirements
40. Response of the application to an input
iterative-incremental development models
automation tools
action
debugging tools
41. Black-box test design technique - test cases are designed from a decision table.
entry criteria
fault attack
decision table testing
data flow structure
42. Components are combined and tested in the order in which basic functionalities start working
nonfunctional requirements
data-driven testing
functional incremental integration
test tool deployment Success Factors
43. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
condition coverage
cause-effect graphic testing
inspection
agile software development model
44. Operational testing performed at an _external_ site without involvement of the developing organization.
functionality
nonfunctional requirements
beta testing
cyclomatic complexity
45. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
control flow structure
documentation tools
risk-based testing
functionality
46. Used to test the functionality of software as mentioned in software requirement specifications.
incident description subheadings
independence of testing
functional testing tool
equivalence partitioning
47. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
operational testing
inspection
iterative-incremental development models
waterfall model benefits
48. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
Incidents
contract acceptance testing
alpha testing
49. Input or combination of inputs required to test software.
conditions
input specifications
integration
contract acceptance testing
50. Separation of testing responsibilities which encourages the accomplishment of objective testing
exhaustive testing
backbone integration
dynamic analysis tools
independence of testing