Sonichigo

Traditional, or example-based testing specifies the behaviour of your software by writing examples of it, each test sets up a single concrete scenario and asserts how the software should behave in that scenario.

When we discuss software testing, we hear commonly about two things: - "test scenarios" and "test cases". Now, these terms might sound similar to each other, but they play distinct roles in ensuring the quality of software applications. So, let's break it down in simpler terms as we explore the core differences between test scenarios and test cases.

It piqued my interest because it let me record my HTTP dependencies, and hey, it's working out for Google, right? Still, it wasn't all smooth sailing - a couple of issues popped up.

In my journey as a software enthusiast, I've constantly sought innovative ways to unravel the intricacies of my Go applications. Recently, I stumbled upon a fascinating technology that has significantly transformed the way I observe and analyze Go processes.

In this blog post, We'll go on a journey of observing Go processes with eBPF. Let's first get to understand "what is eBPF?"

Test generation for Developers. Generate tests and stubs for your application that actually work!