Ensure failed assertions, and fail-to-run assertions actually fail tests
fix failed assertion caught by #1157 fix
Fixes flapping test; ensure empty queue in setup
Merge pull request #1157 from resque/issue-1157/add-assert-in-work-block-helper

Failed Assertions Don't Fail Tests :rage:
Respect TERM_CHILD setting when not forking

The behavior of TERM_CHILD is desirable even when there is no child
process (using FORK_PER_JOB=false). This patch makes non-forking Resque
workers behave the same way when sent a TERM signal.
Fix travis build failure on 1.8.7
update HISTORY.
Bump version to 1.25.2
Change two TBD releases into actual dates.
Make space in HISTORY for 1.25.3
rake: when BACKGROUND, ensure worker.reconnect after daemonizing
tests: use assert_raises

"assert_raise" was a Test::Unit function that is not available in
Minitest. Switch to the newer Minitest syntax, "assert_raises".

This matches all the other "assert_raises" calls within the test suite.
Merge pull request #1202 from ktdreyer/assert-raises

tests: use assert_raises
Resque::Worker#pid on remote workers via Resque::Worker::find

Se #857.

1. Exceptions in the appropriate test were getting "handled" by the
   worker's block handler, causing failed assertions to be muted.
   Fixes the test.

2. Since we have access to the pid when creating a Worker object
   from Resque::Worker::find, set the pid appropriately.