Quality Assessment - Test Harness

What is it about?

Our new test harness is based on CMake/CTest/CDash. CDash is an open source, web-based software testing server actively developed by Kitware (http://www.cdash.org). It is useful for keeping your installation of OpenFOAM®-ext up-to-date with the latest source code release, and to run it automatically against a suite of predefined test cases.

The CMake/CTest scripts for running this test harness are available on the OpenFOAM®-extend SVN repository, under the new section trunk/Breeder_1.5/other/testHarness.

By default, the results generated by the test harness will be published on dashboards deployed on OpenFOAM®-extend at the following address:

http://openfoam-extend.sourceforge.net/CDash/index.php

1. users to pinpoint OF installation problems on various platforms
2. developers to identify problems resulting from code modication
   or addition of new code
   • Non portable code
   • Partial source code commits
   • Broken code following commits
   • Broken tutorials and unit tests
3. testing OpenFOAM® for various:
   • Operating systems
   • Compilers
   • Parallel execution environments

How to contribute?

Submission of Test Harness Results

Please run the tests and re-submit your results. There are various types of result submission possible:

• Experimental (testing and tuning)
• Nightly (once a day using cron job)
• Continuous (polling source code repo.)

A public server is available on OpenFOAM®-Extend using CDash version 1.7.0

http://openfoam-extend.sourceforge.net/CDash

Please have a look at the OpenFOAM® test harness scripts available at

https://openfoam-extend.svn.sourceforge.net/svnroot/openfoamextend/trunk/Breeder
1.5/other/testHarness

Test Case Submission

In order to make OpenFOAM®-ext even better please collect and provide your test-cases for the test harness. Contact Martin Beaudoin for details.

Quality Assessment - Bug Tracker

What is it about?

"A program that is initially bug-free, wasn't worth writing in the first place"

Our bug tracker is based upon MantisBT and designed to help quality assurance. It is intended to provide precise information to the developers on how to reproduce the bug exactly in the underlying system and program version.

The bug tracker within the OpenFOAM®-Extend Project on the one hand side provides a clear interface and a centralized overview of reported software bugs to the developers and thus enables to deduce concise tasks for further improvements of the OpenFOAM® CFD toolbox. On the other hand side the reporter gets notified about changes, updates and work details related to the reported bug.

For this purpose of tracking the state of a bug its report is associated to several states (there are more, but these are the important ones):

How to contribute?

In case you have found a bug or face issues when using OpenFOAM®-Extend feature please report them. For this use the provided form at

https://sourceforge.net/apps/mantisbt/openfoam-extend/main_page.php

Please note: In order to avoid confusion please solely provide bug reports related to OpenFOAM®-Extend features. Reports on more general bugs concerning the official core of the OpenFOAM® CFD toolbox should be adressed to OpenCFD® Ltd. using their bug reporting system under http://www.OpenFOAM®.com/bugs/. Thanks!

Further, please do solely request extensions of basic features that are already implemented and available. For this purpose the bug tracker provides the option Severity/Feature under the menu item "Report Issue". At this place the corresponding developer will take care of your request.

Use Case - Bug Tracker Feature (Extension) Request
I.e. groovyBC should be able to deal with velocity profiles read from files like it already does with timelines.

In order to keeps things sorted please contact sub-groups closest to your topic for features that currently are not assigned to some person in charge.

Use Case - Sub-Groups and Sub-Projects (currently not available feature)
I.e. An automatic tet-mesher (like snappyHexMesh hex-meshes) should be available.

Quality Assessment - Release Committee

For quality assessment it is further planned to found a release committee in order to review the development state in different task lines - proofing their quality - and subsequently to announce releases on a regular basis.

More information will follow at this place!