diff options
| author | bors-servo <lbergstrom+bors@mozilla.com> | 2016-01-14 08:20:05 +0530 |
|---|---|---|
| committer | bors-servo <lbergstrom+bors@mozilla.com> | 2016-01-14 08:20:05 +0530 |
| commit | 9c713cb4688f1a1729ada64846fac2d8426b1ef4 (patch) | |
| tree | ba90e872eede527ef53627243694d428f611de65 /python/tidy.py | |
| parent | b26c7bd7ea92bdbf7cdcaa0e3d826a880b9cd0ca (diff) | |
| parent | 5a8c5337550ccac3ec04cd74a6e1372eaf8981bc (diff) | |
| download | servo-9c713cb4688f1a1729ada64846fac2d8426b1ef4.tar.gz servo-9c713cb4688f1a1729ada64846fac2d8426b1ef4.zip | |
Auto merge of #9298 - nikkisquared:test_fetch, r=KiChjang
Implement a basic test for Fetch
As per @jdm's suggestion that I start minimally testing the Fetch protocol to catch any errors, I wrote a very simple test that just calls Fetch and checks that the response isn't a network error. I've made changes as necessary for every failure I encountered, although this doesn't mean the implementation is faultless yet.
As always, I look forward to any feedback for improvements regarding the test itself, the changes to the fetch files I've made, and anything that I missed and should update.
<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9298)
<!-- Reviewable:end -->
Diffstat (limited to 'python/tidy.py')
0 files changed, 0 insertions, 0 deletions