-
Notifications
You must be signed in to change notification settings - Fork 75
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
Updated docs, added trivial tests #11
Conversation
webdev/pubspec.yaml
Outdated
@@ -12,5 +12,10 @@ dependencies: | |||
io: ^0.3.2+1 | |||
stack_trace: ^1.9.2 | |||
|
|||
dev_dependencies: | |||
test: ^0.12.0 | |||
test_descriptor: ^1.0.0 |
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.
Where is test_descriptor used?
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.
Oh! Not yet...good catch...
echo -e '\033[1mTASK: test\033[22m' | ||
echo -e 'pub run test' | ||
pub run test || EXIT_CODE=$? | ||
;; | ||
*) echo -e "\033[31mNot expecting TASK '${TASK}'. Error!\033[0m" | ||
EXIT_CODE=1 | ||
;; |
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.
Is this our recommended approach to travis testing now? What happened to the days of just adding a few lines in the travis.yaml?
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.
This is using mono_repo
– let's us test multiple packages in one repo easily...
PTAL |
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.
One more question, then LGTM.
|
||
test('should fail in a package without a build_runner dependency', () async { | ||
var process = await TestProcess.start('dart', ['bin/webdev.dart', 'serve']); | ||
await process.shouldExit(255); |
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.
Are we expecting anything other than a failure yet?
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.
This is running against itself – so no build_runner dep or anything. We expect it to always fail.
...although in the future it should fail with a more helpful message and a different error code
@@ -0,0 +1,39 @@ | |||
// Copyright (c) 2017, the Dart project authors. Please see the AUTHORS file |
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.
2018
Eh...
…On Tue, Mar 20, 2018 at 10:50 AM Nate Bosch ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In webdev/test/integration_test.dart
<#11 (comment)>:
> @@ -0,0 +1,39 @@
+// Copyright (c) 2017, the Dart project authors. Please see the AUTHORS file
2018
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#11 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABCivZeP_KnUgJc693c9WZR2D3TIMiLks5tgUFfgaJpZM4SyONG>
.
|
No description provided.