-
Notifications
You must be signed in to change notification settings - Fork 19
chore: add nut tests for plugin-org #54
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
Conversation
mshanemc
left a comment
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.
approved with comments. The only one I have strong feelings about it the weird import/require change
| const result = execCmd('force:org:list --skipconnectionstatus --json'); | ||
| expect(result.shellOutput.code).to.be.equal( | ||
| 0, | ||
| concatString(result.shellOutput.stdout, result.shellOutput.stderr) |
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 does produce nicer messages from mocha on fails. Does this belong in testkit so Pete doesn't have to boilerplate it? @shetzel
shetzel
left a comment
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.
Looks good! 1 non-blocking comment.
Windows tests are failing becuase stdout is not being parsed to lines using os.EOL
What does this PR do?
Add new nut tests for plugin-org
What issues does this PR fix or reference?
@W-8856585@