Professional Documents
Culture Documents
Reviewer in Reading
Reviewer in Reading
Waterfall Model
Incremental Waterfall Model
Prototyping Model
Spiral Model
The
Project Initiation
Project Planning
Project Execution
Project Closure
phases of Product Life Cycle:
Idea or innovation
Development
Introduction or adaptation
Growth
Maturity
Decline
Introduction to Testing
The goal of testing is to ensure that the business system meets
the established functional and technical requirements.
The different types of software testing are (according to the
Accenture Testing Framework):
Unit testing - Tests individual units of the application.
Assembly testing - sometimes called String test. Ensures
that the interactions between the components function
correctly.
Product testing - sometimes called System test, as it tests
that all business requirements are met by the system.
The Application Product test validates that the
product requirements are met by each individual
application.
The Integration Product test is an end-to-end test of
the product requirements across all applications and
platforms. After successfully completing the
application product test, integration product test can
occur.
Performance testing - Is carried out to ensure that a release
is capable of operating at the load levels specified in the
business performance requirements and any agreed-on
Service Level Agreements (SLAs) such as (load, stress,
endurance/ volume, and throughput)
Acceptance testing - Ensures that the users and
stakeholders are satisfied with the solution.
User Acceptance Testing Testing with the client.
Operational Acceptance Test - focuses on the
operations/support users to perform a set of tests to
verify that the system operates as intended. It verifies
Testing Technique
In the ADM for Testing perspective, both Discrete Testing and
Embedded Testing (or projects for testing in development
projects), share the common disciplines Analyze Test, Design Test,
Prepare Test, and Execute Test.
In the Analyze stage, the Test Team will Identify Application Test
Requirements, plan for Functional and Non-functional Testing,
Define the Test Environment and Data, and Confirm Test Analysis
Deliverables.
Requirements guide the design, building, and testing of the
product. And are initially developed during the Solution
Planning/Plan stage.
Requirements and Traceability Work Product is used to maintain
bi-directional traceability from the application requirement items
back to the high-level business requirements and to the
downstream analysis, design, build, and test components.
Product Testing is the first point where the solutions functional
and business requirements are tested together.
Assembly Test, ensures that related application components
function properly when assembled.
When a Production system is updated with new functionality,
existing code must be tested to ensure the new functionality will
not adversely impact it. This is called a Regression Test.
UAT proves to the responsible business units that the application
performs as expected and meets all the customer and product
requirements included in the current release.
Non-Functional Testing is a testing of an application for its nonfunctional requirements.
Testing Work Products are created during Test Planning,
Design and Preparation. These work products are:
Test Approach (Analyze Test) Test Scenarios (Design Test)
Test Conditions and Expected Results (Design Test)
Test Cycle Control Sheet (Analyze Test)
Test Scripts (Prepare Test)
Litmus is a test design artifact generation tool that semiautomates the test design phase.
Applied Statistics
Applied Statistics testing is a statistical approach to Test Design
that provides maximum coverage with a minimum number of test
scripts.
Applied Statistics provides three key benefits during the Test
Design phase:
Addresses common challenges in the Test Design process.
Provides a structured approach to Test Design.
Provides actionable information to determine the
appropriate amount of testing.
The Applied Statistics process involves the following key steps:
Define parameters and values.
Prepare and generate tests.
Analyze and adjust coverage.
Confirm expected results and scripts.
Review and sign-off.
Update test execution plan.
Two tools on the market that use Applied Statistics for test design
are:
Hexawise, a part of Accenture Delivery Tools (ADT):
Is a software Test Design tool.
Ensures all important combinations are tested by
maximizing test coverage with minimum number of
test conditions..
AllPairs Testing or Pair-wise Testing:
Is a combination of sets to be tested.
Is a method that finds all double-mode faults that are two
parameters conflicting with each other.
The following are the features of the Hexawise Test Design tool:
Creates test conditions quickly and easily.
Flexible to use on any kind of test project.
Generates the smallest possible number of tests to meet
the coverage requirements.
Peer Review
Verification and Validation are two important review methods.
Verification ensures that you build the product right
Validation ensures that you build the right product.
Peer reviews:
Promote early detection and removal of defects from a
deliverable
Facilitate knowledge transfer
Provide an understanding of the content
Gain inputs from the reviewer
Encourage continuous improvement
Identify areas of improvement in overall processes
Support overall quality and solution delivery excellence
Reduce time and costs resulting from rework.
The roles involved in a peer review:
Project Manager
Deliverable Owner (Author)
Reviewer
Moderator (Optional).
The phases in the Peer Review process are:
Planning for the Peer Review
Scheduling the Peer Review
Preparing for the Peer Review
Peer Review
The Test Environment is a setup of the software and hardware on
which the Testing Team is going to test the newly built software
product or application.
Common test data provides control over the quality of testing,
which significantly improves the productivity of the testing effort.
Test Data Management helps define standards, tasks, ownership,
roles, and responsibilities to ensure the accuracy, completeness,
and integrity of test data.
The five areas covered in an effective Test Data Management
Approach are:
Data Identification - the data items which the project will
require in order to test the application and state sources of
this data and any dependencies which exist.
Data Acquisition - the methods used to acquire data, such
as data stubs, data mining, data extracts and data
conversion.
Data Conditioning - Processes which need to be followed on
the acquired data such as scrubbing, modification, or
transformation.
Data Population - the processes to define how the data will
be populated to test environments (for example, will it be