Skip to content

Conversation

@kjdelisle
Copy link
Contributor

@kjdelisle kjdelisle commented Feb 15, 2018

The check for equality on example packages after cloning prevents
update of the contents of those packages, since they are no longer
equivalent! As a result, we are disabling this test for now until
we can come up with something that suitably validates the
behaviour we expect, but in a way that doesn't prevent future
changes from passing tests.

blocks #1001

Checklist

  • npm test passes on your machine
  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style guide
  • Related API Documentation was updated
  • Affected artifact templates in packages/cli were updated
  • Affected example projects in packages/example-* were updated

* being cloned properly, we can't hang that idea on validating the
* particular presence of any content that isn't perpetually required.
*
* I'm not sure how to update this test in a useful way without creating
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a comment saying this test can be removed entirely once #932 is completed as that will test a project by running it, which should be adequate verification of cloneExampleFromGitHub

@kjdelisle kjdelisle force-pushed the cli/disable-clone-test branch from 6102676 to 4f9ef9d Compare February 15, 2018 18:25
The check for equality on example packages after cloning prevents
update of the contents of those packages, since they are no longer
equivalent! As a result, we are disabling this test for now until
we can come up with something that suitably validates the
behaviour we expect, but in a way that doesn't prevent future
changes from passing tests.
@kjdelisle kjdelisle force-pushed the cli/disable-clone-test branch from 4f9ef9d to 0132f4d Compare February 15, 2018 19:49
Copy link
Contributor

@b-admike b-admike left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My concern is that this is the main(only?) test we have for lb4 example, so if we can keep some checks intact temporarily until #932 is finished then that'd be great. Otherwise, I'm fine with skipping it as well.

@kjdelisle
Copy link
Contributor Author

@b-admike Unfortunately, it seems to be the only test underneath that describe, so it's all disabled as a result. :(

@kjdelisle kjdelisle merged commit 14f6333 into master Feb 15, 2018
@kjdelisle kjdelisle deleted the cli/disable-clone-test branch February 15, 2018 20:31
@kjdelisle
Copy link
Contributor Author

Not waiting on macOS to finish, since it passes locally on my mac, works everywhere else AND just happens to be disabling a test.

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.

5 participants