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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@telefonica/living-apps-core-jest

v0.5.0

Published

Mocks for testing laSdk calls with Jest

Downloads

1,404

Readme

@telefonica/living-apps-core-jest

Mocks for testing laSdk calls with Jest

Installation

npm install --save-dev @telefonica/living-apps-core-jest

Import @telefonica/living-apps-core-jest once (for instance in your tests setup file) and you're good to go:

// In your own jest.setup.js (or any other name)
import '@telefonica/living-apps-core-jest';
// In jest.config.js add (if you haven't already)
setupFilesAfterEnv: ['<rootDir>/jest-setup.js'];

You will also need to include your setup file in your `tsconfig.json`` if you haven't already:

  // In tsconfig.json
  "include": [
    ...
    "./jest-setup.ts"
  ],

Examples

test('your test', async () => {
  laSdk.telefonicaApi.get.mockResolvedValueOnce({
    value: 42,
  });

  const result = await someFunctionThatUsesGet();

  expect(result).toEqual({ value: 42 });
});
test('your test', async () => {
  render(<YourComponent />);

  expect(laSdk.focus).toHaveBeenCalledWith('some-element');
});
test('your test', async () => {
  render(<GenericWorldController {...} />);

  expect(laSdk.getMakerContents).toHaveBeenCalledTimes(1);
  expect(laSdk.getMakerContents).toHaveBeenCalledWith('YOUR SCREEN NAME');

Mocked Values

All the values from laSdk are set to the "most falsy" value possible that honor the type definitions. Except functions which are all jest.fn() functions; meaning:

| type | value | example | | :---------- | :---------- | :--------------------------- | | function | jest.fn() | laSdk.http.get | | boolean | false | laSdk.video.isPlaying | | number | NaN | laSdk.video.duration | | string | '' | laSdk.video.src | | Nullable | null | laSdk.video.videoSessionId |

There are a few exceptions:

  1. laSdk.KEYS are the actual keys, we decided there was no drawback in populating KEYS with the real values. Even in this mocking library.
  2. Honoring @telefonica/living-apps-core-web-types there are some strings that are specifically defined, in those cases we choose one from those instead of the empty string; example: laSdk.locale #=> 'es-ES'

Caveats

  • This package is executing a beforeEach() with the following mock setup (if this setup cause any trouble please contact with the team):
laSdk.persistenceRead() => Promise<void>

laSdk.getMakerContents() => Promise<{
  status: 200,
  json: {
    id: '__mocked_layout_id__',
    customType: 'layout_text',
    question: '',
    background: {},
    suggestions: [], s
  },
}>