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. Find defects in code while the software application being tested is running.
driver
functional testing
dynamic analysis tools
conditions
2. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
IEEE incident report template
nonfunctional requirements
SW development model
driver
3. Behavior or response of a software application that you observe when you execute the action steps in the test case.
IEEE incident report template
independence of testing
test execution tasks
actual result
4. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
inspection
maintainability
impact analysis
incremental testing
5. 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
beta testing
load testing
functional incremental integration
waterfall model benefits
6. Requirements that determine the functionality of a software system.
risk-based testing
business process-based testing
driver
functional requirements
7. A set of conditions that a system needs to meet in order to be accepted by end users
horizontal traceability
code coverage
nonfunctional requirements
acceptance criteria
8. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
SW development model
incident life cycle phases
condition coverage
functional requirements
9. Testing software in its operational environment
operational testing
configuration management
Incidents
condition coverage
10. Ability of software to provide appropriate performance relative to amount of resources used.
alpha testing
efficiency
coverage measurement tools
documentation tools
11. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
input specifications
functional testing tool
defect density
testing process phases
12. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
data-driven testing
interoperability
error
maintainability testing
13. Severity - Priority
efficiency
Impact subheadings
incident life cycle phases
control flow structure
14. 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
cause-effect graphic testing
SW development model
test tool deployment Success Factors
LCSAJ testing
15. The smallest software item that can be tested in isolation.
beta testing
multiple condition coverage
IEEE test case specification template
component
16. 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
waterfall model phases
operational testing
backbone integration
test data preparation tools
17. A table showing combinations of inputs and their associated actions.
LCSAJ testing
business process-based testing
decision table
impact analysis
18. Special additions or changes to the environment required to run a test case.
equivalence partitions
stub
test condition
environmental needs
19. Black-box test design technique - test cases are designed from a decision table.
big-bang testing
control flow structure
decision table testing
stub
20. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
condition coverage
functional testing
interoperability
test log uses
21. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
risk-based testing
documentation tools
incident description subheadings
functional incremental integration
22. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
functional testing
incremental testing
monitor
incident report
23. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
integration
functional testing tool
independence of testing
contract acceptance testing
24. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
IEEE incident report template
debugging
accuracy
25. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
integration testing
error
functional testing tool
component integration testing
26. Based on analysis of functional specifications of a system.
documentation tools
functional testing
input specifications
conformance testing tools
27. Black-box testing technique used to create groups of input conditions that create the same kind of output.
nonfunctional requirements
keyword-driven testing
equivalence partitioning
decision table
28. A task of maintaining and controlling changes to all entities of a system.
decision table testing
conformance testing tools
configuration management
exhaustive testing
29. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
condition coverage
incident life cycle phases
fault attack
incremental testing
30. Incident Report - Identifier - Summary - Incident - Description - Impact
load testing
control flow structure
IEEE incident report template
LCSAJ
31. Tools used to store and manage incidents return phone defects failures or anomalies.
incident management tools
debugging tools
experience-based techniques
incident report
32. Sequence in which instructions are executed through a component or system
decision table testing
control flow structure
failure rate
exit criteria
33. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
automation tools
keyword-driven testing
debugging tools
34. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
black-box testing
monitor
incident life cycle phases
decision testing
35. Sequence in which data items are accessed or modified by code.
incident description subheadings
data flow structure
conditions
bottom-up integration
36. Components are combined and tested in the order in which basic functionalities start working
waterfall model phases
iterative-incremental development models
functional incremental integration
integration management tools
37. Integration approach components or subsystems are combined all at once rather than in stages.
decision testing
business process-based testing
maintainability testing
big-bang testing
38. Software products or applications designed to automate manual testing tasks.
beta testing
maintainability
IEEE incident report template
automation tools
39. Testing software components that are separately testable. Also module program and unit testing.
cause-effect graphic testing
test log uses
component testing
test implementation tasks
40. Measures amount of testing performed by a collection of test cases
interoperability
functional testing
coverage
error
41. The capability of a software product to provide agreed and correct output with the required degree of precision
stub
configuration management tools
accuracy
COTS
42. Input or combination of inputs required to test software.
condition coverage
big-bang testing
conditions
instrumentation
43. An event or item that can be tested using one or more test cases
incident description subheadings
test condition
boundary value analysis
impact
44. Tools used by developers to identify defects in programs.
stub
waterfall model phases
incremental testing
debugging tools
45. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
IEEE incident report template
error
actual result
46. Human action that generates an incorrect result.
Three main SW development models
error
component testing
debugging
47. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
equivalence partitions
backbone integration
horizontal traceability
fault attack
48. Linear Code Sequence and Jump.
exhaustive testing
test analysis & design tasks
LCSAJ
equivalence partitioning
49. Combining components or sytems into larger structural units or subsystems.
horizontal traceability
functional requirements
integration
bottom-up integration
50. The process of finding analyzing and removing causes of failure in a software product.
debugging
test data preparation tools
functional testing tool
anomalous events