Vladimir Dementyev 8541394e71 Add ActionCable::Channel::TestCase ... ActionCable::Channel::TestCase provides an ability to unit-test channel classes. There are several reasons to write unit/functional cable tests: - Access control (who has access to the channel? who can perform action and with which argument? - Frontend-less applications have no system tests at all–and we still need a way to test channels logic. See also #27191		2018-09-26 22:06:14 -07:00
..
channel	Add ActionCable::Channel::TestCase	2018-09-26 22:06:14 -07:00
connection	Enable `Layout/EmptyLinesAroundBlockBody` to reduce review cost in the future	2018-07-12 21:29:48 +09:00
javascript	Remove thirdparty FIXME	2018-07-25 22:59:11 +02:00
server	Include `ActiveSupport::Testing::MethodCallAssertions` to `ActionCable::TestCase`	2018-06-08 23:29:05 +03:00
stubs	Remove redundant accessors	2018-06-11 16:39:50 +02:00
subscription_adapter	Fix test case to ensure default connection id is filled	2018-09-07 04:00:00 +09:00
client_test.rb	Include `ActiveSupport::Testing::MethodCallAssertions` to `ActionCable::TestCase`	2018-06-08 23:29:05 +03:00
test_helper.rb	Simplify configuring of `ActionCable.server.config.logger` for actioncable tests	2018-08-23 12:36:19 +03:00
test_helper_test.rb	DRY in `assert_broadcasts`	2018-08-23 12:39:03 +03:00
worker_test.rb	Inherit all actioncable's test classes from `ActionCable::TestCase`	2018-06-08 23:23:06 +03:00