Skip to content

Move js package tests into tests package. #800

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

Merged
merged 1 commit into from
Apr 20, 2018
Merged

Move js package tests into tests package. #800

merged 1 commit into from
Apr 20, 2018

Conversation

dmitshur
Copy link
Member

This way, all GopherJS-specific tests are in tests package, rather than
having an arbitrary split. None of the package js tests were internal
to the package.

This helps a future change where the js package becomes embedded into
the compiler. It makes it easier to add and modify GopherJS tests
without having to regenerate the js package.

Resolves #792.

This way, all GopherJS-specific tests are in tests package, rather than
having an arbitrary split. None of the package js tests were internal
to the package.

This helps a future change where the js package becomes embedded into
the compiler. It makes it easier to add and modify GopherJS tests
without having to regenerate the js package.

Resolves #792.
@myitcv
Copy link
Member

myitcv commented Apr 20, 2018

As discussed @shurcooL 👍 from me.

@dmitshur
Copy link
Member Author

I'm going to merge this and rebase #787 on top. That way, none of the GopherJS tests will be embedded into the core packages, which has benefits (smaller compiler size, easier to modify tests).

@dmitshur dmitshur merged commit fcfa75a into master Apr 20, 2018
@dmitshur dmitshur deleted the move_js_tests branch April 20, 2018 20:01
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

Successfully merging this pull request may close these issues.

2 participants