:
add require sidekiq to the sidekiq.rb
update Gemfile.lock
bump travis-sidekiqs
correct require statement
fix another request
connect to the database
add current user
add current user correctly
add current user correctly
add puts to see were in the condition we are
missing invertted comma
add comments to the worker
I HAVE NO IDEA
Revert "I HAVE NO IDEA"
This reverts commit 8bd1259bf4ea1b479f9391847a4700b7b15efe57.
change the id and source to symbols in the params because siedekiq expects that
add more printout
setup database connection, metrics and notification
correct the test
We can do it, because we use :transaction strategy with DatabaseCleaner,
which starts transaction before each test and rollbacks after it. That
way data before each test is consistent.
The big advantage of such approach is that tests are fast now - we need
to only load Scenario data once.
One of the drawbacks, on the other hand, is that we need to always load
this data, even if no integration tests need running.
We can try to be smart about it and check if any integration tests are
loaded.
