I see your point.
Thanks,
Miklos
On 6 August 2014 17:15, Sascha Zelzer <[email protected]> wrote:
> Hi Miklos,
>
> Yes, for most parameterized tests the MITK_PARAMETERIZED_TEST* macros
> are the way to go. We try to move away from command line arguments for
> tests because they make it harder to execute the actual tests with
> referring to ctest -R ...
>
> Best,
> Sascha
>
> On 07/26/2014 12:34 PM, Miklos Espak wrote:
> > Hi,
> >
> > I noticed that most MITK_TEST macros are now deprecated and you should
> > use a cppunit based framework. Although the docs have not been updated
> > yet, I found a couple of examples in the source code and most changes
> > are straightforward.
> >
> > Just one question. Is there a something in the new framework that
> > could work with the mitkAddCustomModuleTest CMake macro?
> >
> > We use this macro to call the same test with different parameters.
> >
> > Or should we use MITK_PARAMETERIZED_TEST_1 C++ macro and specify the
> > parameters in the source code instead?
> >
> > Cheers,
> > Miklos
> >
>
>
>
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
