-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delayed Job Tests #493
Delayed Job Tests #493
Conversation
…rent delayed job integration
I've taken this up, fixed the existing Maze-tests and added a couple of features to the Delayed job tests. As these tests aren't currently running on CI, reviewers should manually run the |
features/delayed_job.feature
Outdated
Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa" | ||
And I set environment variable "MAZE_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa" | ||
And I configure the bugsnag endpoint | ||
And I generate the gem and put it in "delayed_job" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ben has done this in env.rb and I think I prefer that approach. Perhaps we should look at doing the same here.
Add integration tests for the delayed job integration.
I've added a step to maze to be able to build the current gem and put that into the test docker container. At the moment that invalidates the build because I'm guessing the gem contains the build time - so we need to fix that.
Once we have the framework up and running adding the rests of the tests should be easy.