Is that the only test you have, or are there more?

It should definitely work.

I'm guessing you don't have system call module installed, do you?

https://github.com/gopherjs/gopherjs/blob/master/doc/syscalls.md

It's possible something we changed more recently has made it required for tests to run, or perhaps it's always been that way. I don't know, because I always have it installed, and gopherjs test works for me. It'd be nice to document this though.

For reference, this is what my output is:

$ gopherjs test
PASS
ok  	_/Users/Dmitri/Dropbox/Work/2013/GoLand/src/github.com/shurcooL/play/31	0.458s
$ gopherjs test -v
=== RUN   TestExample
--- PASS: TestExample (0.00s)
PASS
ok  	_/Users/Dmitri/Dropbox/Work/2013/GoLand/src/github.com/shurcooL/play/31	0.469s
$ 

(I'm not sure why it's printing the full path instead of import paths though...)

Is that the only test you have, or are there more?

Correct, just that test. No more.

I'm guessing you don't have system call module installed, do you?

Ok, I gave that a shot and it fixed it. My output is now:

$ gopherjs test
gopherjs: Source maps disabled. Use Node.js 4.x with source-map-support module for nice stack traces.
PASS
ok  	github.com/gopherjs/vecty/example	0.326s
$ gopherjs test -v
gopherjs: Source maps disabled. Use Node.js 4.x with source-map-support module for nice stack traces.
=== RUN   TestExample
--- PASS: TestExample (0.00s)
PASS
ok  	github.com/gopherjs/vecty/example	0.334s

I don't know why I still get the Node.js 4.x warning when my node --version reports v7.9.0 though.

I'm almost certain gopherjs test worked previously without installing the syscall module (I have never installed it in the past AFAIK). So probably a regression, would be my bet.

I'm almost certain gopherjs test worked previously without installing the syscall module (I have never installed it in the past AFAIK). So probably a regression, would be my bet.

We should document this new requirement. It might be worth it to investigate if it's avoidable. The new requirement might be due to recent enhancements, and so it may be unavoidable. Filed #626 for that.

I don't know why I still get the Node.js 4.x warning when my node --version reports v7.9.0 though.

Well, that's a fail on the warning message text. Filed #627 to improve the text. The issue is you need source-map-support module installed. Here, I've highlighted the important part you're missing:

gopherjs: Source maps disabled. Use Node.js 4.x with source-map-support module for nice stack traces.

See the 3rd paragraph of https://github.com/gopherjs/gopherjs/#installation-and-usage for installation instructions of source-map-support module.

This issue forked into #627, which is already resolved, and #626, which is tracking the specific task there.

It looks like everything here is done, so we can close this, correct? /cc @slimsag

sgtm