[CITE-Forum] Testing Locally

BARIS KAZAR baris.kazar at oracle.com
Thu Apr 25 17:19:47 EDT 2013


Hi,-
   I think there must have been some bug in the CITE TeamEngine or the CITE test scripts since
the following snippet seems picking up all the gml:id's now:
  <ogc:GmlObjectId gml:id="{$gml.id}"/>

Thanks

On 4/25/2013 4:13 PM, BARIS KAZAR wrote:
> Hi Richard,-
>  Thanks, that info was very crucial as it is confirming my question:
>
> "I would like to run TeamEngine CTL suites from command line. Thus, should we extract the contents of teamengine-core/target/teamengine-core-4.0-beta2-distribution.tar.gzip into a directory and set the corresponding path as $TE_HOME env variable? That tar file was created after "maven install site" command. "
>
> Now, the tests are working again.
> I see some changes in the tests such as
> wfs-1.1.0-Basic-GetFeature-tc33.1
> The last test for this test suite has changed from <ogc:GmlObjectId gml:id="f001"/> to <ogc:GmlObjectId gml:id="f001 f002 f003 f008 f015"/>.
>
> Best regards
> baris
>
>
>
> On 4/24/2013 11:26 AM, Richard Martell wrote:
>> Baris,
>>
>>
>> Use the binary distribution--don't try to execute the scripts in
>> the source tree.
>>
>> e.g. unpack the archive somewhere (call this TE_HOME):
>>
>>> cd TE_HOME/bin/unix
>>> ./test -source=*
>> where the source param value is a filesystem reference that is either
>> relative to TE_BASE/scripts or absolute.
>>
>> Note that you just need to give the location of the CTL script
>> containing the ctl:suite element (or its parent directory).
>>
>> -- 
>> Richard
>>
>>
>>> -----Original Message-----
>>> From: BARIS KAZAR [mailto:baris.kazar at oracle.com]
>>> Sent: Tuesday, 23 April, 2013 10:51
>>> To: Richard Martell; cite-forum at lists.opengeospatial.org
>>> Cc: BARIS,KAZAR
>>> Subject: Re: [CITE-Forum] Testing Locally
>>>
>>> Hi Richard,-
>>>    Thanks, but i dont want to use the console for now to make
>>> things simpler.
>>>
>>> Trying to run the tests now:
>>>
>>> In the
>>> <some_dir>/teamengine4_apr16_2013/teamengine-core/src/main/scr
>>> ipts/shell/unix dir where test.sh is found,
>>> i am running the following and i get an exception (and
>>> $TE_BASE is appropriately defined):
>>>
>>> echo $TE_BASE
>>> <some_dir>/srv/teamengine
>>>
>>> sh ./test.sh
>>> -source=<some_dir>/srv/teamengine/scripts/wfs/1.1.0/src/main.xml
>>> Exception in thread "main" java.lang.NoClassDefFoundError:
>>> com/occamlab/te/Test
>>> Caused by: java.lang.ClassNotFoundException: com.occamlab.te.Test
>>>           at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>>>           at java.security.AccessController.doPrivileged(Native Method)
>>>           at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>>>           at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>>           at
>>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>>>           at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>> Could not find the main class: com.occamlab.te.Test.  Program
>>> will exit.
>>>
>>> I also tried -source=wfs/1.1.0/src but same issue.
>>>
>>> Best regards
>>> baris
>>>
>>> On 4/23/2013 12:29 PM, Richard Martell wrote:
>>>> Baris,
>>>>
>>>>
>>>> A new teamengine-console module has been added to teamengine. It
>>>> generates the binary CLI distribution that was previously
>>> created when
>>>> building the core module. The most significant change is
>>> the inclusion
>>>> of additional libraries required by TestNG-based suites.
>>>>
>>>> You can build it yourself from source (4.0-beta3-SNAPSHOT)
>>>> <https://svn.code.sf.net/p/teamengine/code/trunk>
>>>>
>>>>
>>>> Note: We always strive to keep the trunk green: "Thou shalt not
>>>> break the trunk!"
>>>>
>>>>
>>>> Alternatively, fetch it from our FTP site (this week only):
>>>>
>>> <ftp://ftp.galdosinc.com/pub/delivery/cite/teamengine-console-
>>> 4.0-beta3-SNAPSHOT-bin.tar.gz>
>>>>
>>>> You don't need to set TE_HOME if you just change to the appropriate
>>>> /bin directory. But do set TE_BASE:
>>>>
>>>> e.g.
>>>>> set TE_BASE=/path/to/te-base      # or modify setenv script
>>>>> test -source=csw\2.0.2\src
>>>> The results should show up in TE_BASE/users/$USERNAME/s000N/.
>>>>
>>>> None of the current CTL suites require any additional
>>> libraries AFAIK (a couple
>>>> of the older ones do). If a suite does have other
>>> dependencies just drop them
>>>> into TE_BASE/resources/lib.
>>>>
>>>>
>>>> -- 
>>>> Richard
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From:
>>>>> cite-forum-bounces+rmartell=galdosinc.com at lists.opengeospatial
>>>>> .org
>>>>> [mailto:cite-forum-bounces+rmartell=galdosinc.com at lists.openge
>>>>> ospatial.org] On Behalf Of BARIS KAZAR
>>>>> Sent: Monday, 22 April, 2013 14:38
>>>>> To: cite-forum at lists.opengeospatial.org
>>>>> Subject: [CITE-Forum] Testing Locally
>>>>>
>>>>> Thanks for the help from Richard and Luis.
>>>>> i still have some more questions.
>>>>>
>>>>> I would like to run TeamEngine CTL suites from command line.
>>>>> Thus, should we extract the contents of
>>>>>
>>> teamengine-core/target/teamengine-core-4.0-beta2-distribution.tar.gzip
>>>>> into a directory and set the corresponding path as $TE_HOME
>>>>> env variable?
>>>>> That tar file was created after "maven install site" command.
>>>>>
>>>>> The automatically generated teamengine-4.0-beta2.pdf file
>>>>> after "maven install site" command says the following:
>>>>> "If a test suite requires any supporting libraries that are
>>>>> not included with the core
>>>>> distribution, these must be added to the
>>>>> TE_BASE/resources/lib directory."
>>>>> That lib dir is not there by default. Should we copy the
>>>>> contents of
>>>>> teamengine-web/target/teamengine-common-libs.tar.gz into
>>> that lib dir?
>>>>> The other thing is that when we got the CTL suites via the
>>>>> export-ctl.sh script, the
>>>>> directory name for WFS came out to be like wfs/1.1.0? (with
>>>>> an extra char at the end) and i am not sure yet this will
>>>>> cause any problems.
>>>>>
>>>>> Best regards
>>>>>
>>>>> _______________________________________________
>>>>> CITE-Forum mailing list
>>>>> CITE-Forum at lists.opengeospatial.org
>>>>> https://lists.opengeospatial.org/mailman/listinfo/cite-forum
>>>>>
>>>
>



More information about the CITE-Forum mailing list