@wdio/shared-store-service
Advanced tools
Exchange data between main process and workers (specs).
The easiest way is to keep @wdio/shared-store-service as a dev dependency in your package.json, via:
npm install @wdio/shared-store-service --save-dev
Instructions on how to install WebdriverIO can be found here.
Get/set a value (a plain object) to/from the store by key (string). The key can be any arbitrary string except * which is reserved as it allows you to fetch the whole store.
To set values to the store call:
await browser.sharedStore.set('key', 'foobar123')
To get values from the store call:
const value = await browser.sharedStore.get('key')
console.log(value) // returns "foobar123"
You can also fetch all key values by using the * key:
const store = await browser.sharedStore.get('*')
console.log(value) // returns `{ key: "foobar" }`
You could also directly access to setValue and getValue async handlers.
Make sure you properly call them with the await keyword.
// wdio.conf.js
import { setValue, getValue } from '@wdio/shared-store-service'
export const config = {
// ...
onPrepare: [async function (config, capabilities) {
await setValue('foo', 'bar')
}],
// ...
after: async () => {
const value = await getValue('foo')
// ...
}
IMPORTANT! Every spec file should be atomic and isolated from others' specs. The idea of the service is to deal with very specific environment setup issues. Please avoid sharing test execution data!
If the worker threads are competing for resources that must be assigned for each worker, you can use Resource Pool API:
// wdio.conf.js
import { setResourcePool, getValueFromPool, addValueToPool } from '@wdio/shared-store-service'
export const config = {
maxInstances: 2,
// ...
onPrepare: async function (config, capabilities) {
await setResourcePool('availableUrls', ['url01.com', 'url02.com'])
},
// ...
beforeSession: async (conf) => {
conf.baseUrl = await getValueFromPool('availableUrls');
},
// ...
afterSession: async (conf) => {
// worker returns the used resource for next workers to use
await addValueToPool('availableUrls', conf.baseUrl);
}
This example ensures that both workers never use the same baseUrl. A unique url is only assigned to one worker until it's released by it.
Add shared-store to the services list and the sharedStore object will be accessible to you on the browser scope in your test.
// wdio.conf.js
export const config = {
// ...
services: ['shared-store'],
// ...
};
If you are using typescript, make sure to add @wdio/shared-store-service to your compilerOptions.types:
{
"compilerOptions": {
"types": ["node", "@wdio/globals/types", "@wdio/shared-store-service"],
}
}
v9.4.2 (2024-12-12)
wdio-cli
wdio-utils, webdriverio
wdio-utils
wdio-runner
webdriverio
wdio-allure-reporter, webdriver
result and onAfterCommand event (@dprevost-LMI)wdio-cli
wdio-utils, webdriverio
wdio-browserstack-service, wdio-types
FAQs
A WebdriverIO service to exchange data across processes
We found that @wdio/shared-store-service demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.