Testing strategy

There are currently several test suites, each approaching testing from a different POV. The outputs of child issues will be added as guidelines to our wiki.

Within this issue, I would like to:

Document what is currently covered.
Create issues for missing coverage based on findings from Document current state of user flows for both CLI and Portal #144
Consider different structure or approach (what is mocked) for unit vs integration vs E2E tests.
Consider other quality processes and practices (Storybook, FE testing) for both CLI and Portal.
Kick off best practices/guidelines for writing tests.

Child issues:

Time-box for this spike is 1MD and after that we will decide what's next.

consider helper functions for file reads in utils

Write helper for the inner logic to share

vi.mock('@code-pushup/portal-client', async () => {
  const module: typeof import('@code-pushup/portal-client') =
    await vi.importActual('@code-pushup/portal-client');

  return {
    ...module,
    uploadToPortal: vi.fn(
      async () => ({ packageName: '@code-pushup/cli' } as ReportFragment),
    ),
  };
});

Is there a open PR for this?

I like the order of the issues! ❤️

The testing strategy principles can be found here.

Navigation Menu

Repository navigation

Testing strategy #145

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Testing strategy #145

Description

Activity

kristihoskova commented on Oct 25, 2023

BioPhoton commented on Oct 30, 2023

BioPhoton commented on Oct 30, 2023

BioPhoton commented on Nov 15, 2023

BioPhoton commented on Nov 19, 2023

Tlacenka commented on Jan 12, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions