| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
* Move Rack::MockRequest/Response into dedicated files.
At some point I think we want to improve the implementation of `Rack::Mock`
in a separate gem. So let's be consistent with naming these files to avoid
clobbering namespace in the future.
|
| |
|
|
|
|
| |
Also, update CHANGELOG with other spec changes made since 2.2.
Implements #1592
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add test:separate task to test run each test file separately.
This is to test that directly requiring a rack component will work.
With test:separate, the test helper will not require rack, and each
test file should call separate_testing with a block that uses
require_relative to only require that component being tested.
Add the appropriate relative requires to get all tests passing
when run separately.
Note that this isn't foolproof. In many cases, the tests use
Rack components that are not under test (such as lint and mock),
and both of those other other rack components, so it's possible
the tests are loading hidden dependencies. I attempted to check
each component to try to find the hidden dependencies, but it is
certainly possible I missed something.
Implements #1621.
|
| |
|
|
|
|
| |
For some reason, the test helper was only used by a single spec file.
This uses it for all spec files. While here, rely on autoload
loading the libraries instead of loading everything manually.
|
| |
|
|
| |
Global expectations have been deprecated in minitest and will start fail in the upcoming major release. Right now it results in multiple warnings. We need to allow them explicitly. Also fixing spacing style in gemspec.
|
| | |
|
| |
|
|
| |
See https://github.com/rack/rack/issues/1243 for history of this task
|
| |
|
|
|
| |
I still can't run some of the tests, so they might have problems. I'll
leave it to the CI to catch them.
|
| | |
|
| | |
|
| |
|
|
|
| |
This commit avoid warn message
Enumerator.new without a block is deprecated; use Object#to_enum
|
| |
|
|
| |
* StringIO is a better choice than a struct here.
|
| | |
|
| | |
|
| |
|
|
| |
Update tests for Directory, ETag, File and Head.
|
| |
|
