London | 26-ITP-January | Karla Grajales | Sprint 3 | 1-implement-and-rewrite-tests

[Grajales-K]

Learners, PR Template

Self checklist

• I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
• My changes meet the requirements of the task
• I have tested my changes
• My changes follow the style guide

Changelist

In this project, I learned how to implement functions and write comprehensive test cases using assertions and error handling (throw). I also practiced using helper functions to improve test readability and finally transitioned to Jest by exporting the logic as a module.

Questions

Hi, I have a question regarding the testing strategy. When and why is it better to implement manual assertions versus using a framework like Jest? Are there specific rules or industry standards on when to use each approach?
Thank you.

[illicitonion]

This is generally looking really good, well done!

On your question:

Hi, I have a question regarding the testing strategy. When and why is it better to implement manual assertions versus using a framework like Jest? Are there specific rules or industry standards on when to use each approach?

In real life, we almost always use a testing framework - they tend to have lots of convenience things (e.g. as you've seen here expect(...).toThrow(...) is much more convenient to write than having to do a try-catch and failing the test in the try after the code you're testing - you can build these things up yourself, but frameworks exist to do this for you :)

[Grajales-K]

This is generally looking really good, well done!

On your question:

Hi, I have a question regarding the testing strategy. When and why is it better to implement manual assertions versus using a framework like Jest? Are there specific rules or industry standards on when to use each approach?

In real life, we almost always use a testing framework - they tend to have lots of convenience things (e.g. as you've seen here expect(...).toThrow(...) is much more convenient to write than having to do a try-catch and failing the test in the try after the code you're testing - you can build these things up yourself, but frameworks exist to do this for you :)

Hi @illicitonion, that makes a lot of sense. Building manual assertions was a great exercise to understand how testing works under the hood, but I can see how expect(...).toThrow() indeed is much cleaner and more efficient for real-world projects.

Thank you very much for your time.