London | 26-ITP-January | Karla Grajales | Sprint 3 | Practice TDD#1079
Open
Grajales-K wants to merge 8 commits intoCodeYourFuture:mainfrom
Open
London | 26-ITP-January | Karla Grajales | Sprint 3 | Practice TDD#1079Grajales-K wants to merge 8 commits intoCodeYourFuture:mainfrom
Grajales-K wants to merge 8 commits intoCodeYourFuture:mainfrom
Conversation
Grajales-K
added
🏕 Priority Mandatory
Grajales-K
changed the title
…e string repetition logic
- Added an emoji to the error string. - Included try/catch blocks in tests to verify manual error capturing. - Updated Jest assertions to match the new error format.
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
1 participant
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.
Learners, PR Template
Self checklist
Changelist
This project is about how to implement the test cases first. Once we cover all possibilities, we can implement the function step by step. I learned that if we need to optimize our function, the test cases are much easier to adapt if we avoid naming them 'case 1'. 'case 2', etc. Using
module.exportandnpx jest --watchcommand was very helpful to get the real-time feedback on what was happening in our implementation.Questions
Is this how the learning approach should be? Should I study the test cases before solving the function, e.g, in Codewars?
Thank you