Codi tests documentation and options

[dbauszus-glx]

The xyz/TESTING.md needs to be reviewed and should be referenced in the xyz/DEVELOPING.md document.

1. It should be possible to run the codi tests with just the workspace option, without the need to first setup an ACL, register a user, approve the user, etc.

2. The security strategy test should perhaps be separate from mapp module tests.

3. user [roles] could be spoofed for tests.

4. A POSTGIS test database should be made available for replicating tests. It is possible to dump and restore a data on Postgres hosted with NEON. https://neon.tech/docs/import/import-from-postgres

5. Perhaps we can make the test database available as bak file with instructions for restoring the data.

6. Tests should be focused on modules and only include required modules. eg. The featureFormats requires the featureFields module. Tests for the featureFormats module should not require other modules in the test. The featureFields should be tested individually prior to the featureFormats which require the featureFields module.

7. Is it possible to import assets in tests? Test for synchronous functions should not include await xhr for assets making the test async.