Skip to content

Adding where does test go section in writing-test.md #18802

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.

Sign up for GitHub

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

Closed
juggernaut451 wants to merge 11 commits into from
Closed

Adding where does test go section in writing-test.md #18802

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
481c5f9
Adding where does test go section in writing-test.md
juggernaut451 Feb 15, 2018
dd902a0
Typo fix
juggernaut451 Feb 15, 2018
c1c8eb5
Typo fix
juggernaut451 Feb 15, 2018
5bf8d98
reframing content and topic of section
juggernaut451 Feb 15, 2018
ca0448b
Fixes: https://github.com/nodejs/node/issues/18774
juggernaut451 Feb 17, 2018
2dea00a
Restructuring the description
juggernaut451 Feb 19, 2018
ba6513b
Wrapping line in 80 characters
juggernaut451 Feb 21, 2018
b24c938
Typo fixes
juggernaut451 Feb 22, 2018
0fa4c3a
refactoring content
juggernaut451 Mar 1, 2018
c8696df
wrapping in 80 char
juggernaut451 Mar 2, 2018
fc0c5b4
doc: adding test directory structure
juggernaut451 Mar 7, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fixes: #18774
  • Loading branch information
@juggernaut451
juggernaut451 committed Feb 17, 2018
commit ca0448b83ea05d302448d6d851281a3e320c3bd7
6 changes: 4 additions & 2 deletions doc/guides/writing-tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,10 @@ Add tests when:
See the test [directory structure overview](https://github.com/nodejs/node/blob/master/test/README.md)
Copy link
Copy Markdown
Member

@BridgeAR BridgeAR Feb 18, 2018

Choose a reason for hiding this comment

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

Since this is longer than 80 characters, please move the reference down to the end of the file and only keep [directory structure overview][].

Copy link
Copy Markdown
Contributor Author

@juggernaut451 juggernaut451 Feb 19, 2018

Choose a reason for hiding this comment

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

changes made.

Copy link
Copy Markdown
Member

@BridgeAR BridgeAR Feb 18, 2018

Choose a reason for hiding this comment

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

Adding a new line after the header would be good for consistency as well.

Copy link
Copy Markdown
Contributor Author

@juggernaut451 juggernaut451 Feb 19, 2018

Choose a reason for hiding this comment

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

changes made.

for an outline of existing test types and their locations.
When deciding on whether to expand an existing test file or create a new one,
consider going through the files related to the subsystem (e.g. ones starting with "test-streams" for `lib/streams.js`)
and assessing whether a related test already exists.
consider going through the files related to the subsystem.
For example, take a look at tests starting with "test-streams"
when writing tests for `lib/streams.js`
Copy link
Copy Markdown
Member

@BridgeAR BridgeAR Feb 18, 2018

Choose a reason for hiding this comment

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

The line breaks in this paragraph are actually not visible when viewing this not in raw form. Therefore it would be good to wrap each line around 80 characters.

Copy link
Copy Markdown
Contributor Author

@juggernaut451 juggernaut451 Feb 19, 2018

Choose a reason for hiding this comment

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

changes made.



Copy link
Copy Markdown
Member

@BridgeAR BridgeAR Feb 18, 2018

Choose a reason for hiding this comment

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

Please keep this consistent with the other places in the doc and only use a single new line :-)

Copy link
Copy Markdown
Contributor Author

@juggernaut451 juggernaut451 Feb 19, 2018

Choose a reason for hiding this comment

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

changes made.

Copy link
Copy Markdown
Member

@BridgeAR BridgeAR Feb 21, 2018

Choose a reason for hiding this comment

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

Hm, this does not seem to be addressed?

## Test structure

Expand Down