Security News
Input Validation Vulnerabilities Dominate MITRE's 2024 CWE Top 25 List
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
@elastic/elasticsearch-mock
Advanced tools
When testing your application you don't always need to have an Elasticsearch instance up and running, but you might still need to use the client for fetching some data. If you are facing this situation, this library is what you need.
Use v1.0.0
for @elastic/elasticsearch
≤ v7 compatibility and v2.0.0
for @elastic/elasticsearch
≥ v8 compatibility.
npm install @elastic/elasticsearch-mock --save-dev
const { Client } = require('@elastic/elasticsearch')
const Mock = require('@elastic/elasticsearch-mock')
const mock = new Mock()
const client = new Client({
node: 'http://localhost:9200',
Connection: mock.getConnection()
})
mock.add({
method: 'GET',
path: '/_cat/health'
}, () => {
return { status: 'ok' }
})
client.cat.health()
.then(console.log)
.catch(console.log)
Constructor
Before start using the library you need to create a new instance:
const Mock = require('@elastic/elasticsearch-mock')
const mock = new Mock()
add
Adds a new mock for a given pattern and assigns it to a resolver function.
// every GET request to the `/_cat/health` path
// will return `{ status: 'ok' }`
mock.add({
method: 'GET',
path: '/_cat/health'
}, () => {
return { status: 'ok' }
})
You can also specify multiple methods and/or paths at the same time:
// This mock will catch every search request against any index
mock.add({
method: ['GET', 'POST'],
path: ['/_search', '/:index/_search']
}, () => {
return { status: 'ok' }
})
get
Returns the matching resolver function for the given pattern, it returns null
if there is not a matching pattern.
const fn = mock.get({
method: 'GET',
path: '/_cat/health'
})
clear
Clears/removes mocks for specific route(s).
mock.clear({
method: ['GET'],
path: ['/_search', '/:index/_search']
})
clearAll
Clears all mocks.
mock.clearAll()
getConnection
Returns a custom Connection
class that you must pass to the Elasticsearch client instance.
const { Client } = require('@elastic/elasticsearch')
const Mock = require('@elastic/elasticsearch-mock')
const mock = new Mock()
const client = new Client({
node: 'http://localhost:9200',
Connection: mock.getConnection()
})
A pattern is an object that describes an http query to Elasticsearch, and it looks like this:
interface MockPattern {
method: string
path: string
querystring?: Record<string, string>
body?: Record<string, any>
}
The more field you specify, the more the mock will be strict, for example:
mock.add({
method: 'GET',
path: '/_cat/health'
querystring: { pretty: 'true' }
}, () => {
return { status: 'ok' }
})
client.cat.health()
.then(console.log)
.catch(console.log) // 404 error
client.cat.health({ pretty: true })
.then(console.log) // { status: 'ok' }
.catch(console.log)
You can craft custom responses for different queries:
mock.add({
method: 'POST',
path: '/indexName/_search'
body: { query: { match_all: {} } }
}, () => {
return {
hits: {
total: { value: 1, relation: 'eq' },
hits: [{ _source: { baz: 'faz' } }]
}
}
})
mock.add({
method: 'POST',
path: '/indexName/_search',
body: { query: { match: { foo: 'bar' } } }
}, () => {
return {
hits: {
total: { value: 0, relation: 'eq' },
hits: []
}
}
})
You can also specify dynamic urls:
mock.add({
method: 'GET',
path: '/:index/_count'
}, () => {
return { count: 42 }
})
client.count({ index: 'foo' })
.then(console.log) // => { count: 42 }
.catch(console.log)
client.count({ index: 'bar' })
.then(console.log) // => { count: 42 }
.catch(console.log)
Wildcards are supported as well.
mock.add({
method: 'HEAD',
path: '*'
}, () => {
return ''
})
client.indices.exists({ index: 'foo' })
.then(console.log) // => true
.catch(console.log)
client.ping()
.then(console.log) // => true
.catch(console.log)
The resolver function takes a single parameter which represent the API call that has been made by the client. You can use it to craft dynamic responses.
mock.add({
method: 'POST',
path: '/indexName/_search',
}, params => {
return { query: params.body.query }
})
This utility uses the same error classes of the Elasticsearch client, if you want to return an error for a specific API call, you should use the ResponseError
class:
const { errors } = require('@elastic/elasticsearch')
const Mock = require('@elastic/elasticsearch-mock')
const mock = new Mock()
mock.add({
method: 'GET',
path: '/_cat/health'
}, () => {
return new errors.ResponseError({
body: { errors: {}, status: 500 },
statusCode: 500
})
})
This software is licensed under the Apache 2 license.
FAQs
Mock utility for the Elasticsearch's Node.js client
We found that @elastic/elasticsearch-mock demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 66 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.