-
-
Notifications
You must be signed in to change notification settings - Fork 195
[all-your-base, leap, hamming] tests are swapped #263
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
Comments
Thanks for reporting that, @NobbZ. I guess I confused the operators when writing it. 😁 This behavior is already fixed in branch test Case{..} = it description assertion
where
assertion = expression `shouldBe` outputDigits
expression = rebase inputBase outputBase inputDigits ...but we only had plans to merge it to Should we fix that now in Edit: |
I've fixed it locally, so I'm fine with whatever you do :) As far as I did rbasso [email protected] schrieb am So., 7. Aug. 2016 um 22:28 Uhr:
|
Yeah basically. We have a separate API that delivers the problem data. It's not a lot of code, but it includes all of the language-specific tracks as submodules, so I have to update the submodules, commit, and deploy, which is still a manual process. I'm sure this could be automated to some degree, but I'm wary of missing something stupid and breaking the site while I'm asleep or traveling. |
By stepwise doing
all-your-base
, I encountered that aJust [1]
was expected but aNothing
got, while my code was only able to returnJust
s at that stage:And I got following test-output (only one out of many):
After changing all occurences of
(~=?)
with(~?=)
in thetest/Tests.hs
I got a more appropriate output in the testrun:The text was updated successfully, but these errors were encountered: