Frequently Asked Questions (by someone, but not really sure where or how these questions got asked...)
- What does GoaTE stand for?
- Greatest of all Test Engines. A bit arrogant perhaps, but it is the GoaTE after all.
- What does GoaTE do?
- GoaTE does several things. It started as a way to introduce a customizable DSL for test data. It has evolved to also provide a standard interface that can be used to provide wrappers around common test frameworks. It also introduces a few patterns, such as employees and expectations, to improve and add some pretty sweet functionality (like retries with timeouts for validations).
- How do I use GoaTE?
- You import the libraries you want and start using them.
- Does GoaTE work with [insert random library/framework]?
- Sure. GoaTE is really just a library. There may not be a specific GoaTE interface defined for the library/framework, but it won't interfer with it. And the existing patterns defined may be applied to your usage of the other library or framework.
- Wait, how many libraries are there in GoaTE?
- We prefer to call them "modules". Currently there are 13 modules in GoaTE. The main module is the "kernel". New modules are added as needed and requested.
- How do I import the libraries?
- Depends. What language are you using? What build tool are you using? Perhaps you should checkout the "Getting Started" tutorial.
- Why is GoaTE so great?
- Because good testing shouldn't be hard to implement or maintain.