[Dune] Improve automated testing

[Christoph Grüninger]

Hi Christian,
I think we should fix our tests first. There are flaws and they need to 
be addressed. After our tests are in a good shape we could start 
thinking about better nightly builds, continuous integration, CTest or 
whatever.

> So... if someone does have a good idea, I'd be happy to
 > here how we can improve the currently automated test
 > situation.

- The status monitor (overview) Matthias referred to does not reflect 
the latest run. I am under the impression it either was not updated or 
is the average of multiple runs. That should be fixable with a 
reasonable amount of work.

- UG is not found.

- Some warnings would vanish if the test would be configured with the 
option --enable-fieldvector-size-is-method

- Run tests on a more regular basis. Some tests for dune-geometry were 
run in November and yesterday.

I tried to remove some of the warnings but could not satisfyingly solve 
them:

- Dune::GeometryType::basicType is deprecated. What should I use 
instead? I could not find any documentation about this. At least a 
deprecation message for the Dune macro would be nice. I'll add this message.

- Dune::EntityPointer<GridImp, EntityPointerImp>::operator & is 
deprecated. The documentation states "This cast is no longer needed to 
ensure assignability of iterators to EntityPointer." Ok, but at least at 
gridcheck.cc:646:31 I don't see the use of th &-operator.

If you enlighten me, I'll take care of these problems.

Bye
Christoph

-- 
Unix is simple and coherent, but it takes a genius – or at any
rate a programmer – to understand and appreciate the simplicity.
[Dennis Ritchie, 1941-2011, created C and Unix]