The -cpuprofile flag should work with Test* functions and there is no need to change them to be Benchmark functions. One caveat is that if the test function ends very quickly, it's possible that the execution is not sampled at all. (The current cpu profile rate is 100Hz.)

Maybe that's why renaming Test functions to Benchmark functions cause to capture the samples - benchmark framework may call the benchmark functions multiple times under the hood, so some samples are captured.

With go tool pprof cpu.prof, running web gives me this: (go version go1.9.2 darwin/amd64)

Exact command:

go test \
  -timeout 20m \
  -v \
  -coverprofile="coverage-\${pkg//\//-}.out" \
  -cpuprofile cpu.prof -bench .  "\$pkg";

The -bench flag used in the profile makes only Benchmark* functions run.
Also, see my previous comment - if the tested function is a trivial function to run, it's unlikely that any meaningful sample is collected.

@hyangah have you tried it yourself? I get the exact same empty output with this command:

go test \
  -timeout 20m \
  -v \
  -coverprofile="coverage-\${pkg//\//-}.out" \
  -cpuprofile cpu.prof  "\$pkg";

The tests are non-trivial, many of which take a few seconds to run.

Yes, here is the profile output from tests in src/runtime/trace

The .prof file was being overwritten by another .prof for a package with no tests.