Closed
Description
The gopherjs test command fails when I specify an explicit path, while this works with standard go test. A simple proof:
$ go test
PASS
ok github.com/flimzy/flashback 0.003s
$ go test .
ok github.com/flimzy/flashback 0.005s
Similar tests with gopherjs in another directory:
$ gopherjs test
PASS
warning: system calls not available, see https://github.com/gopherjs/gopherjs/blob/master/doc/syscalls.md
ok github.com/flimzy/flashback/webclient/pages/all 0.319s
$ gopherjs test .
import ".": import relative to unknown directory
Of course testing '.' isn't that useful, that just proved a simple test case. The same happens if I specify a full path:
$ go test ./couch/
ok github.com/flimzy/flashback-server/couch 0.010s
And with gopherjs:
$ gopherjs test ./webclient/pages/all/
import "./webclient/pages/all/": import relative to unknown directory