ngtx is in early stage. If you have ideas how to further improve it feel free to raise an issue and/or contribute.

ngtx stands for "Angular Testing Extensions" and is a small set of functions aiming to make your life easier when testing Angular components. It's supposed to make your tests lean while increasing the readability by boosting the semantics of each test case.

All common things we do in Angular tests are quite verbose. We often find ourselves writing stuff that does not express our intensions, but really just are steps on our way to our test-goal. Furthermore, while we care about production code to be clean and easy to understand, our testing code is left WET instead of DRY and hard to understand on the first glance.

We can do better and we think we should. ngtx is meant to help you with that by "injecting" small "helpers" into your tests improving both, productivity and readability.

New to ngtx? Let's get you started with these links:

• Getting Started / First Steps
• Feature Overview
• Api Documentation

Having questions or issues using ngtx? You may want to have a look on these links:

• Examples
• StackOverflow

If you know and like ngtx we would love for you to contribute by either giving us feedback on issues or missing features or even by helping us implement already existing issues. If you have ideas how to improve our workflow you're also welcome to share it with us.

• Contributing
• Code of Conduct

• Julian Lang (GitHub: JulianLang, author)
• Patrick-Andre Decker