This guide covers built-in mechanisms in Amber for testing your application.
With this guide you will learn:
- Amber testing terminology
- How to write unit, functional, integration, and system tests for your application.
- Amber makes it very easy to test your application. Amber generates skeleton test code when you generate your controllers, models.
- Tests ensure your application adheres to the specifications it was built for.
- Tests help and guide you through a code refactor.
- Amber tests can also simulate browser requests and thus you can test your application's response without having to test it through your browser.
Amber was built with testing in mind. The first time you generate an Amber application using
amber new your_app_namea
specdirectory is generated. The contents of this directory looks as follow.
modelsdirectories are meant to hold tests for view helpers, mailers, and models, respectively. The
controllersdirectory is meant to hold tests for controllers, routes, and views. The integration directory is meant to hold tests for interactions between controllers.
By default every Amber application generates with three environments:
Each environment's configuration can be modified similarly. In this case, we can modify our test environment by changing the options found in
Your tests are run under AMBER_ENV=test.
Guides for other tests like Controller tests, Integration tests and Model testing are work in progress...