Set-up the environment.¶

1. Clone the repository.

   git clone https://github.com/geoserver/geoserver.git
   

2. Go to cite directory.

   cd geoserver/build/cite
   

3. Inside you will find a structure, like below, with a list of directories which contains the name of the suites to run.

   cite
   |-- forms
   |-- geoserver
   |-- run-test.sh
   |-- wcs10
   |-- wcs11
   |-- wfs10
   |-- wms11
   |-- wms13
   |-- wfs11
   |-- interactive
   |-- logs
   |-- docker-compose.yml
   |-- postgres
   |-- README.md
   `-- Makefile
   

Running the suite tests.¶

There are 2 ways to run the suites. One is running with make that will automate all the commands, and the second one is running the test through WebUI:

1. Running it through Makefile:

   • run make in the console, it will give you the list of commands to run.

     make
     

   • the output will like this:

     clean: $(suite)         Will Clean the Environment of previous runs.
     build: $(suite)         Will Build the GeoServer Docker Image for the Environment.
     test: $(suite)      Will running the Suite test with teamengine.
     webUI: $(suite)              Will running the Suite test with teamengine.
     

   • Choose which test to run, this is an example:

     Warning

     The first Docker build may take a long time.

     suite=wcs10
     

     Note

     Valid values for the suite parameter are:

     • wcs10

     • wcs11

     • wfs10

     • wfs11

     • wms11

     • wms13

   • Choose which GeoServer war file to test by setting the war_url environment variable inside the Makefile, ex:

     war_url = "https://build.geoserver.org/geoserver/main/geoserver-main-latest-war.zip"
     

   Note

   if you don’t want to do it inside the Makefile you have the option of adding the variable in the command when you build the docker images.

   • To clean the local environment.

     make clean
     

   • To build the geoserver docker image locally.

     make build suite=<suite-name>
     

   • Alternative, with the war_url variable include:

     make build suite=<suite-name> war_url=<url-or-the-geoserver-war-file-desired>
     

   • To run the suite test.

     make test suite=<suite-name>
     

   • To run the full automate workflow.

     make clean build test suite=<suite-name>
     

Requirements:¶

• GeoServer running

• teamengine

• PostgreSQL

• PostGIS

1. Prepare the environment:

   • login to postgresql and create a user named “cite”.

   createuser cite;
   

   • Create a database named “cite”, owned by the “cite” user:

   createdb cite own by cite;
   

   • enter to the database and enable the postgis extension:

   create extension postgis;
   

   • Change directory to the citewfs-1.0 data directory and execute the script cite_data_postgis2.sql:

   cd <path of geoserver repository>
   psql -U cite cite < build/cite/wfs10/citewfs-1.0/cite_data_postgis2.sql
   

   • Start GeoServer with the citewfs-1.0 data directory. Example:

   Important

   If the postgresql server is not in the same host of the geoserver, you have to change the <entry key=”host”>localhost</entry> in the datastore.xml file, located inside each workspace directory. ex.

   Note

   <path of geoserver repository>/build/cite/wfs10/citewfs-1.0/workspaces/cgf/cgf/datastore.xml

   cd <root of geoserver install>
   export GEOSERVER_DATA_DIR=<path of geoserver repository>/build/cite/wfs10/citewfs-1.0
   ./bin/startup.sh
   

2. Start the test:

   make webUI
   

3. Go to the browser and open the teamengine webUI.

   • click on the Sign in button and enter the user and password.

   • after creating the session, and chosing the test, enter the following parameters:

   1. Capabilities URL http://<ip-of-the-geoserver>:8080/geoserver/wfs?request=getcapabilities&service=wfs&version=1.0.0

   2. Enable tests with multiple namespaces tests included

      

Requirements:¶

• GeoServer

• teamengine

• Posgresql

• PostGIS

1. Prepare the environment:

   • login to postgresql and create a user named “cite”.

   createuser cite;
   

   • Create a database named “cite”, owned by the “cite” user:

   createdb cite own by cite;
   

   • enter to the database and enable the postgis extension:

   create extension postgis;
   

   • Change directory to the citewfs-1.1 data directory and execute the script dataset-sf0-postgis2.sql:

   cd <path of geoserver repository>
   psql -U cite cite < build/cite/wfs11/citewfs-1.1/dataset-sf0-postgis2.sql
   

   • Start GeoServer with the citewfs-1.1 data directory. Example:

   Important

   If the postgresql server is not in the same host of the geoserver, you have to change the <entry key=”host”>localhost</entry> in the datastore.xml file, located inside each workspace directory. ex.

   Note

   <path of geoserver repository>/build/cite/wfs11/citewfs-1.1/workspaces/cgf/cgf/datastore.xml

   cd <path of geoserver install>
   export GEOSERVER_DATA_DIR=<path of geoserver repository>/build/cite/wfs11/citewfs-1.1
   ./bin/startup.sh
   

2. Start the test:

   make webUI
   

3. Go to the browser and open the teamengine webUI.

   • click on the Sign in button and enter the user and password.

   • after creating the session, and chosing the test, enter the following parameters:

   1. Capabilities URL http://<ip-of-the-geoserver>:8080/geoserver/wfs?service=wfs&request=getcapabilities&version=1.1.0

   2. Supported Conformance Classes:

      • Ensure WFS-Transaction is checked

      • Ensure WFS-Locking is checked

      • Ensure WFS-Xlink is unchecked

      

   3. GML Simple Features: SF-0