Latest Update
why testing is necessary testing is a form of quality control that helps achieve the agreed
upon test objectives within the set scope, time, quality, and budget constraints. Testing's
contribution to the success of a project should not be limited to the test team's activities, but
rather any stakeholder should use their testing skills to bring the product closer to success.
testing provides a cost-effective means of detecting defects. These defects can then be
removed (by debugging - a non-testing activity), so testing indirectly contributes to higher
quality testing objects
recall the relation between testing and quality assurance While one is a product oriented,
corrective approach that focuses on those activities supporting the achievement of appropriate
levels of quality, and is a major form of quality control, while other forms include formal
methods (model checking and proof of correctness), simulation and prototyping.
The other is a process-oriented, preventative approach that focuses on the implementation and
improvement of processes. It works on a basis that if a good process is followed correctly, then
it will generate a good product. QA applies to both the development and testing processes, and
is the responsibility of everyone on a project.
Test results are used both by testing and QA, in testing, the results are used to fix defects, while
in QA they provide feedback on how well the development and test processes are performing.
distinguish between root cause, error, defect, and failure humans make errors which
produce defects (faults, bugs), which in turn may result in failures. Errors are defects but are
not the only cause of failures. A root cause is a fundamental reason for the occurrence of a
problem. Root causes are identified through root cause analysis, which is typically performed
when a failure occurs or a defect is identified.
explain the different test activities and related tasks Test monitoring and test control -
monitoring includes ongoing checking of test activities and comparison to plan. Control involves
taking the actions necessary to meet the test objectives.
, Test analysis - analyzing the test basis to identify testable features, associated test conditions
are defined and prioritized, taking the related risks and risk levels into account. Test basis and
test object are also evaluated to identify any defects they may contain and to assess their
testability.
Test Design - elaborating test conditions into test cases and other testware. Often involves
identification of coverage items, which serve as a guide to specify test inputs. Also includes
defining the test data requirements, designing the test environment and identifying the
necessary infrastructure and tools.
Test Implementation - creating or acquiring testware necessary for test execution. Organize test
cases into test procedures, often assembled into test suites. Manual and automated test scripts
are created.
Test execution - includes running tests in accordance with the test execution schedule. May be
manual or automated. Actual test results are compared with expected test results.
Test Completion - usually occurs at project milestones. For any unresolved defects, change
requests or product backlog items are created. Any useful testware is archived. Test
environment is shutdown to an agreeable state.
explain the impact of context on the test process Stakeholders (needs, expectations,
requirements, willingness to cooperate)
Team members (skills ,knowledge, level of experience, availability, training needs, etc.)
Business Domain (criticality of the test object, identified risks, market needs, legal regulations,
etc.)
Technical factors (type of software, product architecture, technology used, etc.)