-
-
Notifications
You must be signed in to change notification settings - Fork 229
crypto-square wrong tests #97
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
Yea, you're correct on that. It appears everybody in this track just followed the tests and didn't pay much attention to the readme. Would you like to fix it? |
I shamelessly imitated the JavaScript track while implementing the C++ track 😺 |
@patricksjackson OK, I could give it a try. I'm not sure about the time frame as I came across it while implementing the D track and my main focus is right now on that. |
There's a ginormous discussion about this over in the metadata repo: exercism/problem-specifications#190 We have a canonical data set here, I think: https://github.com/exercism/x-common/blob/master/crypto-square.json |
Oops, this is still an issue. I'm looking into it. The correct test suite is now located here: https://github.com/exercism/problem-specifications/blob/master/exercises/crypto-square/canonical-data.json |
Hi,
I think that the last 2 tests for the crypto-square problem are wrong. You can verify that by
stacking the segment in output of the normalized cipher text which should yield the plaintext in
normalized form:
E.g.
Correct
Also the following result
msemoa anindn inndla etltsh ui
does not satisfy the property stated in the README
The text was updated successfully, but these errors were encountered: