Skip to content
This repository was archived by the owner on Mar 5, 2026. It is now read-only.

fix: sys tests use async/await to allow a fix#253

Merged
JustinBeckwith merged 7 commits intogoogleapis:masterfrom
DominicKramer:fix/async-and-fix-system-tests
Nov 16, 2018
Merged

fix: sys tests use async/await to allow a fix#253
JustinBeckwith merged 7 commits intogoogleapis:masterfrom
DominicKramer:fix/async-and-fix-system-tests

Conversation

@DominicKramer
Copy link
Copy Markdown
Contributor

The system tests have been updated to use async/await. This is
done to make it easier to see errors in the tests and fix them.

Fixes: #213

The system tests have been updated to use async/await.  This is
done to make it easier to see errors in the tests and fix them.

Fixes: googleapis#213
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Nov 12, 2018
@JustinBeckwith
Copy link
Copy Markdown
Contributor

@DominicKramer it looks like the unit tests are failing - i was going to wait until those were passing to review :)

@DominicKramer
Copy link
Copy Markdown
Contributor Author

@JustinBeckwith Yes I'm still in the process of resolving some issues that are causing the tests to fail.

Normally, I don't expect a review until I've explicitly added reviewers. However, I could instead indicate in the title not to review. What approach do you suggest I should follow that would align with your team's expectations for a PR that doesn't need to be reviewed yet?

@JustinBeckwith
Copy link
Copy Markdown
Contributor

Ahhhh, got it. Apologies! Typically I don't open the PR until it's ready for some kind of review 🤷‍♂️ This is my bad though, I should have paid better attention. I just saw the issue where someone was asking for a release and got eager :)

…amer/nodejs-error-reporting into fix/async-and-fix-system-tests
The API documents the count as only being approximate and its
value is not accurate enough to use in the tests.  When the
tests were running I watched the error reporting console and saw
the count be (inccorectly) 2 for a few seconds before dropping
down to the correct value of 1.
@codecov
Copy link
Copy Markdown

codecov Bot commented Nov 16, 2018

Codecov Report

❗ No coverage uploaded for pull request base (master@720bc9f). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #253   +/-   ##
=========================================
  Coverage          ?   88.47%           
=========================================
  Files             ?       29           
  Lines             ?     1241           
  Branches          ?      151           
=========================================
  Hits              ?     1098           
  Misses            ?       87           
  Partials          ?       56

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 720bc9f...727b17b. Read the comment docs.

@DominicKramer DominicKramer requested a review from a team November 16, 2018 19:28
@DominicKramer
Copy link
Copy Markdown
Contributor Author

@JustinBeckwith No worries. It is ready to review now :)


cb(matchedErrors);
async function verifyAllGroups(
messageTest: (message: string) => void, maxCount: number,

This comment was marked as spam.

@JustinBeckwith JustinBeckwith merged commit 270c44e into googleapis:master Nov 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix the system tests

3 participants