Hi,
There is an good example on how to set environment variables: nightly test. Please see the
below file:
There is an informal document for your reference(not an official version, just mine :-)
).
Also there is an official document to tell you how to test with local Synthesis Server:
-----Original Message-----
From: Zhu, Yongsheng
Sent: Friday, January 22, 2010 9:49 AM
To: Bommaraju, Rajyalakshmi; syncevolution(a)syncevolution.org
Cc: Zhu, Yongsheng
Subject: RE: Running TestCases
Hi, Raji
The 'CLIENT_TEST_SERVER' should be 'scheduleworld' not
'scheduleword1'.
Commonly, a client-test needs
2 configs for that: scheduleworld_1 and scheduleworld_2. You have to firstly set
up for them well.
Cheers,
Yongsheng
> -----Original Message-----
> From: syncevolution-bounces(a)syncevolution.org
> [mailto:syncevolution-bounces@syncevolution.org] On Behalf Of Bommaraju,
> Rajyalakshmi
> Sent: Friday, January 22, 2010 9:26 AM
> To: syncevolution(a)syncevolution.org
> Subject: [SyncEvolution] Running TestCases
>
> Hi ,
>
> I am trying to run unit tests by copying meeting event data into a file called
> ical20 and placing this in /tmp/test folder. I set following env variables, also
> verified that they are in env.
>
> CLIENT_TEST_SERVER=scheduleworld1
> CLIENT_TEST_SOURCES = ical20
> - CLIENT_TEST_EVOLUTION_PREFIX=file:///tmp/test
>
> , when I run the test as, client-test Client::Sync::ical20::testConversion, Test
fails
> and produced a log which I attached here, My understanding of log is that it
> failed due to being all the sources (calendar , memos etc) inactive.
>
> I tried to set the calendar active by
>
> syncevolution -c scheduleworld1 calendar and then tried the above
"client-test"
> command, but keep getting the same error result.
>
> My questions are , Is my understanding of the log wrong? , If activing calendar
is
> wrong in the way I did, what is the correct way of doing it.?
>
>
> Thanks
> Raji.
> _______________________________________________
> SyncEvolution mailing list
> SyncEvolution(a)syncevolution.org
>
http://lists.syncevolution.org/listinfo/syncevolution