-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Comments
We should determine if:
|
For API / swagger conformance tests that work in mocha one could look at https://github.com/CacheControl/hippie-swagger |
Removing from MVP, top-down approach is out of scope of MVP. However, see #796 |
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 |
Design-first (top-down) approach is out of scope of 4.0 GA, removing this story from the release. |
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 |
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 |
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.
The text was updated successfully, but these errors were encountered: