Professional Documents
Culture Documents
Test case : - Test cases are how the testers validate that a software
function, such as deducting a payroll tax, or a structural attribute of the
software
Test Data: - Test data is information used to build a test case
Test Script: - Test Scripts are online entry of test cases in which the
sequence of entering test cases and the structure of the online entry system
must be validated. This may be manually prepared using paper forms, or may
be automated using capture/playback tools or other kind of automated scripts
tools
Risk: - Risk is the potential loss to an organization, as for example, the risk
resulting from the misuse of its computer. This may involved unauthorized
disclosure, unauthorized modification, and/or loss of information resources, as
well as authorized but incorrect use of a computer
Risk Analysis :- Risk Analysis is an analysis of an organization’s information
resources, it’s existing controls, and remaining organization and computer
system vulnerabilities
Threat:- A threat is something capable of exploiting vulnerability in the
security of a computer system or application
Vulnerability :- A weakness in automated system security procedures,
administrative controls, physical layout, internal controls, and so forth, that
could be exploited by a threat to gain unauthorized access to information or
disrupt critical processing
Control: - control is anything that tends to cause the reduction of risk.
Control can accomplish this by reading harmful effects or by reducing the
frequency of occurrence.
Testers role on the risk
Identify these risks
Estimate the severity of the risk
Develop tests to substantiate the impact of the risk on the application
Page 1 of 10 santhosh_data@yahoo.com
TEST PLANNING
Page 2 of 10 santhosh_data@yahoo.com
TEST PLANNING
Page 3 of 10 santhosh_data@yahoo.com
TEST PLANNING
Page 4 of 10 santhosh_data@yahoo.com
TEST PLANNING
When conducting risk analysis, two major components are taken into
consideration
The probability that the vent will occur
The potential or associated with the event
Some Primary Testing Risks :-
Not Enough Training :- User does not trained in testing, half of full time
independent testing personnel have been trained in testing techniques
Us Vs them mentality :- This common problem arises when developers and
testers are on opposite side of the testing issue
Lake of Test Tool: - IT management may have the attitude the test tools
are a luxury. Manual testing can be an overwhelming task
Lake of Management Understanding and support of testing:- Support
for testing must come from the top, otherwise staff will not take the job
seriously and testers morale will suffer
Lack of Customers and user Involvement:- Users and customers may be
shut out of the testing process, or perhaps they don’t want to be involved
Not Enough Schedule or budget for testing:- Over Reliance on
Independent Testers :- Sometimes called the “throw it over the wall”
syndrome, developers know that independent testers will check their work, so
they focus on coding and let the testers do the testing. Unfortunately, this
results in higher defect levels and longer testing times
Rapid Change: - In some technologies, especially Rapid Application
Development (RAD), the software is created and modified faster than the
testers can test it. This highlights the need for automation, but also for
version and release management.
Page 5 of 10 santhosh_data@yahoo.com
TEST PLANNING
Testers are in A Lose-Lose Situation:- the one hand, if the testers report
too many defects, they are blamed for delaying the project. Conversely, if the
testers do not find the critical defects, they are blamed for poor quality.
Having to Say “No” :- Having to say, “No, the software is not ready for
production,” is the single toughest dilemma for testers. Nobody on the project
likes to hear that and frequently testers succumb to the pressures of schedule
and cost.
Test Environment: - The work environment is not conducive to effective and
efficient testing.
New Technology: - The new focus on client/server, Intranet, and Internet
applications has introduced even more risk to the test process. These multi-
tiered systems are more complex than traditional mainframe systems,
New developmental processes: - Project teams have moved away from
traditional “waterfall” methods, and follow a much more iterative approach to
development and delivery.
Premature Release Risk:- Premature release is defined as releasing the
software into production under the following conditions:
The requirements were implemented incorrectly.
The test plan has not been completed.
Defects uncovered in testing have not been corrected.
The software released into production contains defects; although the
testing is not complete the defects within the software system may not
be known.
4. Risk Analysis
Page 6 of 10 santhosh_data@yahoo.com
TEST PLANNING
Page 7 of 10 santhosh_data@yahoo.com
TEST PLANNING
Testing priorities
o Compliance required to laws and regulations
o Impact on ompetitiveness
o Impact on ethics, values and image
5. Risk Management
Risk management is a totality of activities that are used to both the frequency
and the impact associated with risks. After determining risks; need to
determine risk ‘appetite’ (the amount of the loss) management is willing to
accept for a given risk. There are two activities with risk management Risk
Reduction Method and Contingency Planning
Reduction Method
o Risk Frequency X Loss/Occurrence = Total Loss
o Apply Controls to Minimize Risk
1. Reduce the Opportunity for Error » Minimize Loss
2. Identify Error prior to Loss » Recover Loss
o If the Controls Cost less than the Estimated Loss there is a Good
Case to Implement the Controls
Contingency Planning
o Action Plans should be established for activation when a loss is
known to occur for a given risk. The testers should evaluate the
adequacy of the contingency plans
o
Test Objectives – assures the project directives are met, testing to achieve the
mission of the software testing group. Testing the functional and structural
objectives of the software is accomplished to meet the quality definition category
for“meeting requirements.”
Acceptance Criteria – have the user define this criteria
Assumptions – have them clearly documented. For example if a software
system required a newly developed piece of hardware, an assumption could be
that the hardware would be available on a specific date. The test plan would then
be constructed based on that assumption.
Page 8 of 10 santhosh_data@yahoo.com
TEST PLANNING
People Issues – Watch out if the s/w engineering Director is also the head of
QA.
Constraints – Obvious constraints are test staff size, test budget, and test
schedule
7. Create test Plan
The test plan describes how testing will be accomplished. Its creation is essential
to effective testing, and should take about of the total test effort. If the plan
is developed carefully, test execution, analysis, and reporting will flow smoothly
A Test Plan should Have tests that are Repeatable, controllable and ensure
adequate coverage
o Repetable:-
o Controlable :-
o Coverage :-
How to Write a Good Test Plan…
o Define what it means to meet the project objectives.
o Understand the core business areas and processes.
o Assess the severity of potential failures.
o Identify the components for the system.
o Assure requirements are testable.
o Address implementation schedule issues.
o Address interface and data exchange issues.
o Evaluate contingency plans for system and activities.
o Identify vulnerable parts of the system and processes operating
outside the information resource management area.
Build the Test Plan:
o Set Test Objectives
Referenced by a number
Write as a measurable statement
Assign a priority
Define acceptance criteria
o Develop Test Matrix
Define tests as required
Define conceptual test cases to be entered as a test script
Define verification tests
Prepare software test matrix
o Define Test Administration
Identifies schedule, milestones, and resources needed
Cannot be completed until the test matrix is completed
Develop the Test Matrix:
o Define Tests as Required
Referenced by a name and number
Contains: Objective, Test Inputs, Test Procedure, Acceptance
Criteria, Test Controls – when to stop the test, & Reference to
what is tested
o Define Conceptual Test Cases to be Entered as Test Scripts
Use Case type tests.
o Define Verification Tests
Static test performed on a document developed by the team
responsible for creating software.
o Prepare the Software Test Matrix
A requirements traceability matrix.
Write the Test Plan:
Page 9 of 10 santhosh_data@yahoo.com
TEST PLANNING
o Start Early
o Keep the Test Plan Flexible
o Review the Test Plan Frequently
o Keep the Test Plan Concise and Readable
o Calculate the Planning Effort
o Spend the necessary time to complete the Test Plan
Test Plan Standard: - There is no one universally accepted standard for test
planning. There are many Test Plan Standards available on the Internet from
various organizations, for example: MilStd 498, IEEE829, IEEE/EIA 12207. Most
Test Plan Standards consist of the following sections
Test Scope Test Tools
Test Objectives Scope
Assumptions Referenced Documents
Risk Analysis Software Test Environment
Test Design Test Identification
Roles & Responsibilities Test Schedules
Test Schedule & Resources Requirements Traceability
Test Data Management Notes
Test Environment Appendices
Communication Approach
Page 10 of 10 santhosh_data@yahoo.com