Skip to content

Commit

Permalink
[worker] skip failing integration tests
Browse files Browse the repository at this point in the history
  • Loading branch information
clangenb committed Apr 17, 2024
1 parent 112711f commit 9c1f5c4
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions packages/worker-api/src/integriteeWorker.spec.ts
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
import { Keyring } from '@polkadot/api';
import { cryptoWaitReady } from '@polkadot/util-crypto';
import {paseoNetwork} from './testUtils/networks.js';
import { localDockerNetwork } from './testUtils/networks.js';
import { IntegriteeWorker } from './integriteeWorker.js';
import WS from 'websocket';
import {type KeyringPair} from "@polkadot/keyring/types";

const {w3cwebsocket: WebSocket} = WS;

describe('worker', () => {
const network = paseoNetwork();
const network = localDockerNetwork();
let keyring: Keyring;
let worker: IntegriteeWorker;
let alice: KeyringPair;
Expand Down Expand Up @@ -39,7 +39,7 @@ describe('worker', () => {
// skip it, as this requires a worker (and hence a node) to be running
// To my knowledge jest does not have an option to run skipped tests specifically, does it?
// Todo: add proper CI to test this too.
describe('needs worker and node running', () => {
describe.skip('needs worker and node running', () => {
describe('getWorkerPubKey', () => {
it('should return value', async () => {
const result = await worker.getShieldingKey();
Expand Down

0 comments on commit 9c1f5c4

Please sign in to comment.