DataLoader in Tests: A good idea to verify number of calls?

[bjoernmayer]

Heyho,

I have a test that fails, if I execute all test methods.
If I execute the failing method only, it succeeds.

I thought caching might be the problem, but disabling it for the Dataloader didn't help.

The part that fails is a verification for number of calls to our actual datasource.
In theory it should be called only once, because batching.

In the test it appears to be called twice.

Now the odd part:
I gave up finding an error in our implementation and change the verification to be for two calls.
Guess what:
I fails again, because the datasource was called once

Is it a good idea to verify this number?
Is DGS invoking the Dataloaders sometimes as batches and sometimes seperately?

[bjoernmayer]

I was able to get the test running by using @DirtiesContext

[bjoernmayer]

I was able to get the test running by using @DirtiesContext

Scratch that. The test is flaky.