|Re: [CDO] Switch to another DB backend when doing CDO tests [message #480708 is a reply to message #480670]
||Tue, 18 August 2009 05:48
| Eike Stepper
Registered: July 2009
The test configuration(s) is usually setup by the test suite, together
with the set of test classes. The test configurations are stored on the
file system and read/used if a test run does not explicitely setup a
configuration. Once you've properly started the right suite, you should
be able to repeat single tests with the same configuration.
It's a bit complicated but due to restrictions / design flaws of JUnit
the best we can achieve.
Stefan Winkler schrieb:
> I don't know if there's an "official" way. Yes you can rerun a single
> test from an already run AllTests log.
> My own workaround is usually to temporarily override initTestClasses()
> in AllTestsDbH2 and only adding the test case(s) I want to run without
> calling super.
> However, one must not forget to delete the initTestClasses again before
> committing ;)
> Kai Schlamp schrieb:
>> Never mind I just found a way to re-run a specific test from the JUnit
>> GUI somehow.
>> Kai Schlamp wrote:
>>> Stefan Winkler wrote:
>>>> Kai Schlamp schrieb:
>>>>> When running
>>>>> from my newly setup CDO Source Workspace it fails because the MemStore
>>>>> is automatically used (where some annotations don't make any sense).
>>>>> How do I switch to using H2 instead? Is there a configuration file?
>>>>> Where is it?
>>>> Which launch configuration are you using?
>>>> You should use this one: CDO AllTests (H2).launch which is contained in
>>>> the org.eclipse.emf.cdo.tests.db project.
>>> Thanks Stefan. But is there a way to run a specific test with H2 or
>>> whatever? Before I re-setup my workspace I just right clicked the
>>> test file and chose Run JUnit test. H2 was somehow preset.
Powered by FUDForum
. Page generated in 0.02545 seconds