Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 594
    • Issues 594
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 61
    • Merge requests 61
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #526
Closed
Open
Issue created Mar 07, 2019 by Thomas Markwalder@tmarkMaintainer

Improve MySQL unit test time by implementing a wipe-data only mechanism

MySQL and MariaDB variants can be extremely slow doing schema updates. The current mechanism creates and destroys the schema between each MySQL unit test. With dramatic increase in schema size and the number of unit tests, test execution has become untenable.

Rather than creating and destroying the schema each time, it should be sufficient for each test to determine if it has the correct schema version and then simply wipe the transient data from the database upon entry and exit.

If the schema version is incorrect (or non existent), the schema should be destroyed and recreated. In theory this should happen infrequently, once a environment's unit test schema is correct.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking