Skip to content

test: change assert.equal to assert.strictEqual - #9956

Closed
crokita wants to merge 1 commit into
nodejs:masterfrom
crokita:test-cluster-fix
Closed

test: change assert.equal to assert.strictEqual#9956
crokita wants to merge 1 commit into
nodejs:masterfrom
crokita:test-cluster-fix

Conversation

@crokita

@crokitacrokita commented Dec 1, 2016

Copy link
Copy Markdown
Contributor
Checklist
  • make -j8 test (UNIX)
  • commit message follows commit guidelines
Affected core subsystem(s)

test

Description of change

Use assert.strictEqual() instead of assert.equal() for lines 11, 12, 13, 14, 21, 22, 23, 24, 28

@nodejs-github-botnodejs-github-bot added the test Issues and PRs related to the tests. label Dec 1, 2016
@mscdexmscdex added the cluster Issues and PRs related to the cluster subsystem. label Dec 1, 2016
@mscdex

Copy link
Copy Markdown
Contributor

First line of commit message is too long, see the commit message guidelines here.

@imyllerimyller added the code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. label Dec 1, 2016
@crokitacrokita changed the title test: change assert.equal to assert.strictEqual in filetest: change assert.equal to assert.strictEqualDec 1, 2016

@jasnelljasnell left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM. The commits will need to be squashed and a new-line needs to be added at the end of the file to pass linting.

@Trott

Trott commented Dec 8, 2016

Copy link
Copy Markdown
Member

@Trott

Copy link
Copy Markdown
Member

ping @crokita: Can you add a newline to the end of the file? Even better if you can squash the commits into a single commit, but that can also be done by whoever lands the change.

@crokita

Copy link
Copy Markdown
ContributorAuthor

Yep! Updated the branch. Does this look okay @Trott ?

@TrottTrott left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM if CI is ✅

@Trott

Copy link
Copy Markdown
Member

@italoacasas

Copy link
Copy Markdown

Landed 70d752e

italoacasas pushed a commit that referenced this pull request Dec 23, 2016
- Using assert.strictEqual instead assert.equal
PR-URL: #9956
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Italo A. Casas <me@italoacasas.com>
@Trott

Copy link
Copy Markdown
Member

Thanks for the contribution @crokita! 🎉

targos pushed a commit that referenced this pull request Dec 26, 2016
- Using assert.strictEqual instead assert.equal
PR-URL: #9956
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Italo A. Casas <me@italoacasas.com>
@MylesBorinsMylesBorins mentioned this pull request Dec 27, 2016
targos pushed a commit that referenced this pull request Dec 28, 2016
- Using assert.strictEqual instead assert.equal
PR-URL: #9956
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Italo A. Casas <me@italoacasas.com>
@evanlucasevanlucas mentioned this pull request Jan 3, 2017
evanlucas pushed a commit that referenced this pull request Jan 3, 2017
- Using assert.strictEqual instead assert.equal
PR-URL: #9956
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Italo A. Casas <me@italoacasas.com>
evanlucas pushed a commit that referenced this pull request Jan 4, 2017
- Using assert.strictEqual instead assert.equal
PR-URL: #9956
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Italo A. Casas <me@italoacasas.com>
MylesBorins pushed a commit that referenced this pull request Jan 23, 2017
- Using assert.strictEqual instead assert.equal
PR-URL: #9956
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Italo A. Casas <me@italoacasas.com>
MylesBorins pushed a commit that referenced this pull request Jan 24, 2017
- Using assert.strictEqual instead assert.equal
PR-URL: #9956
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Italo A. Casas <me@italoacasas.com>
@MylesBorinsMylesBorins mentioned this pull request Jan 24, 2017
MylesBorins pushed a commit that referenced this pull request Feb 1, 2017
- Using assert.strictEqual instead assert.equal
PR-URL: #9956
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Italo A. Casas <me@italoacasas.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

clusterIssues and PRs related to the cluster subsystem.code-and-learnIssues related to the Code-and-Learn events and PRs submitted during the events.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

@crokita@mscdex@Trott@italoacasas@jasnell@imyller@targos@nodejs-github-bot