[Paraview-developers] [Paraview] ParaView 3.8 Branch Comming Soon

[Utkarsh Ayachit]

Ken,

There's nothing special that you need to do to when creating a new
test. Just create it and you would normally and add it to the
Applications/ParaView/Testing/XML/CMakeLists.txt (or under Python).
There are a couple of new Cmake functions add_client_tests,
add_client_server_tests, add_client_render_server_tests that manage
the grouping of tests automatically based on the value of
TEST_GROUP_SIZE variable (defined in
Applications/ParaView/Testing/CMakeLists.txt).

If a test is changing global settings such as background color, lut,
application settings, view settings etc., then you don't want such a
test to get grouped with other tests. In that case, set a variable of
the form ${TEST_NAME}_BREAK to TRUE. If the aforementioned
cmake-functions detect such a variable, that test is played by itself.

You may look at  pqCommandLineOptionsBehavior::resetApplication (in
Qt/ApplicationComponents) to see what is reset before playing another
test in the sequence.

Utkarsh

On Fri, Feb 5, 2010 at 2:55 PM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> Recently the GUI testing framework has gone under some changes.  Most of
> these changes are to support running multiple tests under a single execution
> of ParaView.  Could someone explain how to create a new test under the new
> system and perhaps give some guidance on when we should be combining tests
> (and when we shouldn’t)?
>
> -Ken
>
>
> On 2/4/10 7:01 AM, "Dave Partyka" <dave.partyka at kitware.com> wrote:
>
> Greetings Everyone,
>
> In preparation for the ParaView 3.8 release we will be branching CVS head
> towards the end of February/Early March. Please be aware that if you have
> changes that should go out with this release then be sure to commit them
> soon. With this in mind I am going to be less tolerant of compile and test
> failures as we aim to make the dashboard as green as possible.
>
> Also there are a large number of files that have very poor coverage,
> including quite a few that have zero coverage.
>
> http://www.cdash.org/CDash/viewCoverage.php?buildid=531124
>
> If you are registered and log into CDash you can see a column of
> CDash guesstimated authors as well. If you are the main author of any of
> these files I would appreciate it if you would add a test or two to improve
> the coverage of your class to at least 60%. I will also be sending out
> emails to individual authors to keep this going.
>
> I appreciate your cooperation in these efforts.
>
> Thanks!
>
>
>
>    ****      Kenneth Moreland
>     ***      Sandia National Laboratories
> ***********
> *** *** ***  email: kmorel at sandia.gov
> **  ***  **  phone: (505) 844-8919
>     ***      web:   http://www.cs.unm.edu/~kmorel
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>