Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dorie
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • dorie
  • dorie
  • Issues
  • #99

Closed
Open
Opened Aug 24, 2018 by Lukas Riedel@lriedelOwner

Build unit tests in separate pipeline job

Description

The current pipeline is set up to build all targets in the build:main build with Release flags (with optimization). this includes all unit tests which might become more in the future and clutter the finished Docker application.

We should start distinguishing between

  • system tests: tests on the final application, i.e., the dorie executable
  • unit tests: tests that run special executables which only serve this purpose

Proposal

  • Further split the build stage by creating a new job build:unit-tests: Compile all (unit) test executables.
  • Remove build_tests command from build:main.
  • Add job test:unit-tests to the testing stage: Run all system test executables here.
  • Add custom target unit_test for running all system tests. This requires a naming convention for system tests: All system test targets must begin with dorie_ut_ test. They will be collected into the custom target using a regex match.

How to test the implementation?

New pipeline succeeds.

Related issues

!87 (merged), !82 (merged), !55 (merged) add more system tests.

People involved

@sospinar, what do you think?

Edited Aug 24, 2018 by Lukas Riedel
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dorie/dorie#99