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

doc: document directories in test directory #5557

Closed
wants to merge 1 commit into from
Closed

doc: document directories in test directory #5557

wants to merge 1 commit into from

Conversation

mike182uk
Copy link
Contributor

Pull Request check-list

Please make sure to review and check all of these items:

  • Does make -j8 test (UNIX) or vcbuild test nosign (Windows) pass with
    this change (including linting)?
  • Is the commit message formatted according to CONTRIBUTING.md?
  • If this change fixes a bug (or a performance problem), is a regression
    test (or a benchmark) included?
  • Is a documentation update included (if this change modifies
    existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Affected core subsystem(s)

  • tests

Description of change

Add documentation for test directory as per #5538

@mike182uk
Copy link
Contributor Author

There are 2 directories that i am struggling to document: cctest and testpy. If some one could drop a sentence or two on this thread for them i'll update the PR.


###parallel

Various tests that are run in parallel.
Copy link
Member

Choose a reason for hiding this comment

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

Nit: are run in parallel -> may be run in parallel.

Copy link
Contributor

Choose a reason for hiding this comment

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

able to be run in parallel ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍 Updated

@mscdex mscdex added doc Issues and PRs related to the documentations. test Issues and PRs related to the tests. labels Mar 4, 2016

| Runs on CI |
|:------------:|
| No |
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be true I think.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, it's run as part of make. If git blame isn't misleading me, @bnoordhuis wrote the one file in that directory and may be able to supply a half-sentence summary of what it does if no one else steps up. If all else fails, you can just say something hand-waving like "C++ test that is run as part of the build process".

@Trott
Copy link
Member

Trott commented Mar 4, 2016

testpy is not a directory of tests like the others. It is used by the tools/test.py test wrapper (which is used, for example, if you run make test).

@Trott
Copy link
Member

Trott commented Mar 4, 2016

Overall, looks like a fine start to me. Thanks for doing this. Hopefully we can fill in the one or two gaps and land this.

@mike182uk
Copy link
Contributor Author

@Trott Thanks for the feedback, i've updated the PR to include descriptions for cctest and testpy. I've used your description above for cctest for now, but if someone comments with a more descriptive description i'll update the PR.


###internet

Tests for networking related modules ([DNS](https://nodejs.org/api/dns.html), [HTTP](https://nodejs.org/api/http.html), [Net](https://nodejs.org/api/net.html), [TLS](https://nodejs.org/api/tls.html)).
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe give more details about how these actually make outbound connections. There are tests for all of those modules in both /parallel and /sequential. None of those actually go outside the local network though.

Copy link
Contributor

Choose a reason for hiding this comment

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

nit: long line. Please keep them under 80 columns

@evanlucas
Copy link
Contributor

LGTM with the few nits fixed. Thanks!


| Runs on CI |
|:----------:|
| No |

Choose a reason for hiding this comment

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

Maybe an explanation of why those tests are not run in CI could be useful?

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree that would be useful.

@Trott
Copy link
Member

Trott commented Mar 4, 2016

#5528 added a known_issues directory so maybe add that if you're already tidying up a few other things?

@mike182uk
Copy link
Contributor Author

Fixed the long line issues, updated the description for the internet directory, and added the known_issues directory.

@Trott
Copy link
Member

Trott commented Mar 5, 2016

LGTM. (There are gaps that experienced people might be able to fill in. But as this is, it is much better than what we have now, which is nothing.)

|:----------:|
| No |

###addons
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add a space after the hashes. Various markdown parsers fail to render such headings otherwise.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍 fixed.

@evanlucas
Copy link
Contributor

LGTM

@Trott
Copy link
Member

Trott commented Mar 5, 2016

I know we usually don't run CI on doc-only changes, but I have this nagging sense that there's a non-zero possibility that an extra file in test can have side effects. I'm almost certainly wrong, but just in case:

https://ci.nodejs.org/job/node-test-pull-request/1869/

@jasnell
Copy link
Member

jasnell commented Mar 7, 2016

LGTM

Trott pushed a commit to Trott/io.js that referenced this pull request Mar 7, 2016
PR-URL: nodejs#5557
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@Trott
Copy link
Member

Trott commented Mar 7, 2016

Landed in 96af474

@Trott Trott closed this Mar 7, 2016
@Fishrock123 Fishrock123 mentioned this pull request Mar 7, 2016
Fishrock123 pushed a commit that referenced this pull request Mar 8, 2016
PR-URL: #5557
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Fishrock123 pushed a commit that referenced this pull request Mar 8, 2016
PR-URL: #5557
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
MylesBorins pushed a commit that referenced this pull request Mar 17, 2016
PR-URL: #5557
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
MylesBorins pushed a commit that referenced this pull request Mar 21, 2016
PR-URL: #5557
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
MylesBorins pushed a commit that referenced this pull request Mar 21, 2016
PR-URL: #5557
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants