chore(blog): some fixes in node:test series (#412)

Signed-off-by: mateonunez <mateonunez95@gmail.com>
mateonunez · Jan 23, 2024 · d6f5f0d · d6f5f0d · vercel · Jan 23, 2024
1 parent 874d08a
commit d6f5f0d
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/articles/you-should-use-node-test-act-one.mdx b/articles/you-should-use-node-test-act-one.mdx
@@ -1,7 +1,7 @@
 ---
 title: 'You should use `node:test` - Act One'
 date: 2024-01-06T13:00:00.000Z
-updated: 2024-01-08T19:35:00.000Z
+updated: 2024-01-23T02:35:00.000Z
 description: >-
   My personal experience moving from different testing frameworks to
   the new Node Test Runner. Act One.

diff --git a/articles/you-should-use-node-test-act-two.mdx b/articles/you-should-use-node-test-act-two.mdx
@@ -1,10 +1,10 @@
 ---
 title: 'You should use `node:test` - Act Two'
-date: 2024-01-10T13:00:00.000Z
-updated: 2024-01-10T13:00:00.000Z
+date: 2024-01-23T02:35:00.000Z
+updated: 2024-01-23T02:35:00.000Z
 description: >-
-  My personal experience moving from different testing frameworks to
-  the new Node Test Runner. Act Two.
+  In this article I'm going to talk about Mocks and Reporters using the new Node Test Runner.
+  This is the second article of the series "You should use `node:test`". If you haven't read the first article, I recommend doing so before reading this one.
 tags:
   - node
   - test