mirror of
https://github.com/mperham/sidekiq.git
synced 2022-11-09 13:52:34 -05:00
68f09786ff
This test doesn't assert anything about the test data itself. Therefore using a regular object is fine. This also fixes the build for Rubinius. The problem is that a minitest mock object removes all kinds of methods that should be there. Since exception_data is for example used in an array later on, it should respond to methods like equal? and == in order to be able to behave properly in an array. In MRI you can get away with this, because once you go into C land, you don't go back to Ruby until you're done. This means you can remove methods that data structures normally depend on without MRI breaking. |
||
|---|---|---|
| .. | ||
| config.yml | ||
| fake_env.rb | ||
| helper.rb | ||
| test_api.rb | ||
| test_cli.rb | ||
| test_client.rb | ||
| test_exception_handler.rb | ||
| test_extensions.rb | ||
| test_fetch.rb | ||
| test_middleware.rb | ||
| test_processor.rb | ||
| test_redis_connection.rb | ||
| test_retry.rb | ||
| test_scheduling.rb | ||
| test_stats.rb | ||
| test_testing.rb | ||
| test_testing_inline.rb | ||
| test_web.rb | ||