| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add streams assert methods to ActionCable channel test case | Sergey Ponomarev | 2018-12-18 | 1 | -4/+45 |
| | | |||||
| * | Fix typos | R.T. Lechow | 2018-10-01 | 1 | -2/+2 |
| | | | | | Fixes some typos. | ||||
| * | Remove Rails 5.0 workaround from ActionCable::Channel::TestCase | Vladimir Dementyev | 2018-09-27 | 1 | -6/+2 |
| | | | | | | | | The hack was merged from action-cable-testing gem by mistake. We don't need it in Rails 6. (cherry picked from commit 92030ec4b4309835ed0e792229984a1f0a044cef) | ||||
| * | Add ActionCable::Channel::TestCase | Vladimir Dementyev | 2018-09-26 | 1 | -0/+275 |
| 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 | |||||
 |
index : rails.git | |
| Mirror of official rails repo with custom fixes. | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |