-
Notifications
You must be signed in to change notification settings - Fork 1.1k
test(cli): disable GitHub cloning tests #1003
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
Conversation
| * 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 |
There was a problem hiding this comment.
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
6102676 to
4f9ef9d
Compare
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.
4f9ef9d to
0132f4d
Compare
b-admike
left a comment
There was a problem hiding this 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.
|
@b-admike Unfortunately, it seems to be the only test underneath that describe, so it's all disabled as a result. :( |
|
Not waiting on macOS to finish, since it passes locally on my mac, works everywhere else AND just happens to be disabling a test. |
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 testpasses on your machinepackages/cliwere updatedpackages/example-*were updated