pelias/api - api - CogtoSrc

2542 Commits

67 Branches

133 Tags

4.7 MiB

Tree: 19eb0b57d1

Commit Graph

Author	SHA1	Message	Date
Julian Simioni	8f159ceda7	chore(tests): Update test running script with latest info Use npx instead of calling binaries in node_modules, and link to relevant issue. Connects https://github.com/pelias/pelias/issues/744	6 years ago
Julian Simioni	d98973c21f	Handle fatal errors in unit tests Due to the way our unit tests are run, a fatal error in the API code that causes the node process to quit with an error will not be picked up by `tap-dot`, and the unit tests will still return a passing status code. This is due to the way status codes from pipes are handled by default. Fortunately, there is an ["unofficial bash strict mode"](http://redsymbol.net/articles/unofficial-bash-strict-mode/) that helps fix this sort of thing, and by running our unit tests with a few tweaks we can ensure that any failure in the unit tests is captured.	9 years ago

Author

SHA1

Message

Date

Julian Simioni

8f159ceda7

chore(tests): Update test running script with latest info

Use npx instead of calling binaries in node_modules, and link to
relevant issue.

Connects https://github.com/pelias/pelias/issues/744

6 years ago

Julian Simioni

d98973c21f

Handle fatal errors in unit tests

Due to the way our unit tests are run, a fatal error in the API code
that causes the node process to quit with an error will not be picked up
by `tap-dot`, and the unit tests will still return a passing status
code. This is due to the way status codes from pipes are handled by
default.

Fortunately, there is an ["unofficial bash strict mode"](http://redsymbol.net/articles/unofficial-bash-strict-mode/)
that helps fix this sort of thing, and by running our unit tests with a
few tweaks we can ensure that any failure in the unit tests is captured.

9 years ago

2 Commits (19eb0b57d1bc5d2bd12fd87e8be5397458a2b4e2)