test(@toss/utils): wrote test code for getViewportSize function

[okinawaa]

Overview

I wrote test code for getViewportSize function

PR Checklist

• I read and included theses actions below

1. I have read the Contributing Guide
2. I have written documents and tests, if needed.

[netlify]

👷 Deploy request for slash-libraries pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	6f45aa6

[okinawaa]

I'd like to test the server status, should I fill it out like this?
Is it better to mock the isServer function itself

[JayeHa]

@okinawaa
I think directly chaning the window object in your tests could be risky. 😢
I'm not sure that your tests won't affect the other tests.

How about mocking it like this instead?
I try it based on this reference!

import { getViewportSize } from '.';

let windowSpy: jest.SpyInstance;

beforeEach(() => {
  windowSpy = jest.spyOn(global, 'window', 'get');
});
afterEach(() => {
  windowSpy.mockRestore();
});

describe('getViewportSize', () => {
  it('should return viewport size', () => {
    windowSpy.mockImplementation(() => ({
      innerWidth: 1024,
      innerHeight: 768,
    }));

    const expectedSize = { width: 1024, height: 768 };
    const size = getViewportSize();

    expect(size).toEqual(expectedSize);
  });

  it('should return zero size when running on server', () => {
    windowSpy.mockImplementation(() => undefined);

    const expectedSize = { width: 0, height: 0 };
    const size = getViewportSize();

    expect(size).toEqual(expectedSize);
  });
});

[vercel]

@raon0211 is attempting to deploy a commit to the Toss Team on Vercel.

A member of the Team first needs to authorize it.