-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ada tests #714
Ada tests #714
Conversation
GCOVR code coverage report https://714.url.prtest.cppalliance.org/gcovr/index.html |
930d99d
to
939c7bf
Compare
GCOVR code coverage report https://714.url.prtest.cppalliance.org/gcovr/index.html |
939c7bf
to
f467158
Compare
GCOVR code coverage report https://714.url.prtest.cppalliance.org/gcovr/index.html |
f467158
to
026c79b
Compare
GCOVR code coverage report https://714.url.prtest.cppalliance.org/gcovr/index.html |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #714 +/- ##
===========================================
+ Coverage 97.11% 97.21% +0.10%
===========================================
Files 155 155
Lines 8461 8486 +25
===========================================
+ Hits 8217 8250 +33
+ Misses 244 236 -8
... and 5 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
This PR implements the basic tests from Ada. It replicates the basic tests and a second basic test, which is based on fixtures. The Ada repository has 8 more files with fixtures. I expect we'll have about the same number of conflicts in these files so I'll describe what these conflicts are.
The tests were helpful to find bugs (5 bugs were found over 767 tests). On the other hand, Ada and node.js implement lots of exceptions for corner cases. And their tests are often exploring the very same corner cases we don't have. This means a large number of URLs (473 - 62%) have different expected results in Ada. For instance, modifying URLs in Ada might have different results depending on the scheme or even on whether some components "look like numbers".
So for each case, I had to check if it was really a bug or if the difference was intended behavior. That involved checking the RFC again. Here's a summary of the reasons why the expected results didn't match:
Summary Ada and Boost.URL conflicts
When the expected results don't match, the fixture in this PR includes the reason. In all cases, Boost.URL is coherent with the intended behavior we have decided.