posener

Be Careful with Table Driven Tests and t.Parallel()

We Gophers, love table-driven-tests, it makes our unittesting structured, and makes it easy to add different test cases with ease.

Let’s create our table driven test, for convenience, I chose to use t.Log as the test function. Notice that we don't have any assertion in this test, it is not needed to for the demonstration.

func TestTLog(t *testing.T) {
	t.Parallel()

arsham

go test -run=. -bench=. -benchtime=5s -count 5 -benchmem -cpuprofile=cpu.out -memprofile=mem.out -trace=trace.out ./package | tee bench.txt
go tool pprof -http :8080 cpu.out
go tool pprof -http :8081 mem.out
go tool trace trace.out

go tool pprof $FILENAME.test cpu.out
# (pprof) list <func name>

# go get -u golang.org/x/perf/cmd/benchstat
benchstat bench.txt

webchick

Array
(
    [hook_menu] => 6744
    [hook_uninstall] => 4742
    [hook_perm(ission)] => 4012
    [hook_install] => 3751
    [hook_theme] => 3525
    [hook_schema] => 3003
    [hook_help] => 2465
    [hook_form_alter] => 2273

fzaninotto

<?php

interface Bar {}

class Foo extends Exception implements Bar {}

try
{
    throw new Foo();
} catch (Bar $e) {