amida-tech / greyscale

Indaba - Turn knowledge into data :earth_africa: :earth_asia: :earth_americas:
http://indaba.amida-tech.com
Other
8 stars 4 forks source link

Feature/inba 990 jf trim tables #512

Closed jmfadeley closed 2 years ago

jmfadeley commented 5 years ago

What does this PR do?

Removes various tables, controllers, tests, functions and files that are not needed by our current product, reducing the complexity and "red herrings" of Greyscale.

Related JIRA tickets:

Did the user.integration, discussion.integration and task.integration tests pass? Test can be run with:

node_modules/.bin/mocha test/user.integration.js test/discussion.integration.js test/task.integration.js --bail -t 10000

users.integration.js works but the other two will not and are unlikely to have ever did. This is because they do not factor in the importance of creating the project first, then the product. Because this is a reduction in code, it did not touch upon these particular areas enough to merit fixing tests just yet.

How should this be manually tested?

Go into your database instances. Completely wipe out your Indaba database and recreate it blank. Then in amida-auth-microservice, wipe out the users other than Admin. If you set your auth service admin's password with AUTH_SERVICE_SEED_ADMIN_PASSWORD, be sure to set that in Greyscale as well.

Under greyscale\backend, run yarn seed. Then run yarn start. In another terminal, run yarn test-seed.

Check that 29 tables are generated in the develop or testorg namespace for Indaba's database.

Regression test Indaba entirely. Record any bugs.

Background/Context

Screenshots (if appropriate):