README
¶
GopherJS Protobuf binding automated tests
Synopsis
We have Qunit tests written in the GopherJS client in ./client/.
We have a server running the gRPC backend and hosting the GopherJS client in ./server/.
We have a Chromedriver driven browser integration testing setup
that loads the GopherJS client page and checks that there were 0 failures,
courtesy of ginkgo, gomega and agouti.
Simply running ginkgo . starts the server hosting the GopherJS unit test client,
loads the page in Chromedriver using agouti, parses the number of failures and
if it's anything other than 0, the entire test fails.
Requirements
- Chromedriver
- Google Chrome 62+
- ginkgo (
govendor install +program,vendor)
Running
$ make test
Directories
¶
| Path | Synopsis |
|---|---|
|
proto/test
Package test is a generated protocol buffer package.
|
Package test is a generated protocol buffer package. |
|
proto/multi
Package multitest is a generated protocol buffer package.
|
Package multitest is a generated protocol buffer package. |
|
proto/test
Package test is a generated protocol buffer package.
|
Package test is a generated protocol buffer package. |
|
proto/types
Package types is a generated protocol buffer package.
|
Package types is a generated protocol buffer package. |
Click to show internal directories.
Click to hide internal directories.