Let's talk about software testing

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.
Hey Chris, you have actually talked about software testing. this article surely gonna help young developers. keep writing like this. waiting for your next article. next time try to cover topic Top software testing company in USA or QA testing companies in USA to get users know about it. just given idea.
In fact, it seems to me that you can use any common software because they work the same way. By the way, I would also like to say that the organization of the development process of its implementation is also an important issue. For example, you can find more information here qawerk.com/blog/software-testing-life-cycle-step-step-guide/ If you have ever thought about business tools, I think you need to acquire more knowledge in this area.
Glad you enjoyed the article
Yess! Please! Just like with your TypeScript series, I expect to learn a lot!!
Way to go Chris!
A lot more articles coming out on this 💖
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...

Software testing seems to be one of the most opinionated things in the software ecosystem. Some people swear by it and only do TDD (test-driven development), while others wing it and see what happens.
I'm not here to tell you which one to pick, as it's personal and dependent on your time/project/and many more factors.
But let's take a look at what testing can do for you.
Before diving into this in-depth, let's look at which types of testing we'll be looking at.
Most of us will have at least done manual testing, which often means you create a system/feature and manually test different options to see if it works.
This is common regardless of the other tests you might have and is often needed to verify the initial product.
But we can enhance these manual tests by introducing automated tests. The significant part about these is that they are created once run forever. It means it initially takes us some setup time, but we can keep running them and see no regression or bugs were introduced.
In the automated section, we have many different approaches to testing.
I won't be going over all of them, so here are some well-used ones.
Unit testing Unit tests are the simplest form of automated tests. They are super low level and test a "unit", which can be one function, one component, or even one interaction. The idea is to have them as small and quick as possible so we can test many small tests relatively fast and cheap.
Integration tests These are used to test integrations with external factors, such as your database, user system, or external APIs. They often require mocks of these external systems and are considered heavier to run.
Functional tests These are kind of enhancements to the integration tests, where integrations only care about data coming from a connection. Functional tests take it one step further and want the data to display correctly.
So an example could be:
End to end tests This kind of testing is there to validate user flows. We want to verify a user flows through a program correctly. This can even include loading states, disabling a button, and showing a result from a form. These tests are super valuable and quite expensive as they take a lot of resources and take longer to set up.
There are many more types of testing, and depending on your needs, they might be even more important.
However, for this basic introduction, I want to leave it here. Do let me know what your favorite combination of tests is and how you go about automating it.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter