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. Waterfall iterative-incremental "V"
code coverage
Three main SW development models
Impact subheadings
decision table
2. Tests interfaces between components and between integrated components and systems.
integration testing
environmental needs
failure
configuration management tools
3. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
debugging
test analysis & design tasks
nonfunctional requirements
IEEE test case specification template
4. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
resolution types
documentation tools
data-driven testing
contract acceptance testing
5. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
integration
impact analysis
conformance testing tools
incident report
6. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
configuration management
beta testing
nonfunctional requirements
7. Sequence in which instructions are executed through a component or system
nonfunctional requirements
control flow structure
testing process phases
failure
8. Black-box testing technique used to create groups of input conditions that create the same kind of output.
monitor
equivalence partitioning
test condition
LCSAJ
9. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
Impact subheadings
inspection
test management tool features
maintenance testing
10. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
LCSAJ
maintainability testing
control flow structure
waterfall model benefits
11. Specific groups that represent a set of valid or invalid partitions for input conditions.
driver
experience-based techniques
equivalence partitions
agile software development model
12. The capability of a software product to provide agreed and correct output with the required degree of precision
defect density
integration
accuracy
LCSAJ testing
13. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incremental testing
defect masking
incident life cycle phases
configuration management tools
14. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
keyword-driven testing
incident life cycle phases
test analysis & design tasks
incident management tools
15. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
environmental needs
equivalence partitioning
test execution tasks
debugging
16. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
black-box testing
automation tools
functional requirements
17. Component - Integration - System - Acceptance
maintainability
interoperability
monitor
test levels
18. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
driver
actual result
integration management tools
interoperability testing
19. A unique identifier for each incident report generated during test execution.
cause-effect graphic testing
incident report identifier
instrumentation
efficiency
20. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
test log uses
COTS
decision table testing
driver
21. A component of the incident report that determines the actual effect of the incident on the software and its users.
contract acceptance testing
boundary value analysis
impact
control flow structure
22. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
test management tool features
business process-based testing
exhaustive testing
23. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
driver
data flow structure
horizontal traceability
incident report identifier
24. A document that records the description of each event that occurs during the testing process and that requires further investigation
Three main SW development models
decision testing
Impact subheadings
incident report
25. Tools used to identify and calculate coverage items in program code.
COTS
beta testing
coverage measurement tools
business process-based testing
26. Informal testing technique in which test planning and execution run in parallel
exploratory testing
interoperability testing
debugging
equivalence partitions
27. The smallest software item that can be tested in isolation.
inspection
component
decision coverage
driver
28. Increased load (transations) used to test behavior of system under high volume.
data flow structure
test tool deployment Success Factors
load testing
LCSAJ testing
29. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
test condition
code coverage
interoperability
functional testing tool
30. 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 log uses
horizontal traceability
configuration management
31. Conditions required to begin testing activities.
conditions
test levels
defect density
entry criteria
32. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
alpha testing
incident report
acceptance testing
stub
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
configuration management
agile software development model
test data preparation tools
incident life cycle phases
34. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
error guessing
incremental testing
defect density
stub
35. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
exit criteria
component testing
component
waterfall model phases
36. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
conformance testing tools
cyclomatic complexity
waterfall model phases
test control Tasks
37. Tools used by developers to identify defects in programs.
test implementation tasks
automation tools
debugging tools
impact analysis
38. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
exploratory testing
monitor
entry criteria
39. Process used to create a SW product from initial conception to public release
testing process phases
driver
SW development model
informal review
40. Deviation of a software system from its expected delivery services or results
failure
acceptance testing
Incidents
functional incremental integration
41. Testing software in its operational environment
operational testing
coverage measurement tools
independence of testing
alpha testing
42. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
test management tool features
functionality
conformance testing tools
integration testing
43. Components are integrated in the order in which they are developed
ad hoc integration
SW development model
error guessing
incident report
44. Events that occurred during the testing process our investigation.
maintenance testing
Incidents
test planning Tasks
black-box testing
45. White-box design technique used to design test cases for a software component using LCSAJ.
incident report identifier
input specifications
functional testing
LCSAJ testing
46. Integrate different kinds of tools to make test management more efficient and simple.
experience-based techniques
integration management tools
interoperability testing
keyword-driven testing
47. Find defects in code while the software application being tested is running.
dynamic analysis tools
error
black-box testing
incident description subheadings
48. A functional testing approach in which test cases are designed based on business processes.
coverage
business process-based testing
impact
SW development model
49. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
dynamic analysis tools
test levels
LCSAJ
defect
50. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
test management tool features
test data preparation tools
condition coverage