daphne/.gitignore

*.egg-info
*.pyc
__pycache__
dist/
build/
/.tox
.hypothesis
.cache
Initial commit 2015-12-23 20:05:15 +03:00			`*.egg-info`
Ignore Python compiled files 2016-06-15 22:18:56 +03:00			`*.pyc`
			`__pycache__`
Update gitignore 2016-02-09 23:56:18 +03:00			`dist/`
			`build/`
Test against Python 3.4 and multiple Twisted versions (#75) * Test against Python 3.4 and multiple Twisted versions This commit adds tox to be able to test against different dependencies locally. We agreed that Python 3.4 should be supported across all Channels projects, so it is also added with this commit. Furthermore, I think it makes sense to support a broad range of Twisted releases, as users of daphne are not unlikely to have other Twisted code running. It's not feasible to test against all releases since 16.0, and it would require constant maintenance to add new releases as they come out. So I opted to keep things simple for now, and only test against the oldest supported and the current Twisted release. I did consider @jpic's great idea from https://github.com/django/daphne/pull/19 to just use tox to avoid having to duplicate the dependency matrix. But it does lead to slower test runs as it bypasses Travis' caching, and is slightly more verbose. * Require asgiref 1.0 and use receive instead of receive_many As both daphne and asgiref had a 1.0 release, I think it makes sense to require the presumably more stable asgiref 1.0. It's also a good occasion to fix the deprecation warnings when running the tests by switching to receive instead of receive_many. * Document supported Python and Twisted versions 2017-01-31 04:24:17 +03:00			`/.tox`
Full test suite for HTTP requests (#91) * Add Hypothesis for property-based tests Hypothesis: "It works by letting you write tests that assert that something should be true for every case, not just the ones you happen to think of." I think it's well suited for the task of ensuring Daphne conforms to the ASGI specification. * Fix accidental cast to byte string under Python 2 While grepping for calls to str(), I found this bit which looks like a cast to unicode was intended under Python 2. * ASGITestCase - checking channel messages for spec conformance This commit introduces a new test case class, with it's main method assert_valid_http_request_message. The idea is that this method is a translation of the ASGI spec to code, and can be used to check channel messages for conformance with that part of the spec. I plan to add further methods for other parts of the spec. * Add Hypothesis strategies for generating HTTP requests Hypothesis, our framework for test data generation, contains only general so-called strategies for generating data. This commit adds a few which will be useful for generating the data for our tests. Alos see http://hypothesis.readthedocs.io/en/latest/data.html. * Add and convert tests for HTTP requests This commit introduces a few Hypothesis tests to test the HTTP request part of the specification. To keep things organized, I split the existing tests module into two: one concerned with requests, and one concerned with responses. I anticipate that we'll also add modules for chunks and server push later. daphne already had tests for the HTTP protocol. Some of them I converted to Hypothesis tests to increase what was tested. Some were also concerned with HTTP responses, so they were moved to the new response module. And three tests were concerned with proxy behaviour, which I wasn't sure about, and I just kept them as-is, but also moved them to the request tests. * Fix byte string issue in Python 2 Twisted seems to return a byte string for the client and server IP address. It is easily rectified by casting to the required unicode string. Also added a test to ensure this is also handled correctly in the X-Forwarded-For header parsing. * Check order of header values I'm in the process of updating the ASGI spec to require that the order of header values is kept. To match that work, I'm adding matching assertions to the tests. The code unfortunately is not as elegant as I'd like, but then it's only a result of the underlying HTTP spec. * Suppress warning about slow test The kitchen sink test expectedly can be slow. So far it wasn't slow enough for hypothesis to trigger a warning, but today Travis must've had a bad day. I think for this test is is acceptable to exceed hypothesis' warning threshold. 2017-03-15 00:12:07 +03:00			`.hypothesis`
			`.cache`