Bibliothèque dédiée à la qualité logicielle
Etudes disponibles : 6
Basáez, Daniel: Fuzzing
Fuzzing is a technique for Testing, and is very effective for finding security
vulnerabilities in software.
Cullmann, Xavier-N./Lambertz, Klaus: Complexité et qualité
La complexité de code est un facteur ayant un impact direct sur la durée
de vie et l'exploitation d'un logiciel, notamment sur son taux de defauts,
sa testabilité et sa maintenabilité. Par conséquent, la compmplexité a une influence
directe sur la qualité d'un logiciel et sur son coût.
Gries, Caspar: New Trends in the Optimization of C-Code
Despite all of the recent progress concerning the tools and techniques of Software
Development, which allow for shorter development cycles by automating common
tasks and generally shifting the field of human engagement to more abstract levels,
only a small fraction of all projects benet from this advancement. A great part of
Software Development still uses concepts that have been devised decades ago, namely
the C programming language. ...
Lambertz, Klaus: Les erreurs de logiciels, le plus cher feu d´artifice de tous les temps
En Europe, grâce aux logiciels de tests nous pourrions économiser plus de 100
milliards d´euros par an
Rothmann, Andreas: Classic Algorithms for Pairwise Testing
This paper gives an overview on the most important classic algorithms for pairwise testing.
All algorithms use combinatorial strategies to find a test set, which covers pairwise
combinations of system parameters (for example system settings or inputs from the user).
The idea of pairwise testing is already 20 years old but for the last five years
its popularity has been rising extremely.
The reason is that testers have to face more complex software projects with the
same time target.
Raffeiner, Simon: Functionality and Design of the CMock framework
Development cycles in the embedded world
have not changed fundamentally for many years now.
Even though the principles of agility, test-driven development
and extreme programming have been adapted
to embedded development in the last ten years, the advantages of unit
testing and mocking are widely ignored. The problem
mainly arises from the misconception among developers
that code written for embedded platforms without an
operating system is hard to test because of the missing
interaction possibilities with the system, and that space
constraints make the use of frameworks impossible. Most
developers focus on system testing instead. This paper
shows how the CMock1 mocking framework can be used
in conjunction with the Unity2 unit test framework to implement
White-Box-Tests for embedded system software
written in the C programming language.
last updated: 14.01.2010 © 2009-2010 Verifysoft Technology GmbH
|