Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Hey,


On Tue, Mar 18, 2014 at 9:09 AM, Fouda Manga, Christian <
christian.fouda_manga@siemens.com> wrote:

 Hi,

we are using CppUnit Framework to test gas analyser which are safety
relevant products. For the certification of the product, we have to do the
following:


   1. show the specification and the documentation of the all the tools
   used. That means also for the test tools (CppUnit Framework).
   2. Prove that that the test tool fulfills its specification


I have the following questions:


   1. Is there any specification or detailed documentation available?
   2. Is there a proof of fulfilling the specification available?





So the most up-to-date documentation is at
http://people.freedesktop.org/~mmohrhard/cppunit/ which contains all my
fixes for documentation errors. However there is no formal specification
for cppunit except for this automatically generated documentation based on
the doxygen comments in the code.


As there is no formal specification we can of course not prof that we
fulfill it. We have a number of automated tests in examples/cppunittest
that you can execute and that test most features and make sure that they
are working correctly. I'm not sure if the VisualStudio project file in the
directory is still working but I execute the tests at least during
packaging on Linux.

Help in improving the documentation is of course highly appreciated.

Regards,
Markus

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.