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. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
contract acceptance testing
input specifications
functional testing
entry criteria
2. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
backbone integration
code coverage
test execution tasks
3. Increased load (transations) used to test behavior of system under high volume.
load testing
LCSAJ testing
test tool deployment Success Factors
test log uses
4. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
data-driven testing
interoperability
LCSAJ
5. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
defect
LCSAJ testing
IEEE incident report template
iterative-incremental development models
6. Black-box testing technique used to create groups of input conditions that create the same kind of output.
test log uses
equivalence partitioning
documentation tools
alpha testing
7. White-box design technique used to design test cases for a software component using LCSAJ.
actual result
Three main SW development models
LCSAJ testing
acceptance testing
8. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
conditions
maintainability testing
actual result
big-bang testing
9. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
exploratory testing
risk-based testing
maintenance testing
10. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
incident description subheadings
COTS
acceptance criteria
11. Find defects in code while the software application being tested is running.
dynamic analysis tools
documentation tools
beta testing
risk-based testing
12. Calculates the number of executed branch outcomes in code.
test execution tasks
defect density
decision coverage
efficiency
13. Incident Report - Identifier - Summary - Incident - Description - Impact
debugging
IEEE incident report template
SW development model
functionality
14. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
test management tool features
resolution types
error guessing
anomalous events
15. Develop & proiroitize test cases Create groups of test cases Set up test environment
test implementation tasks
big-bang testing
horizontal traceability
failure
16. One defect prevents the detection of another.
defect masking
interoperability
integration
incremental testing
17. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
component integration testing
debugging tools
decision testing
maintainability
18. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
functional testing tool
IEEE test case specification template
incident description subheadings
resolution types
19. Waterfall iterative-incremental "V"
exhaustive testing
component
test implementation tasks
Three main SW development models
20. 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.
functional requirements
inspection
cyclomatic complexity
acceptance testing
21. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
acceptance testing
experience-based techniques
COTS
interoperability
22. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
cause-effect graphic testing
maintenance testing
waterfall model benefits
test analysis & design tasks
23. A unique identifier for each incident report generated during test execution.
defect
coverage measurement tools
waterfall model benefits
incident report identifier
24. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
black-box testing
environmental needs
conformance testing tools
incident report
25. Informal testing technique in which test planning and execution run in parallel
acceptance criteria
exploratory testing
waterfall model phases
Impact subheadings
26. A document that records the description of each event that occurs during the testing process and that requires further investigation
equivalence partitioning
driver
incident report
environmental needs
27. Tests interfaces between components and between integrated components and systems.
integration testing
system testing
load testing
coverage measurement tools
28. Deviation of a software system from its expected delivery services or results
informal review
input specifications
failure
independence of testing
29. Testing performed to determine whether the system meets acceptance criteria
exhaustive testing
big-bang testing
IEEE test case specification template
acceptance testing
30. Tools used to store and manage incidents return phone defects failures or anomalies.
incident description subheadings
nonfunctional requirements
incident management tools
bottom-up integration
31. Based on analysis of functional specifications of a system.
control flow structure
functional testing
test log uses
horizontal traceability
32. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
driver
environmental needs
system testing
condition determination coverage
33. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
actual result
condition determination coverage
functionality
dynamic analysis tools
34. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
component integration testing
defect
incident life cycle phases
conformance testing tools
35. 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
waterfall model benefits
LCSAJ
monitor
Three main SW development models
36. Allows storage of test input and expected results in one or more central data sources or databases.
environmental needs
data-driven testing
agile software development model
data flow structure
37. The smallest software item that can be tested in isolation.
decision table testing
component
nonfunctional requirements
backbone integration
38. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
risk-based testing
test analysis & design tasks
big-bang testing
ad hoc integration
39. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
integration testing
integration
code coverage
40. The process of finding analyzing and removing causes of failure in a software product.
maintainability testing
debugging
incident life cycle phases
system testing
41. A component of the incident report that determines the actual effect of the incident on the software and its users.
test tool deployment Success Factors
impact
business process-based testing
resolution types
42. 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
debugging
test implementation tasks
test levels
43. Black-box test design technique - test cases are designed from a decision table.
decision table testing
defect density
LCSAJ testing
beta testing
44. Software products or applications designed to automate manual testing tasks.
impact analysis
automation tools
IEEE test case specification template
decision table
45. Integration approach components or subsystems are combined all at once rather than in stages.
risk-based testing
coverage measurement tools
big-bang testing
component
46. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
accuracy
alpha testing
test log uses
test levels
47. Linear Code Sequence and Jump.
test data preparation tools
LCSAJ
actual result
COTS
48. 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
exhaustive testing
agile software development model
IEEE incident report template
keyword-driven testing
49. Events that occurred during the testing process our investigation.
Incidents
LCSAJ testing
equivalence partitions
defect
50. 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
inspection
bottom-up integration
automation tools