Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add components testing #36

Closed
Scot3004 opened this issue Apr 7, 2018 · 1 comment
Closed

Add components testing #36

Scot3004 opened this issue Apr 7, 2018 · 1 comment

Comments

@Scot3004
Copy link
Contributor

Scot3004 commented Apr 7, 2018

On the starter is not given a test framework but could be good if it have a test suite, for quality

@Vagr9K
Copy link
Owner

Vagr9K commented Apr 10, 2018

Unfortunately due to the way gatsby starters work, you can't use them as separate plugins or NPM packages. This means that you'll have to work on the code written in the starter.

I wanted to initially add unit tests back in summer, but then realized that whoever will try to use my starter, will be stuck with my preferred unit testing system, which he might not like, or just not need.

I appreciate you pointing out the flaws of the project, but until gatsby creates a different starter system, "fixing" this flaw will only limit it's usability.

@Vagr9K Vagr9K closed this as completed Apr 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants