Originally at 2014-10-07T12:27:49Z by Herbert Vojčík
The problem is, they often need browser environment to run.
Or, develop a convention for splitting UI-based and UI-agnostic tests so the latter can be run in command line (and therefore travis or anything else).
Originally at 2014-10-07T12:27:49Z by Herbert Vojčík
The problem is, they often need browser environment to run.
Or, develop a convention for splitting UI-based and UI-agnostic tests so the latter can be run in command line (and therefore travis or anything else).
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5134578-find-a-way-to-run-unit-tests-for-amber-projects-in-travis?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github).
</bountysource-plugin>
Originally at 2014-10-07T12:27:49Z by Herbert Vojčík
The problem is, they often need browser environment to run.
Or, develop a convention for splitting UI-based and UI-agnostic tests so the latter can be run in command line (and therefore travis or anything else).
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Closing, not using travis in Amber itself as it is github only.