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

A better tool for automated API smoke tests #644

Closed
bajtos opened this issue Oct 12, 2017 · 7 comments
Closed

A better tool for automated API smoke tests #644

bajtos opened this issue Oct 12, 2017 · 7 comments

Comments

@bajtos
Copy link
Member

bajtos commented Oct 12, 2017

Right now, we are recommending Dredd for automated testing of API conformance with the spec. This tool has several shortcomings:

  • A binary dependency. Setting up build env is tricky (especially in enterprise environments with a constrained access to the interned), it requires us to spend more time on support. The time needed to npm install all dependencies is too long too.

  • The tool does not integrate with our Mocha test runner. We have to configure Dredd to log test failures to stdout/stderr, which makes test report inconsistent.

  • When a test fails, the error message is too verbose and makes it difficult to quickly spot what went wrong.

I am proposing to find a tool that will give our users a better UX.

@kjdelisle
Copy link
Contributor

We should determine if:

  • is there a better solution than Dredd
  • if not, drop this section from "Thinking in LoopBack" and from our examples (if any)
  • write a blog post about it

@thinusn
Copy link

thinusn commented Nov 5, 2017

For API / swagger conformance tests that work in mocha one could look at https://github.com/CacheControl/hippie-swagger

@bajtos bajtos removed the MVP label Dec 12, 2017
@bajtos
Copy link
Member Author

bajtos commented Dec 12, 2017

Removing from MVP, top-down approach is out of scope of MVP. However, see #796

@bajtos bajtos added the non-MVP label Dec 15, 2017
@bajtos bajtos mentioned this issue Feb 6, 2018
4 tasks
@stale
Copy link

stale bot commented Jun 13, 2018

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Jun 13, 2018
@jannyHou jannyHou removed the stale label Jun 13, 2018
@bajtos
Copy link
Member Author

bajtos commented Jul 30, 2018

Design-first (top-down) approach is out of scope of 4.0 GA, removing this story from the release.

@stale
Copy link

stale bot commented Oct 28, 2019

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Oct 28, 2019
@stale
Copy link

stale bot commented Nov 27, 2019

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

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

No branches or pull requests

5 participants