Integration Testing

[simon-leech]

Integrity Test

The integrity test forms the basis for layer/location testing on an application and can be ran either locally or on a deployed application.

Requirements
The integrity test should loop through every locale available to that user and run the tests.
The tests should attempt to do these things:

• Turn on every layer accessible to the user
• Select a location on every layer accessible to the user (turning on all dataviews too)
• Add a new location on every editable layer accessible to the user
• Delete that new location on every editable layer accessible to the user
• Turn on all filters on every layer accessible to the user
• Turn on all themes on every layer accessible to the user
• Run the Template Test on the Workspace API to check for failing or missing templates
• Each test should return a pass or fail that is stored to the layer describe.
• This includes errors for failing themes and failing filters.

Nice to Haves

• Ability to test the gazetteer by just providing a 'test' word and checking for any errors.
• Ability to check for cloudinary key provision

[dbauszus-glx]

@simon-leech I don't think integration tests should be working like this.

The integration test doesn't test the mapp library. Ie whether an entry module is able to process the data format or whether openlayers is able to render a style. We need test for this with controlled workspaces.

Neither should the integration test be whether roles work as they are expected to work. There are seperate CLI tests for this with controlled workspaces.

For me the integration test should be whether a layer configuration works. Can a geometry be requested in the right format. Does the style parser run. Does a location get request return json. Is it possible to insert a location. Modify this location, and then delete the location.

Are any references fields accessible.

Are any referenced templates accessible.

DBS connections themselves should be tested in the CLI.

It should be possible to run these test from a plugin interface for individual layers.

It should be possible to run these tests for all layers in a locale.

These tests should probably not run for dozens or hundreds of locales but be executed for individual locales.

[simon-leech]

Step 1: Utility - Layer

• Run styleparser to see configuration warnings;
• Data does not need to be displayed on the mapview, we are testing the connections and data returned;
• Request wkt which gets geometry plus all field required - one test rather than looping over every theme (check if we have this query, requires a limit);

Step 2: Plugin

• Amend existing plugin (button that opens a dialog, that lets you select a layer or click all to run against all);
• Accessible to Admins Only;
• Allow Admin to generate a user token for certain roles;

Step 3: Utility - Location

• Get location from the layers to check they work too;