Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • lutra lutra
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 152
    • Issues 152
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • 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
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OTTROTTR
  • lutralutra
  • lutralutra
  • Issues
  • #408
Closed
Open
Issue created Jan 29, 2023 by Yiyao Chen@yiyaocDeveloper

Parallel test execution

We could parallelise existing tests with JUnit 5 and Maven to reduce execution time.

Notes:

  • In order to utilise parallelism, the tests need to be independent, which means they shouldn’t depend on the success of other tests. If there are tests that need to be executed in specific order, we could separate them into another category.
  • Shared resources is a challenge. E.g. tests that write models to the same output file will probably result in flaky tests.
  • Random test failures could also mean that Lutra’s implementation is not thread-safe.
Assignee
Assign to
Time tracking