acctesting test campaign edition continuous delivery

Acctesting Test Campaign Edition Continuous Delivery

Turcu CristinaTE-MPE

On behalf of the TE-MPE-MS Software TeamTechnical meeting 16.01.2014

K. Fuchsberger 2TE-MPE-TM, 2012-05-10, Acctesting – Motivation, Overview and First Experience

Content

Acctesting Test Campaign Edition-Situation-Improvements-New Features-Outlook

Continuous Delivery-Deployment before -Deployment now-Summary-Outlook

Turcu Cristina | TE-MPE | Acctesting Test Campaign Edition & Continuous Delivery 2

• Accelerator testing

Situation


Situation

• 3 steps for validating a test:– Test execution – Test analysis – Test signing

Test-Phases.

Tests


What is a Campaign ?

• Campaign: contains the necessary tests in order to determine if a system/circuit is safe for running.

• Test Plan: defines which tests have to be executed for which systems during one test campaign.



Content




Test Campaign Edition Why we need it?

• Before• Edit the test plan by directly editing the Database (DB)

– Security or consistency problems– More flexibility needed

• Improvements:• Editing the test plan without directly editing the DB• Impose restrictions on editing the DB, using Role Base

Access Control (RBAC) • Allows many campaigns and keeps the history of them• Allows different system types, not only Circuits as before


Status


Persistence Layer

GUIPanel

GUIPanel

NewGUIPanel

Core Layer

Data

Migration

Old DB(LSA account ‘owned’ by CO)

New DB(dedicated DB account)


Content




Acctesting - new features

• Campaign history• Campaign browsing• Display and edit old campaigns



• Create, Delete and Edit selected campaign


• Enable/Disable single test



• Systems are grouped and can be activated/deactivated by test types




Content




Acctesting Outlook

Next Steps:

• Waiting for user feedback• Will be used for this Hardware commissioning• Server is operational in development (dev)

environment, but the GUI parts can’t be release for the moment– waiting for some release features from CO



Content




Continuous Delivery

• What it is?– represents a series of practices to ensure the code

can be rapidly and safely deployed for operation by delivering every change to a production-like environment after all the necessary tests passed.

• Why do we need it?– To always have the latest product version

potentially deliverable– For a simple and fast deployment.



Content




Project dependencies

• 45 projects• Respect order• Time: ½ day

• Common build



Content




Continuous Delivery

Commit onRevision control software (SVN)

Automatic build using a Continuousintegration server

Manually deployment

dev

pro

Junit:Unit testsIntegration testsFunctional testsAcceptance tests

• Continuous delivery:– Used by many companies– Has proven its efficiency


Commit a server change

• Commit to SVN– generate a snapshot of the application (Tarball (.tar))

• use to deployment on the node (development /production)– attaches version of the DB and the server to the Tarball

• usefull in case of a rollback, so we know which version of the server is compatible with witch version of DB

Commit onSVN


Manually deployment

dev

proJunit:Unit testsIntegration testsFunctional testsAcceptance tests


Bamboo

Commit on SVN


Manually deployment

dev

pro

• Continuous integration server. • Builds the project and runs the tests whenever a developer

commits an update• Continuously tests the software

Developers

SourceControl

Agents


Bamboo


• The system is working when all the builds are green

– a problem can be spotted quickly– provides the root cause of the error

• stack traces

• Provides statistics– build duration– number of failures /build– successful buils/time– time to fix, etc

Bamboo


• Integration– Jira (able to associate task with builds), Fisheye(a

source history with hooks into Jira), Crucible (assists in code reviews), Clover (monitors code coverage in the build)

– Build systems: Ant, Maven, Make, Command Line

Bamboo


• Crucible - assists in code reviews

Bamboo


Unit Tests

• JUnit – framework for writing tests• Unit tests:

– Test small unit of functionality– Everything is done in the memory(no DB, no network)– Uses mocks

• Benefits– Formalize requirements– Write and debug code easily, fewer bugs– More maintainable code

Commit onSVN

Automatic build using Bamboo

Manually deployment

dev



Integration Tests

• Integration tests– Test of how well classes work together– Environment(accessing DB, connecting to server..)

• Purpose– find bugs that unit tests can't detect– To verify

• Functionality• Performance• Reliability

Commit onSVN


Manually deployment

dev



Functional & Acceptance Tests

• Functional tests– check a particular feature for correctness by comparing with

the specification– don't concern on intermediate results

• Acceptance tests– particular type of functional test– illustrate the user stories – ensure that all the software features are complete

Commit onSVN


Manually deployment

dev



Deployment

• Information about the state of the server:– what version of the DB it is used– what version of the server has been deployed

• What we improved– possibility to specify the environment to deploy the server: pro /

dev– ability to see all succesful deployments.

Commit onSVN


Manually deployment

dev



Deployment


• aaa• Four Steps (done automatically):• 1. Stop server• 2. Migrate the DB• 3. Deploy the server• 4. Start server

Deployment



Content




Summary

Commit onSVN

Build using Bamboo

Deploy using Bamboo

dev

pro

Junit:Unit testsIntegration testsFunctional testsAcceptance tests

Automatically

Manually selecting the environment, the release and starting the deployment.

generate a Tarball(.tar)attaches version of the DB and the server to the Tarball

Stop serverMigrate the DBDeploy the serverStart server



Content




Outlook

• In place for:– Acctesting server

• To be extended to:– RDA3 server– PC Interlock server– System management server– Analysis server

• Plan:– Have continuous delivery for the GUI– Improve DB rollback


Thank you for your Attention!

• Questions?


acctesting test campaign edition continuous delivery

Documents

test plan

acctesting motivation

release features

necessary tests

conew dbdedicated db

database dbsecurity

development dev environment

hardware commissioningserver