Vortrag III - 04.11.2010

11:15 - 12:00 A collaborative test design approach
for unit tests in large-scale projects
Michael Mlynarski,
Universität Paderborn/Software Quality Lab

 

Although testing nowadays increasingly gains in importance, unit testing is mostly not approached systematically. Particularly in large-scale projects, the test manager often only cares about higher test levels, while unit tests just “happen” during development. On the other hand several companies in the software development industry discovered the need for more agility in their business. Agile software development frameworks like Extreme Programming (XP) point out, that testing has a major role within it. Especially techniques like Test-Driven Development (TDD) where code is implemented according to prior defined test cases promise high quality through testable code. Although the advantages of using TDD in small and medium projects has been shown, the use in large-scale projects is still missing.

At Capgemini sd&m we run projects with agile development models like Scrum. We have observed that, nevertheless, in most of the projects TDD is not used. In interviews with the responsible test managers we have identified the following underlying reasons:

• Project leaders shy the risk of additional costs and of not getting ready in time.

• TDD approaches often lack of structured test design methods and of measurable functional test coverage.

• The resulting test cases seem to be too fine grained. Higher level test cases are then still missing.

• TDD usually results in a large number of test cases, which are difficult to maintain over a longer period.

At Capgemini sd&m we have introduced a test methodology, focusing large-scale projects. It is based on ISTQB  and defines a clear test process for all test levels and a test specification method. Early design of so called test aspects for each test level enables us to give the development team a proposal of what should be tested within unit testing. The proposal is handed-over to the development team which extends it with their own test aspects. Our approach connects structured and risk-based test design with TDD concepts. This way we improve the overall test quality and enhance the communication between the test and development team. Our solution aims to improve TDD and the mentioned problems.

 

Michael Mlynarski, Universität Paderborn/Software Quality Lab
Michael Mlynarski hat ein Informatik-Masterstudium an der Universität Paderborn abgeschlossen. Seit März 2008 arbeitet er im Auftrag des Software Quality Labs (s-lab) der Universität Paderborn bei Capgemini sd&m Research an dem Thema Testspezifikation. Sein Promotionsschwerpunkt liegt auf dem Gebiet des modellbasierten Testens von Informationssystemen.

 

 

 

 

> zurück zum Vortragsprogramm

© 2014 imbus AG