documentation for this app's tests

[quadrophobiac]

On a fresh download and install of this application tests executed with bundle exec rake fail due to database "bothan_deploy_test" does not exist.
Am I missing something? There's hints that this application uses sidekiq (and also in the procfile). Is this required for the tests to run.
Not sure if its related but bundle exec rake db:migrate also fails with ActiveRecord::NoDatabaseError: FATAL: database "bothan_deploy" does not exist
@pezholio @Floppy @pikesley I don't know which of you worked on this one but could you provide me some pointers here so I can flesh out this repos README accurately?

[quadrophobiac]

bundle exec rake db:create:all followed by bundle exec rake db:migrate establishes a database that can be used but the tests (bundle exec rake) still has 13 out of 14 failures.
7 of those return this error (the ones relating to DB access)

Failure/Error: bothan = Bothan.create(app_id: '34234234', token: 'my-token')
      
      ActiveRecord::StatementInvalid:
        PG::UndefinedTable: ERROR:  relation "bothans" does not exist

[quadrophobiac]

I think the tests are failing due to missing variables from local .env. The heroku instance indicates requirements of github, herokku and redis ENV variables in addition to the pusher and bothan specific variables that are part of bothan's ENV file. Would appreciate some advice on how to understand/determine which variables are required locally in order that I know how to tackle issues like this in future

[Floppy]

only the variables available in travis (look at the build logs to see them if encrypted) are needed for tests to pass, whether locally or anywhere else. Others may be needed (from the Heroku list) for actually running in dev.

[quadrophobiac]

Thanks @Floppy - nabbing those env variables has reduced failing tests to 8, all related to postgres somehow. Then running bundle exec rake db:reset fixed all but one of the remaining specs

[Floppy]

have you run the migration with RAILS_ENV=test?