This mono repo allows the testing of the various express-session connect modules that are in the public registry. The majority of the connect modules persist to some sort of DB that can be shared with amongst various instances of the nodejs servers so that load balancing is possible. For all but the most trival systems testing is achieved using Docker based services.
The following connect modules are to be tested with the priority being given to those with the highest downloads.
| name | downloads (1000s) | local test package |
|---|---|---|
| connect-redis | 220 | redis-store |
| connect-mongo | 81 | mongo-store |
| memorystore | 41 | lru-memory-store |
| connect-session-sequelize | 31 | sequelize-store |
| session-file-store | 18 | |
| connect-pg-simple | 15 | pg-simple-store |
| express-mysql-session | 12 | mysql-store |
| connect-mongodb-session | 10 | |
| connect-session-knex | 7 | |
| connect-dynamodb | 4 | |
| express-nedb-session | 3 | |
| connect-memcached | 3 | |
| firestore-store | 2 | |
| @google-cloud/connect-firestore | 1 | |
| @google-cloud/connect-datastore | 1 | |
| connect-session-firebase | 1 |
In order to test on the GitHub Actions suite it is necessary to run the express session services as docker images. To that end we need to be able to publish the express store docker images and then we need to be able to load them to test.
- switch to docker actions rather than the hard coded shell scripts
- use the docker bump version script
- create fuller integration tests
- create an artifact for the smoke tests so we do not need to run lerna again
- is it possible to create an artifact for the docker image rather than publishing it
- move example workflows to example folder