New 42-day free trial Get it now
Smarty

Your Convey needs more focus

Smarty header pin graphic
Updated July 2, 2025
Tags
Smarty header pin graphic

One of the great benefits of TDD/BDD is that you usually don't have to spend much, if any time at all in a debugger. To enter a debugger is to admit a loss of control over the system under test. Even so, there are times when you do need to debug something, even if you're maintaining the discipline.

Lately, most of my coding is in GoLang. Coming from using an IDE almost exclusively to write Python (using PyCharm) and C# (using VS and ReSharper), and knowing how great the visual debugging tools are it's hard to fathom using a console-based debugger for GoLang code. Yes, I know about godbg, which is an amazing tool, but I would rather stay in my test runner of choice, which is GoConvey.

Up until now I would do something like this to achieve debugging:

  • Add log.Println statements where the bugs are
  • Use SkipConvey to limit execution to the test in question (this can get tedious if the test suite is large)
  • Run the tests and observe the output

Or...

  • Add the logging statements
  • Use an init function in the test code to substitute a nil writer to the logger
  • Substitute stdout in the Convey scope that executes the code with logging
  • run the tests and observe the output

Yuck.

Now, there's a better way. It still means putting in some logging, which may or may not be temporary. But, all you have to do now is something like this:

FocusConvey("Subject: Integer incrementation and decrementation", t, func() {
	var x int

	FocusConvey("Given a starting integer value", func() {
		x = 42

		FocusConvey("When incremented", func() {
			x++

			Convey("The value should be greater by one", func() {
				So(x, ShouldEqual, 43)
			})
			FocusConvey("The value should NOT be what it used to be", func() {
				So(x, ShouldNotEqual, 42)
			})
		})
		Convey("When decremented", func() {
			x--

			Convey("The value should be lesser by one", func() {
				So(x, ShouldEqual, 41)
			})
			Convey("The value should NOT be what it used to be", func() {
				So(x, ShouldNotEqual, 42)
			})
		})
		Reset(func() {
			x = 0
		})
	})
})

In this code, only those scopes declared with FocusConvey will be executed, the reset will be ignored. Much easier to toggle for debugging purposes.

Of course, you shouldn't leave the test suite with a bunch of FocusConvey calls lying around. After you fix your code get rid of the Focus and just keep Convey.

Happy debugging!

Subscribe to our blog!
Learn more about RSS feeds here.
Read our recent posts
What to look for in an address data solution: Data accuracy
Arrow Icon
Once you know what capabilities you need, the next challenge is choosing a provider that actually delivers—pun intended. This blog is part of our five-part series, What to look for in an address data solution. Previously, we discussed the need to find an address data solution that understands the importance of speed, scalability, and reliability, enabling you to maintain automated, efficient, and accurate workflows in any industry that deals with addresses. Today, we’ll focus on the hidden costs of inaccurate data, defining and combating the “validation gap”, and why it’s important in any industry.
Empowering finance, healthcare & insurance companies with international autocomplete
Arrow Icon
Address data plays a vital role for finance, healthcare, and insurance companies. When these companies serve customers worldwide, processes like KYC compliance, fraud prevention, and onboarding become even more complicated, making accurate data even more essential. Enter International Address Autocomplete, a form and checkout address-filling feature that saves the day for more than just ecommerce companies based in the US. It’s also great for finance, healthcare, and insurance companies worldwide.
What to look for in an address data solution: Speed, volume, and reliability
Arrow Icon
Not all address tools are created equal. The right platform should do more than validate—it should verify, enrich, and future-proof your data. This blog is part of our five-part series, What to look for in an address data solution. Previously, we discussed the hidden costs of poor address data, including misdeliveries, lost revenue, billing errors, and operational inefficiencies. These creep up because companies mistakenly assume that their CRM or ERP already validates and standardizes addresses.

Ready to get started?