Comments (4)
To me, this worked out:
mock.add({
method: 'POST',
path: `/my_index/_bulk`
}, () => (
new ResponseError({
body: error,
statusCode: 404,
headers: {},
meta: {} as any,
warnings: [],
})
));
Note: If you want to still return the "meta" prop, you can do the same strategy with the connection: connection: {} as any
Note2: "error" is a const defined earlier, with the desired content
from elasticsearch-js-mock.
In case it's helpful to others, I worked around this by manually crafting one:
const err = Object.create(ResponseError.prototype);
Object.assign(err, {
meta: {
body: {
status: 500,
error: {
type: "whatever",
},
},
500,
headers: {},
},
});
This means the object returns true to instanceof ResponseError
in my exception handler code and works for my use case.
from elasticsearch-js-mock.
I'm using
"@elastic/elasticsearch-mock": "0.3.0",
"@elastic/elasticsearch": "7.9.1",
in case that helps.
from elasticsearch-js-mock.
I'm getting stuck too.
I'd like to use ResponseError to write tests for unexpected requests, but there is more code to generate ResponseError, in other words, the code for testing is getting mess.
I'd like to know if there is a better way to mock ResponseError.
from elasticsearch-js-mock.
Related Issues (20)
- Ignore deep equal check for params body HOT 1
- Clear mocks HOT 1
- Same request with no data and with data gets the same result even if they don't have same response. HOT 1
- TypeError: Cannot destructure property 'ConfigurationError' of 'errors' as it is undefined. HOT 6
- Mocking a "scroll" search HOT 6
- Fails since 7.14.0 HOT 14
- How to mock bulk method HOT 1
- Support for multiple definitions
- how to use with multiple versions ? HOT 2
- Does not work with 8.x version of the client. HOT 1
- ReferenceError: setImmediate is not defined HOT 4
- elastic mocks timeout when used with jest fake timers
- How to use elastic-mock properly? HOT 4
- Upgrading of elasticsearch-mock form v1.0 to v2.0 HOT 1
- How to simulate a delayed response or error?
- High level API around the http mock
- ProductNotSupportedError for elasticsearch-js-mock >=v0.3.1 <=1.0.0 and @elasticsearch/elasticsearch >7.13.0 <= 7.17.0
- How to seperate mocks from implementation?
- Making assertions about how the mock was used HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from elasticsearch-js-mock.