19 items tagged ”Testing”

<p>Smarty’s security and confidentiality approach is built around a simple idea: process address data in accordance with customer agreements and relevant privacy requirements, protect it, and limit who (and what) can access it. </p><p>We recognize that you own your compliance requirements, and we’re here to make that easier. Below is a synthesized view of the controls and practices Smarty follows to support compliance, along with details on our Enhanced Data Privacy upgrade, which provides an extra layer of protection for you and your business or organization.

<p>In today's fast-paced tech world, it's essential to gain insights from those who have been in the trenches, building, testing, and creating software that impacts our daily lives. One such individual is Michael Whatcott, a key figure at Smarty. Let's dive into his journey, approach, and the knowledge he's garnered over the years. </p><p>But that’s just Michael's professional bio. To know who Michael is, we’ve asked for some clarification. </p><h2><strong>Explain it to a 10-year-old: What do you do at Smarty?</strong></h2><blockquote><p><i>I work on the tools and systems that make payments, manage subscriptions, and create reports here at Smarty.

<p>It's been said that naming is one of the <a href="https://www. martinfowler. com/bliki/TwoHardThings. html">two hardest problems in computer science,</a> along with cache invalidation and 'off-by-one' errors. (See what I did there?) Do you ever find yourself wondering what policies and practices you could adopt to make your life easier when reading code you wrote months ago? Or maybe you're up at night wishing you knew how to write code in such a way as to maximize adoption and convenience for your users? Well, look no further because we've anticipated the need, solved the problem, and now we're sharing our knowledge and wisdom at no charge, all out of the goodness of our hearts in this comprehensive, totally no-nonsense (nudge, nudge, wink, wink) style guide of Go naming conventions.

<p>One topic that seems to come up repeatedly on Stack Overflow or other online forums is the topic of how to <code>go get</code> private dependencies. Specifically, if I have a private Git repository on Github or Bitbucket, how do I bring that code locally via the <code>go get</code> tool such that automated builds can produce a clean, consistent build without interaction from a user? This problem is largely solved for public Github dependencies but continues to be a challenge for private dependencies.

<p>Writing test functions in Go is easy:</p><pre><code class="language-plaintext">package stuff import "testing" func TestStuff(t testing. T) { t. Log("Hello, World!") } </code></pre><p>Running test functions is also easy:</p><pre><code class="language-plaintext">$ go test -v === RUN TestStuff --- PASS: TestStuff (0. 00s) stuff_test. go:6: Hello, World! PASS ok github. com/smartystreets/stuff 0. 006s </code></pre><p>Preparing shared state for multiple test functions is problematic. The usual recommendation is to use <a href="https://github.

<p>For the purpose of this article, consider the following CSV data, slightly modified from the <a href="https://pkg. go. dev/encoding/csv#exampleReader">docs for <code>encoding/csv</code></a>:</p><pre><code class="language-plaintext">csvData := strings. NewReader(strings. Join([]string{ , , , , }, "\n")) </code></pre><p>Here's how you read the data, line by line, using the <code>Reader</code> provided in that package:</p><pre><code class="language-plaintext">reader := csv. NewReader(csvData) for { record, err := reader.

<p>I was recently <a href="https://github. com/smartystreets/goconvey/issues/360#issuecomment-368348056">asked two interesting questions</a>:</p><ol><li>Why did you move from GoConvey to <a href="https://github. com/smartystreets/gunit">gunit</a>?</li><li>Are you recommending folks do the same?</li></ol><p>These are great questions, and since I'm a co-creator of GoConvey and the principal author of Gunit, I feel responsible for giving a thorough answer. For the impatient, here's the TL;DR:</p><p>Question 1: Why did you move to gunit?</p><blockquote><p>After using GoConvey and feeling consistent friction with that approach, we came up with an alternate approach that was more aligned with what we value in a testing library and which eliminated said friction.

<p>For this installment of the <a href="/blog/tags/testing">Testing in Go series</a> we'll be talking about a grouping of packages that facilitate general-purpose comparisons in various contexts. Since the most common context is testing it seemed like this series was the right place for the discussion. </p><p>We generally refer to these comparison functions as <strong>assertions</strong> (<i>cue ominous background music and spooky sound effects</i>). You may have already read the opinions found on the Golang FAQ related to assertions.

<h2>Introduction</h2><p>TL;DR: Choose an approach to software testing that helps your organization create the best possible end results. That might mean using and/or creating a few tools and/or libraries along the way. Or, maybe not. What follows is a description of what we do at SmartyStreets, couched as a response to <a href="https://danmux. com/posts/thecultofgotest/">Dan Mullineux's equally valid way</a> of doing things. </p><h3>The cost</h3><blockquote><p>A favourite test helper library, with some simple test assertion functions clearly has some value.

<p>I was given the task of setting up a <a href="https://tinc-vpn. org/">tinc</a> VPN so that we could test performance for comparison against other VPN systems. This task took much longer than it should have. For that reason, I am making this post to help me and others remember how to do it again in the future. </p><hr><p>Installing <code>tinc</code> is straightforward enough. You can <a href="https://tinc-vpn. org/download/">download the latest release</a> and build it or install it from your favorite package manager.

<p>Not every server is made equally. On dedicated servers, the hardware varies widely. On virtual and cloud servers, the resource allocations also vary widely. Some servers are CPU-optimized for maximum computing power. Others focus on having a lot of memory. Some servers are built to have a good balance of all system resources. </p><p>Hardware aside, we require many differing tasks of our servers. Some applications are processor hungry, some need large amounts of disk space, while others take up a lot of memory.

<p>For this installment of the <a href="/blog/tags/testing">Testing in Go series</a> I'll share a really nifty way to deal with time in your unit tests. When the behavior you are testing depends on the current time it can be tricky to assert on the results because the current time is a moving target. So, usually we end up resorting to approximations in our assertions that, while functional, always bother me a bit. In some cases, depending directly on the system's current time prevents acceptable test coverage.

<p>I think it's time for a slight detour. In <a href="/blog/go-testing-part-1-vanilla">part 1</a> we covered the basics of testing in go. In <a href="/blog/go-testing-part-2-running-tests">part 2</a> we covered a few slick ways to execute tests. In <a href="/blog/go-testing-part-3-convey-behavior">part 3</a> we covered some of our recent endeavors at Smarty to build on the basics. Toward the end of that post, we went into some detail regarding our approach to assertions. The assertions referenced in the GoConvey project are actually their own separate project that are imported into GoConvey.

<h2>Review</h2><p>Welcome to part 3 of our <a href="/blog/tags/testing">"Testing in Go" series</a>. If you're new here, feel free to <a href="/blog/tags/testing">catch up</a> before reading on. </p><p>In <a href="/blog/go-testing-part-1-vanilla">part 1</a> of this series I eluded to <i>our perceptions</i> of the standard testing tools provided by the Go tool and the standard library and what was missing <i>for us</i>. We all have different expectations of a testing tool and so it's no wonder that <a href="https://github.

<p>Here's part 1 of our <a href="/blog/tags/testing">"Testing in Go" series</a>. </p><h2>Introduction</h2><p>Thinking about trying <a href="https://go. dev/">Go</a>? You won't regret it! It's great that testing is baked into the <a href="https://pkg. go. dev/testing"><code>"testing"</code> package</a> from the standard library and the corresponding <a href="https://pkg. go. dev/cmd/go#hdr-Testpackages"><code>go test</code> command</a> (which has all sorts of useful and interesting <a href="https://pkg.

<p>Here's part 2 of our <a href="https://www. smarty. com/blog/tags/testing">"Testing in Go" series</a>. If you're new, feel free to <a href="https://www. smarty. com/blog/tags/testing">catch up</a> before reading on. </p><hr><h2>Basics</h2><p>You've already learned how to execute tests in Go for a single package. </p><pre><code class="language-plaintext">$ go test </code></pre><p>There's a bit more to it, though. You can run any package from anywhere if you provide the import path. For example, this command runs the actual tests for the "testing" package from the standard library:</p><pre><code class="language-plaintext">$ go test -v testing </code></pre><p>If you've already run <code>go get github.

<p><a href="https://github. com/smartystreets/goconvey/issues/106">You asked for it</a> and <a href="https://github. com/smartystreets/goconvey/issues/144">now you've got it</a>. </p><p>For packages that pass all tests, coverage reports are generated and made available by clicking the package name, which in that case becomes a link (provided you've cleared your browser's cache!). </p><p><img src="https://d3jlqkabnnke2x. cloudfront. net/goconveycoveragebarc7288d4b3c. png" alt="Click the package name" height="316" width="588"></p><p>Right now the coverage command that is run is something like this:</p><pre><code class="language-plaintext">$ go test -covermode=set -coverprofile=&lt;packagename&gt;.

<p>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. </p><p>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.

<p>It's now been a few months since I decided that the kind of testing tools I wanted for Go programming hadn't yet been created (or I just hadn't found them yet. . . ). So, about 4 months ago I started work on GoConvey and a month later came the first release. </p><p>The coolest thing about GoConvey (other than the <a href="https://github. com/smartystreets/goconvey/wiki/Composition"><u>clean DSL</u></a>, comprehensive set of <a href="https://github. com/smartystreets/goconvey/wiki/Assertions"><u>built-in assertions</u></a>, and the fact that it <a href="https://github.