Virtualization in testing – case AditroFAST-presentationEspoo, 28.4.2009

13.04.23 2

SPEAKERS

Ilkka Koskinen (ilkka.koskinen@aditro.com)• Worked in Aditro since 1998• Duties in product development: Definitions, database

design, testing issues, administrative tasks

Aki Villa (aki.villa@aditro.com)• Worked in Aditro since 1999• Duties in product development: Testing, Installation

packaging, virtualization, technical support

13.04.23 3

CONTENT

Virtualization possibilitiesVirtualization in Aditro FinlandDevice lifecyclePractical issues to be consideredSnapshotsVirtualization in testsOther issues for high utilization levelPros and consSummary

VIRTUALIZATION POSSIBILITIES

13.04.23 4

Focus on Aditroproduct development

13.04.23 5

Machine virtualization

VIRTUALIZATION IN ADITRO FINLAND (PRODUCT DEVELOPMENT)

13.04.23 6

DEVICE LIFECYCLE

13.04.23 7

1. PlanDefine deviceCheck existence

2. OrderDoc or web formPre-defined options

3. UseMainte-nanceCopies

4b. Store

4a. Kill

PRACTICAL ISSUES TO BE CONSIDERED

» Role of virtual device» Private or public» Task-specific or general

» Life cycle» Depends on role» Snapshots, backups etc.

» Responsibilities» Technical maintenance» Content maintenance

» Location of auxiliary software» On VM or own workstation?

13.04.23 8

SNAPSHOTS

13.04.23 9

“Snapshot is a representation of a person or scene in the form of a print or transparent slide; recorded by a camera on light-sensitive material”

Source: The American Heritage® Dictionary of the English Language

SNAPSHOTS

13.04.23 10

» Image of whole device» Data, applications, user definitions etc. saved as they were when snapshot

was taken

» Main purposes» to return to an earlier state, when re-running test set» to freeze defect state for further investigation

» A good management application recommended» More or less automated snapshot handling, graphical user interface etc.» In some cases it’s needed to take snapshots from several devices

simultaneously» Potential IP-address conflicts

VIRTUALIZATION IN TESTS

13.04.2311

Functionality tests (Dev. team)

DEVELOPMENT PERIOD

Installation tests (Dev. Team, architects)

Regression tests (Dev. team)

Performance tests (Dev. team)

Concept/Suite tests (Several teams)

Alfa tests (Teams + Customer care)

Beta/pilot tests (Customer)

SUPPORT PERIOD CONTINUOUS

Problem investigations(Customer care & Dev. team)

Testing of new technologies etc.(Dev. teams, architects)

Unit tests (Dev. team)

Suitable for almost every test type!

OTHER ISSUES FOR HIGH UTILIZATION LEVEL

» Virtualization & Test Automation» Virtualization might offer ’countless’ test environments, but without

automated tests human resources become easily a bottleneck» Does automated testing tool support used virtualization technology / practice?

» Virtualization & Test Data» Several VMs (original or snapshots) -> where test data is located and how it

co-operates with actual VM?» Who is responsible to maintain test data?

13.04.23 12

PROS & CONS

» Flexible » Amount of devices and

their content according to actual needs

» Easy-going» Fast to enable/disable» Fast to repair

» Consistent states» Rollbacks instead of

deletions and clean ups

» Requires resources» HW / Personnel

» Requires planning» To avoid overlapping,

unnecessary costs, general confusion

» Requires elaborate knowledge

» Doesn’t work without co-operation in almost every organization level

13.04.23 13

» Real devices» Basically same

features as in physical devices

» Licenses

SUMMARY

13.04.23 14

Requires investments, time and support

A never ending improvement process

Possible to achieve impossible goals