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

Add tests for #182/#183 #184

Closed
blag opened this issue Jun 29, 2019 · 3 comments · Fixed by StackStorm/st2tests#175
Closed

Add tests for #182/#183 #184

blag opened this issue Jun 29, 2019 · 3 comments · Fixed by StackStorm/st2tests#175
Labels

Comments

@blag
Copy link
Contributor

blag commented Jun 29, 2019

#182 was a regression, but we should add a test for that so we don't regress again in the future. Opening this issue to track the status of that.

@arm4b arm4b added the tests label Jun 29, 2019
@arm4b
Copy link
Member

arm4b commented Jun 29, 2019

Yeah, having those ^^ changes minimal/granular as possible still hit the regressions. I'm afraid to think what would happen with multiple changes coming in #168.

Minimally, something along the lines would be useful to test:

  • Nock the failing HTTP response from ST2 API. Ensure that function doesn't throw and that hubot doesn't exit.
  • Additionally need to ensure that the warning message is sent back to chat as well:

@blag
Copy link
Contributor Author

blag commented Jun 29, 2019

@armab Yep, I think we all made the right call (thanks to you).

If we need to check the output we should simply make it an end-to-end test in st2tests. I’ll do that next week; should be pretty straightforward.

@arm4b
Copy link
Member

arm4b commented Jun 29, 2019

Thanks, I'll take care of the first part then: Nock/HTTP unit test in this repo to ensure hubot doesn't exit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants