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

test(typings): Added tests for typings. #1189

Closed
wants to merge 1 commit into from

Conversation

david-driscoll
Copy link
Member

No description provided.

@david-driscoll
Copy link
Member Author

This may break at the moment, I just split this off of #1086, I'll be making some adjustments to it later this evening.

@kwonoj
Copy link
Member

kwonoj commented Jan 13, 2016

Thanks for splitting. Let's not push changes more for now, instead let's leverage this PR to discuss mechanics of type validation test.

Currently there are 3 (including this) way proposed,

@kwonoj
Copy link
Member

kwonoj commented Jan 13, 2016

Mainly separation between suggestion is will we going to use existing test cases vs. creating separate set of tests for type validation only.

@kwonoj kwonoj added the blocked label Jan 13, 2016
@kwonoj
Copy link
Member

kwonoj commented Jan 13, 2016

As same as other proposal, I've marked it as blocked for now to get final conclusion.

@kwonoj
Copy link
Member

kwonoj commented Feb 19, 2016

@david-driscoll , I have created PR #1364 to enable logistics of testing type definition using existing test environment. Once it's agreed, these test may live under existing specs.

@kwonoj
Copy link
Member

kwonoj commented Mar 2, 2016

@david-driscoll , I've created initial proposal #1414 to migrate these test into current unit test environment.

@benlesh
Copy link
Member

benlesh commented Mar 2, 2016

It seems like with the integration tests all in TypeScript now, this might be a redundant effort. What do you think @david-driscoll? @kwonoj?

@kwonoj
Copy link
Member

kwonoj commented Mar 2, 2016

this might be a redundant effort.

: Sort of, but test case itself is still valid. Once #1414 is accepted and checked in this PR need to be updated to use those approach (or either create new PR based on those). I'd like to let @david-driscoll decide between updating this PR or close it.

@kwonoj
Copy link
Member

kwonoj commented Mar 10, 2016

#1414 is now checked in, this PR can utilize it.

@kwonoj
Copy link
Member

kwonoj commented Mar 22, 2016

@david-driscoll , per discussion at #1479 let me close this PR for now. Primarily we'd like to cover type definition sanity via consumption from unit test itself, unless it's explicitly required. If there's some cases need to be explicitly, please reopen anytime and let's continue discussion.

Really appreciate for effort. Thanks again!

@kwonoj kwonoj closed this Mar 22, 2016
@lock
Copy link

lock bot commented Jun 7, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants