FIX: Update test cases where is not correct the expected value.

[clouby]

Hey Gleam team,

I noticed that the last two test cases about the armstrong_numbers challenge are not correct to the expected value; those cases should have expected a false value.

Also made some tests with external tools that match the expected value:

Test Cases

• armstrong_number_containing_seven_zeroes_test
• the_largest_and_last_armstrong_number_test

[github-actions]

This PR touches files which potentially affect the outcome of the tests of an exercise. This will cause all students' solutions to affected exercises to be re-tested.

If this PR does not affect the result of the test (or, for example, adds an edge case that is not worth rerunning all tests for), please add the following to the merge-commit message which will stops student's tests from re-running. Please copy-paste to avoid typos.

[no important files changed]

For more information, refer to the documentation. If you are unsure whether to add the message or not, please ping @exercism/maintainers-admin in a comment. Thank you!

[lpil]

Thank you. Could you fix the test please 🙏

[clouby]

@lpil Done ✅ - Let me know if looking good for you, thanks!

[jiegillet]

Sorry to butt in, but I'm pretty sure that this number and the following one are Armstrong numbers (see the comments or example sections, or the full list). I suspect that the site you posted screenshots from uses JS to check the number, and numbers that large are always treated as floats and lose precision.
Similarly, having to introduce Floats in the example solution to make it work seems suspicious to me.

Also, in general, the practice exercises all come from a repo common to all the Exercism tracks, so if there is an issue not linked to the specificity of a track language, it should be solved over there so that all tracks can benefit.

[clouby]

Thanks for your explanation here, I'll take a look further about Armstrong criteria - I'll close it.