John Barker j16r

This is a quick sketch of how I think terminology applies to the various kinds of mocking and test doubles that apply in Go.

In practice, the most effective way to mock things in Go is to use an interface, and then to substitute a specialized testing implementation in place of a real one. Wherever a substitute is used, I think this should be called a "double".

There is one specialization of a "double" and that is a "fake" implementation. Fakes can often have real world uses, e.g: "RamDiskDatabase", but are typically

	#!/usr/bin/env ruby

	require 'date'
	day = (Date.today - Date.civil(2021, 6, 19)).to_i
	won = rand(5)+1
	puts "Wordle #{day} #{won}/6"

	tiles = ['🟩','🟨','⬛️']

	(1..won-1).each do \|row\|

	func TestHeightsController_Index(t *testing.T) {
	threshold := big.NewInt(2)
	tests := []struct {
	name string
	status int
	}{
	{"good clients", 200},
	// Hard to do error cases without adding an if with difference setup. could add test helpers...
	}

	#!/usr/bin/env bash -e

	organization=$1

	if [ -z $organization ]; then
	echo "Usage: $0 <organization>"
	echo
	echo "Make sure to specify \$GITHUB_API_TOKEN as an environment variable."
	echo "Acquire one here: https://github.com/settings/tokens"
	echo

	#!/usr/bin/env bash -e

	organization=$1

	if [ -z $organization ]; then
	echo "Usage: $0 <organization>"
	echo
	echo "Make sure to specify \$GITHUB_API_TOKEN as an environment variable."
	echo "Acquire one here: https://github.com/settings/tokens"
	echo

	package main

	import (
	"fmt"
	"runtime"
	)

	func main() {
	s := new(runtime.MemStats)
	runtime.ReadMemStats(s)

	package main

	import "fmt"

	type Level int

	const CODE Level = 1

	type Logger struct {
	}

	package main

	import "fmt"

	type Trait interface {
	String() string
	}

	type Traitable struct {
	}

	package main

	import "fmt"

	func main() {
	collection := []int{1, 2, 3, 4, 5}

	ptr1 := &collection[0]
	ptr2 := &collection[1]
	ptr3 := &collection[2]