Practical experience with test-driven development during commissioning of the multi-star AO system ARGOS

M. Kulas; Jose Luis Borelli; Wolfgang Gässler; Diethard Peter; Sebastian Rabien; Gilles Orban de Xivry; Lorenzo Busoni; Marco Bonaglia; Tommaso Mazzoni; Gustavo Rahmer

doi:10.1117/12.2056218

18 July 2014 Practical experience with test-driven development during commissioning of the multi-star AO system ARGOS

M. Kulas, Jose Luis Borelli, Wolfgang Gässler, Diethard Peter, Sebastian Rabien, Gilles Orban de Xivry, Lorenzo Busoni, Marco Bonaglia, Tommaso Mazzoni, Gustavo Rahmer

Author Affiliations +

Proceedings Volume 9152, Software and Cyberinfrastructure for Astronomy III; 91520D (2014) https://doi.org/10.1117/12.2056218
Event: SPIE Astronomical Telescopes + Instrumentation, 2014, Montréal, Quebec, Canada

Abstract

Commissioning time for an instrument at an observatory is precious, especially the night time. Whenever astronomers come up with a software feature request or point out a software defect, the software engineers have the task to find a solution and implement it as fast as possible. In this project phase, the software engineers work under time pressure and stress to deliver a functional instrument control software (ICS). The shortness of development time during commissioning is a constraint for software engineering teams and applies to the ARGOS project as well. The goal of the ARGOS (Advanced Rayleigh guided Ground layer adaptive Optics System) project is the upgrade of the Large Binocular Telescope (LBT) with an adaptive optics (AO) system consisting of six Rayleigh laser guide stars and wavefront sensors. For developing the ICS, we used the technique Test- Driven Development (TDD) whose main rule demands that the programmer writes test code before production code. Thereby, TDD can yield a software system, that grows without defects and eases maintenance. Having applied TDD in a calm and relaxed environment like office and laboratory, the ARGOS team has profited from the benefits of TDD. Before the commissioning, we were worried that the time pressure in that tough project phase would force us to drop TDD because we would spend more time writing test code than it would be worth. Despite this concern at the beginning, we could keep TDD most of the time also in this project phase This report describes the practical application and performance of TDD including its benefits, limitations and problems during the ARGOS commissioning. Furthermore, it covers our experience with pair programming and continuous integration at the telescope.

Citation Download Citation

M. Kulas, Jose Luis Borelli, Wolfgang Gässler, Diethard Peter, Sebastian Rabien, Gilles Orban de Xivry, Lorenzo Busoni, Marco Bonaglia, Tommaso Mazzoni, and Gustavo Rahmer "Practical experience with test-driven development during commissioning of the multi-star AO system ARGOS", Proc. SPIE 9152, Software and Cyberinfrastructure for Astronomy III, 91520D (18 July 2014); https://doi.org/10.1117/12.2056218

ACCESS THE FULL ARTICLE

INSTITUTIONAL
Select your institution to access the SPIE Digital Library.

SELECT YOUR INSTITUTION

PERSONAL
Sign in with your SPIE account to access your personal subscriptions or to use specific features such as save to my library, sign up for alerts, save searches, etc.

PERSONAL SIGN IN

No SPIE Account? Create one

PURCHASE THIS CONTENT

SUBSCRIBE TO DIGITAL LIBRARY

50 downloads per 1-year subscription

Members: $195

Non-members: $335 ADD TO CART

25 downloads per 1 - year subscription

Members: $145

Non-members: $250 ADD TO CART

PURCHASE SINGLE ARTICLE

Includes PDF, HTML & Video, when available