npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@ixon-cdk/testing

v1.21.0

Published

This package contains a implementation of the `ComponentContext`, usefull for component testing.

Readme

IXON Component Development Kit Testing

This package contains a implementation of the ComponentContext, usefull for component testing.

Component testing

App Engine UI Components can be tested in Jest, just like a regular unit test. To test components, two libraries are recommended, @testing-library/svelte and @ixon-cdk/testing. @ixon-cdk/testing implements the Component Context API for use in testing, while @testing-library/svelte makes it easy to do DOM assertions on your components.

Note: the @testing-library/svelte documentation can be found here.

Component Context

The Component Context is dependent on the host app, for example Portal, to function. This is not workable in unit tests. For unit tests, a Mock Component Context is created. Depending on the component, you can create a new ComponentContext with createMockComponentContext({}) or ComponentContextFactory with createMockComponentContextFactory({}). When creating the context, you can set several options, for example the component inputs.

import { createMockComponentContext } from '@ixon-cdk/testing';
import { AGENT_LIST } from '@testing/mock-data';
import MyComponent from './my-component.svelte';

const context = createMockComponentContext({});

const component = render(MyComponent, {
  props: {
    context,
  },
});

ResourceDataClient

The results of the ResourceDataClient can be configured when creating the ComponentContext, you don't need to use Jest mocks. In the following example, a ComponentContext is created with ResourceDataClient options. When the component queries the Agent resource, the value AGENT_LIST[0] will be given. This works for both query and render.

import { createMockComponentContext } from '@ixon-cdk/testing';
import { AGENT_LIST } from './mock-data';
import MyComponent from './my-component.svelte';

const context = createMockComponentContext({
  resourceData: {
    selectors: [
      {
        selector: 'Agent',
        value: AGENT_LIST[0],
      },
    ],
  },
});

const component = render(MyComponent, {
  props: {
    context,
  },
});

In certain situations, you want to be able to update the resource, for example to mimic a Change Notification. You can also provide a BehaviourSubject as value. When a new value is published, the query listeners will be called and the render method will re-render the templates. In the following example, the agent name will be updated.

import { createMockComponentContext } from '@ixon-cdk/testing';
import { AGENT_LIST } from './mock-data';
import MyComponent from './my-component.svelte';

const agent$ = new BehaviorSubject(AGENT_LIST[0]);
const context = createMockComponentContext({
  resourceData: {
    selectors: [
      {
        selector: 'Agent',
        value: agent$,
      },
    ],
  },
});

const component = render(MyComponent, {
  props: {
    context,
  },
});

// Update the agent name
agent$.next({
  ...AGENT_LIST[0],
  name: 'Demo loader',
});

LoggingDataClient

The results of the LoggingDataClient can be configured when creating the ComponentContext, you don't need to use Jest mocks. In the following example, a ComponentContext is created with LoggingDataClient options.

import {
  createMockComponentContext,
  createMockLoggingDataValue,
} from '@ixon-cdk/testing';
import MyComponent from './my-component.svelte';

const dateTime = DateTime.fromJSDate(BASE_TIME);
const context = createMockComponentContext({
  loggingData: {
    selectors: [
      {
        selector: 'Agent#selected:default.tag.count-int-last',
        values: [createMockLoggingDataValue(27, dateTime.toMillis())],
      },
    ],
  },
});

const component = render(MyComponent, {
  props: {
    context,
  },
});

In certain situations, you want to be able to update the data, for example to mimic live data. You can also provide a BehaviourSubject as value. When a new value is published, the query listeners will be called.

import {
  createMockComponentContext,
  createMockLoggingDataValue,
} from '@ixon-cdk/testing';
import MyComponent from './my-component.svelte';

const dateTime = DateTime.fromJSDate(BASE_TIME);
const values$ = new BehaviorSubject([
  createMockLoggingDataValue(27, dateTime.toMillis()),
]);

const context = createMockComponentContext({
  loggingData: {
    selectors: [
      {
        selector: 'Agent#selected:default.tag.count-int-last',
        values: values$,
      },
    ],
  },
});

const component = render(MyComponent, {
  props: {
    context,
  },
});

values$.next([
  createMockLoggingDataValue(29, dateTime.plus({ seconds: 10 }).toMillis()),
]);