Golang: tests and working directory

unit-testing go working-directory
Jesse Brands picture Jesse Brands · May 24, 2014 · Viewed 36.5k times · Source

I'm writing some unit tests for my application in Go. The tests fail however because it cannot find the configuration files. Normally the binary looks for the configuration files in the working directory under the path conf/*.conf.

I figured that browsing to the directory that has conf/ and running go test in it would solve it, but it still reports that the file system cannot find the path specified.

How can I tell go test to use a certain directory as the working directory so that the tests may actually be executed?

Answer

N8Theo picture N8Theo · Jan 28, 2015

You may be able to use the Caller to get the path to the current test source file, like this:

package sample

import (
    "testing"
    "runtime"
    "fmt"
)

func TestGetFilename(t *testing.T) {
    _, filename, _, _ := runtime.Caller(0)
    t.Logf("Current test filename: %s", filename)
}

Related questions

Mock functions in Go

I'm puzzled with dependencies. I want to be able to replace some function calls with mock ones. Here's a snippet of my code: func get_page(url string) string { get_dl_slot(url) defer free_dl_slot(url) resp, err := …

Read More
How can I do test setup using the testing package in Go

How can I do overall test setup processing which sets the stage for all the tests when using the testing package? As an example in Nunit there is a [SetUp] attribute. [TestFixture] public class SuccessTests { [SetUp] public void Init() { /* Load …

Read More
How to measure code coverage in Golang?

Has anyone succeeded in generating code coverage for Go unit tests? I can't find a tool for that on the web.

Read More