Managing Test Environments From AppLabs

650 views
556 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
650
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
64
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Managing Test Environments From AppLabs

  1. 1.
  2. 2. Test Environments How to get them Right Kevin Harvey 20 th August 2008
  3. 3. Overview <ul><li>This Webinar will aim to address the following: </li></ul><ul><ul><li>Why it is important to get Test Environments right </li></ul></ul><ul><ul><li>Environment Goals </li></ul></ul><ul><ul><li>Environment Requirements </li></ul></ul><ul><ul><li>Cost Effectiveness </li></ul></ul><ul><ul><li>Stability </li></ul></ul>
  4. 4. Why ? <ul><li>Keep the project cogs moving !!! </li></ul><ul><li>Minimise loss of man hours due to lack of environment availability in all areas of the project </li></ul><ul><li>Maximise design and development time available </li></ul><ul><li>Minimise unnecessary defects due to unknown environment inconsistencies </li></ul><ul><li>Save money </li></ul>
  5. 5. Key Attributes <ul><li>Stable </li></ul><ul><li>Maintainable </li></ul><ul><li>Accurate </li></ul><ul><li>Accessible </li></ul><ul><li>Cost effective </li></ul>
  6. 6. Basic Environment
  7. 7. Key Questions <ul><li>What will the test environment be used for ? </li></ul><ul><li>What does the test environment look like ? </li></ul><ul><li>Who will access the test environment ? </li></ul><ul><li>How many environments will I need ? </li></ul><ul><li>How do I minimise downtime ? </li></ul>
  8. 8. Purpose <ul><li>What will the test environment be used for </li></ul><ul><li>Proofing and designing business process solutions </li></ul><ul><li>Developing solutions </li></ul><ul><li>Unit testing </li></ul><ul><li>Smoke testing </li></ul><ul><li>Integration testing </li></ul><ul><li>User acceptance testing </li></ul><ul><li>Performance testing </li></ul><ul><li>Security testing </li></ul><ul><li>Operation acceptance testing </li></ul><ul><li>Post go live warranty periods </li></ul>
  9. 9. Technical Structure <ul><li>What does the test environment look like </li></ul><ul><li>Architecture </li></ul><ul><li>External system links </li></ul><ul><li>Interfaces both internal and external </li></ul><ul><li>Data Loads </li></ul>
  10. 10. User Requirements <ul><li>Who will access the test environment </li></ul><ul><li>Support </li></ul><ul><li>Developers </li></ul><ul><li>Testers </li></ul><ul><li>Analysts </li></ul>
  11. 11. Project Requirement <ul><li>How many environments </li></ul><ul><li>Development </li></ul><ul><li>Staging </li></ul><ul><li>Integration </li></ul><ul><li>Performance </li></ul><ul><li>Security </li></ul><ul><li>User Acceptance </li></ul><ul><li>Operational Acceptance </li></ul>
  12. 12. Stability <ul><li>How do I minimise downtime </li></ul><ul><li>Configuration management </li></ul><ul><li>Release Management </li></ul><ul><li>Efficient test user administration </li></ul><ul><li>Availability Monitoring </li></ul><ul><li>Virtualisation </li></ul>
  13. 13. Stability (cont) Example Dev STG INT PERF & SEC UAT OAT
  14. 14. Summary <ul><li>There are no definitive answers </li></ul><ul><li>Early and concise information gathering is key </li></ul><ul><li>Involve all key project players as early possible </li></ul><ul><li>Ensure stability through ongoing management </li></ul><ul><li>If possible appoint a dedicated Test Environment Manager </li></ul><ul><li>If you have any questions, then please e-mail: </li></ul><ul><ul><li>[email_address] </li></ul></ul>

×