Loading...Please purchase the course to watch this video.
Full Course
Advanced testing in Go is essential for ensuring both performance and reliability in applications. This module focuses on several key techniques, beginning with benchmark tests that allow developers to evaluate the performance of their code by comparing different algorithms. It then shifts to end-to-end testing for CLI applications, tackling common challenges and presenting effective methods to ensure applications behave as intended from a user's perspective. The module concludes by introducing test helpers, which streamline the testing process and alleviate some of the complexities developers face. These strategies collectively enhance the robustness of Go applications and promote better coding practices.
No links available for this lesson.
In this module, we're going to take a look at how we can perform some advanced testing when it comes to Go. We're going to begin this module by taking a look at benchmark tests, which is a really powerful tool when it comes to Go to be able to test the performance of your code. In order to do this, we're going to take a look at the algorithms we implemented in the last module, comparing them to the ones that we implemented earlier on in the course, to see which one is actually going to be more performant.
Afterwards, we then move on to end-to-end testing when it comes to CLI applications. Which is something that is sometimes considered difficult to do, but we're going to take a look at a couple of ways I like to do this, or I like to perform end-to-end tests. And through doing so, we'll add a whole suite of tests to make sure that our application works as it would if we were a user.
Lastly, we then round off this module in order to create something called test helpers, which can make it much easier for us to write test code. It's a shame we're writing it at the end of this testing module, but it's good for us to understand the pain that we're trying to solve through this solution.
So with that, let's jump on into our first lesson, which is on benchmark testing.