Jest test vs it

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

When working on Jest test cases, you might come across two different approaches, as you can see below.
test('if this function succeeds', () => {
expect(1).toBeTruthy();
});
it('should test if this function succeeds', () => {
expect(1).toBeTruthy();
});
As you can see, the above tests are pretty much the same function. However, the naming is different.
Basically, it is an alias for test, so they are functionally the same.
So, what makes it different?
This alias is created to make your tests more readable from a test output point of view.
It can really help make your tests more readable from a readability point of view.
Imagine the second test to use the test function.
test('should test if this function succeeds', () => {
expect(1).toBeTruthy();
});
This immediately sounds a bit off, right?
And these outputs definitely show up weird in your test result, so try to make them look as much like English sentences as possible.
This totally depends on the use case.
I personally use it more for render checks. It often makes more sense.
However, it's totally up to you which one makes more sense for specific use-cases.
Which one do you prefer?
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter