Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Links #297

Merged
merged 2 commits into from
Jul 11, 2023
Merged

Links #297

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4946bf8
Links
Jul 11, 2023
f916aa2
Links
Jul 11, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions docs/blog/crucial-tests/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ slug: testing-the-dark-scenarios-of-your-nodejs-application
date: 2023-07-07T11:00
hide_table_of_contents: true
title: Testing the dark scenarios of your Node.js application
authors: [goldbergyoni, razluvaton ]
authors: [goldbergyoni, razluvaton]
tags:
[
node.js,
Expand All @@ -28,7 +28,7 @@ But there is a pitfall: most developers write _only_ semi-happy test cases that

Here are a handful of examples that might open your mind to a whole new class of risks and tests

_Side note: I've just released a comprehensive testing course that I've been working on for two years. 🎁 It's now on sale, but only for the month of July. Check it out at [testjavascript.com](https://testjavascript.com/)_
**July 2023: My testing course was launched: I've just released a comprehensive testing course that I've been working on for two years. 🎁 It's now on sale, but only for the month of July. Check it out at [testjavascript.com](https://testjavascript.com/)**

## **Test Examples**

Expand Down Expand Up @@ -489,11 +489,9 @@ beforeAll(() => {
- Test your HTTP client retry mechanism (very easy with nock)
- Test that the DB migration succeed and the new code can work with old records format
- Test DB connection disconnects
- You may find many more examples at my fresh new testing course - [testjavascript.com](https://testjavascript.com)


## It's not just ideas, it a whole new mindset

The examples above were not meant only to be a checklist of 'don't forget' test cases, but rather a fresh mindset on what tests could cover for you. Modern tests are not just about functions, or user flows, but any risk that might visit your production. This is doable only with component/integration tests but never with unit or end-to-end tests. Why? Because unlike unit you need all the parts to play together (e.g., the DB migration file, with the DAL layer and the error handler all together). Unlike E2E, you have the power to simulate in-process scenarios that demand some tweaking and mocking. Component tests allow you to include many production moving parts early on your machine. I like calling this 'production-oriented development'

**My new online testing course -** If you're intrigued with beyond the basics testing patterns, ]consider my online course which was just launched and is 🎁 on sale for 30 days (July 2023)](https://testjavascript.com)
**My new online testing course -** If you're intrigued with beyond the basics testing patterns, [consider my online course which was just launched and is 🎁 on sale for 30 days (July 2023)](https://testjavascript.com)
1 change: 1 addition & 0 deletions docs/blog/which-monorepo/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
slug: monorepo-backend
date: 2022-11-07T11:00
title: Which Monorepo is right for a Node.js BACKEND now?
authors: [goldbergyoni, michaelsalomon]
tags: [monorepo, decisions]
Expand Down
Loading