EmmanuelDemey / EmmanuelDemey/eslint-plugin-angular
Regression tests with some big angular apps
- Dominant language
- JavaScript
- Stars
- 620
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
Regarding a 1.0.0 release it would be great to have a set of big real world application which follow a lot of the plugin rules and can be used to verify regressions that may not be covered by our unit tests.
I can imagine different scenarios how this could work. Two examples...
1. Simple but manual
Before each release some of use build the plugin locally and run the check against applications we are building
Pros:
- We can also check private apps we write for customers
- No big investment in a complex ci setup
Cons:
- Manual process (error prone!)
1. Integrated in Travis
We find some open source apps or angular modules which already use the plugin or at least follow a lot of rules without using it.
Then we somehow run a new release (or each build) automated against these projects.
Pros:
- Automated!!!
Cons:
- We have to find enough (or big enough) projects which cover a lot of rules
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.