managing test environments

15
AppLabs confidential and restricted circulation 1

Upload: kevin-harvey

Post on 25-May-2015

1.538 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Managing Test Environments

AppLabs confidential and restricted circulation 1

Page 2: Managing Test Environments

Proactive Test Environments

Kevin Harvey

Page 3: Managing Test Environments

AppLabs confidential and restricted circulation 3

Overview

Test environments no matter how large, small, simple or complex, areIntegral to the success and smooth running of any testing project.

Upfront organisation combined with effective proactive environmental management can ensure that environmental downtime or instability is mitigated as much as possible. Ensuring the affects of technical downtime on the project baseline dates are kept to a minimum

This can be achieved by addressing a few points prior to setting up your test environment (s)

Page 4: Managing Test Environments

AppLabs confidential and restricted circulation 4

Why ?

Keep the project cogs moving !!!

Minimise loss off man hours due to lack of environment availability in all areas of the project

Maximise design and development time available

Minimise unnecessary defects due to unknown environment inconsistencies

Save money

On a project with 10 development / support, 5 testers & 2 business resources environment downtime would cost a project approx ..... £10,000 per day !!!!!

Page 5: Managing Test Environments

AppLabs confidential and restricted circulation 5

Key Attributes

Stable

Maintainable

Accurate

Accessible

Cost effective

Page 6: Managing Test Environments

AppLabs confidential and restricted circulation 6

Basic Environment

USERS &

SECURITY

USERS &

SECURITY

CUSTOMERINFORMATION

CUSTOMERINFORMATION

ACCOUNT INFORMATION

ACCOUNT INFORMATION

PROCESSING ENGINE (s)

PROCESSING ENGINE (s)

REPORTINGREPORTING

Page 7: Managing Test Environments

AppLabs confidential and restricted circulation 7

Key Questions

What will the test environment be used for ?

What does the test environment look like ?

Who will access the test environment ?

How many environments will I need ?

How do I minimise downtime ?

Page 8: Managing Test Environments

AppLabs confidential and restricted circulation 8

Purpose

What will the test environment be used for

Proofing and designing business process solutions Developing solutions Unit testing Smoke testing Integration testing User acceptance testing Performance testing Security testing Operation acceptance testing Post go live warranty periods

Page 9: Managing Test Environments

AppLabs confidential and restricted circulation 9

Technical Structure

What does the test environment look like

Architecture External system links Interfaces both internal and external Data Loads

Page 10: Managing Test Environments

AppLabs confidential and restricted circulation 10

User Requirements

Who will access the test environment

Support Developers Testers Analysts

Page 11: Managing Test Environments

AppLabs confidential and restricted circulation 11

Project Requirement

How many environments

Development Staging Integration Performance Security User Acceptance Operational Acceptance

Page 12: Managing Test Environments

AppLabs confidential and restricted circulation 12

Project Requirement (cont)

Example scenarios

PERF & SEC

PERF & SEC

Page 13: Managing Test Environments

AppLabs confidential and restricted circulation 13

Stability

How do I minimise downtime

Configuration management Release Management Efficient test user administration Availability Monitoring

Page 14: Managing Test Environments

AppLabs confidential and restricted circulation 14

Stability (cont)

ExampleDevDev STGSTG

INTINT PERF & SEC

PERF & SEC UATUAT OATOAT

Page 15: Managing Test Environments