Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #26982
Closed
Open
Issue created Feb 26, 2019 by Inactive Account@winh🚫Contributor

Proof of concept for implementing frontend integration tests

The frontend testing guide mentions frontend integration tests as a testing level between unit tests and system tests (spec/features/).

In Karma the distinction between frontend integration tests and unit tests is not clear and we have not framework that supports the former. Additionally we are aiming at migrating all Karma tests to Jest (&895 (closed)).

In Jest we are currently running all tests in JSDOM and not in a browser. This implies that certain scenarios cannot be tested or behave differently than in the real application. Additionally Jest does not provide a framework for integration level tests either.

This issue is meant to evaluate our options by implementing a proof of concept for frontend integration tests.

Old description

Support running Jest tests in browsers

Our Jest tests currently run with jsdom which is the default. We should look into ways to also make it run in real browsers.

See also

  • https://github.com/smooth-code/jest-puppeteer
  • https://github.com/GoogleChrome/puppeteer/tree/master/experimental/puppeteer-firefox/

This issues is meant to provide a proof of concept. We can then create follow-up issues for the implementation if necessary.

Edited Aug 20, 2019 by Inactive Account
Assignee
Assign to
Time tracking