protobuf-go/protogen
Joe Tsai 42fa50da34 test.bash: do not run golden tests by default
The golden tests are sensitive to the exact version used:
* Protobuf toolchain since the generated Descriptor is dependendent on protoc
(for example, default json_names were auto-populated in later versions of protoc)
* Go toolchain since the generated .pb.go files is dependent on the exact output
of gofmt and the gzip compression used.

There are other areas where it depends on unstable output, but the above are the
major causes.

Since test.bash ensures that the golden tests are run with exact versions of the
protobuf and Go toolchains, we can ensure that the tests are reproducible across
different developer workstations.

Thus, we add a "golden" build tag to disable them for normal invocations of
"go test ./..." and only run them if test.bash is run.

If test.bash is ever updated with newer versions, the golden testdata can be
updated at the same time.

Change-Id: Ia2b7b039aad2ddaef7652e332215bf9403a6d856
Reviewed-on: https://go-review.googlesource.com/c/142458
Reviewed-by: Damien Neil <dneil@google.com>
2018-10-16 16:49:18 +00:00
..
testdata/go_package protogen, cmd/protoc-gen-go: initial commit 2018-08-22 17:08:04 +00:00
names_test.go protogen: camel-case "Foo.bar" as "FooBar" instead of "Foo_Bar". 2018-10-16 16:18:01 +00:00
names.go protogen: camel-case "Foo.bar" as "FooBar" instead of "Foo_Bar". 2018-10-16 16:18:01 +00:00
protogen_test.go test.bash: do not run golden tests by default 2018-10-16 16:49:18 +00:00
protogen.go protogen: avoid an obscure package name consistency check failure 2018-10-16 16:04:50 +00:00