Re: [Cppqed-support] new testsuite

[Raimar S. <rai...@ui...>]

On Tuesday, January 07, 2014 11:38:15 Andras Vukics wrote:
> Hi Raimar,
> 
> Thanks for your reply, it worked. The only negative I see is that in such a
> kdevelop session when the projects are imported separately, kdevelop does
> not recognize them as separate git repositories. With monolithic import,
> however, git does work in kdevelop. This was not like that so far when I
> had only the separate repositories cloned. Can it be that kdevelop gets
> confused by the git repository on a level below in the directory hierarchy?

Unfortunately this is a drawback, yes. The problem is that the submodules 
don't have a .git directory but a .git file with an entry pointing to the true 
.git directory, which is located on the highest level of the super-repository. 
Kdevelop does not support this (yet). With monolithic import the git support 
of kdevelop is also not optimal, because you can only commit to the super-
repositories, not the submodules. It didn't bother me too much because I'm not 
using the kdevelop git features at all.

> I tried the testsuite and it ran fine both with make and ctest. I must say
> I’m very impressed. The documentation is also nice, though at the moment I
> do not have time to try and add new tests on the basis of it. One thing
> that occured to me: how do you think we can integrate the bazaar „physical”
> testsuite which relied on comparison of trajectory outputs via Sebastian’s
> pycppqed?

I'm glad it works and that you like it. Which parts of pycppqed are needed for 
the physics test suite? If it is only comparing trajectories, this is already 
supported by the python test driver. In the long run it is probably best to 
merge pycppqed into cpypyqed.

Best regards
Raimar