> umm, the point is that @SkipByGridDialect doesn't work, or I could just
put it on existing methods.
By splitting up the affected tests into several classes you should be able
to apply @SkipByGridDialect on the class level. Then no session factory at
all will be built bootstrapped for a skipped b
On 15/04/15 15:20, Gunnar Morling wrote:
> > umm, the point is that @SkipByGridDialect doesn't work, or I could
> just put it on existing methods.
>
> By splitting up the affected tests into several classes you should be
> able to apply @SkipByGridDialect on the class level. Then no session
> fa
On 15/04/15 13:54, Gunnar Morling wrote:
> How many tests are affected by this problem?
hmm, good question. At present most of the association tests and a
handful of assorted others that happen to use associations are blowing
up because I haven't finished the association support. I'm working
How many tests are affected by this problem?
If not too many, it might be feasible to split those test methods into
several test classes (each only referencing the entities it actually needs)
which you then can mark individually with @SkipByGridDialect as needed.
I am no big of copying/pasting te
In the course of developing the cassandra backend for OGM I've hit an
issue with some of the backendtck tests.
These tests are in core and reused by each backend. It's possible to
exclude tests at class or method level per backend, which prevents
irrelevant tests from running for a given backe
