Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
haskell-gargantext
haskell-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 175
    • Issues 175
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • haskell-gargantexthaskell-gargantext
  • Issues
  • #482

Closed
Open
Opened Jun 23, 2025 by Alfredo Di Napoli@AlfredoDiNapoli
  • Report abuse
  • New issue
Report abuse New issue

Considering merging together the `tasty` and `hspec` test drivers

Historically speaking the tests I wrote for the DB operations were written with the intent of being run sequentially, in case we wanted to rely on the results of a previous test in the next one. Given that requirement, I wanted only those kind of tests to be run sequentially, and given that tasty doesn't support per-test-group sequential running, I had to split the test suite in two parts, one using tasty as the driver and one using hspec as the driver.

However, we later changed things such that our database tests can run in parallel, which means that in principle the use of two test drivers is unnecessary and sometimes confusing.

I would like to use tasty-hspec to run our existing hspec tests using a single driver, and remove the need for garg-test-hspec. I think that having a single testsuite stanza will help setting up things like hpc if we want to run any kind of test coverage analysis on the codebase.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
To Review (review requested)
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext#482