test: add case for odd starting value in Collatz sequence#4039
Closed
titikshit wants to merge 1 commit intoexercism:mainfrom
Closed
test: add case for odd starting value in Collatz sequence#4039titikshit wants to merge 1 commit intoexercism:mainfrom
titikshit wants to merge 1 commit intoexercism:mainfrom
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
Member
|
Hi @titikshit 👋🏽 This problem is a practice exercise that has been pulled from a common repository. The content and tests have been auto-generated. To add, alter, or propose a test, we ask that you open an issue in the forum under |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Adds a missing test case for handling odd-number Collatz inputs.
Motivation
Odd starts (like 25) help surface an easy mistake: using / produces floats, which breaks the integer sequence.
Using // keeps the logic consistent.
This test highlights the issue, and I suggest recommending // in the implementation
Changes
Added test_odd_number_start to verify steps(25) == 23.