Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M MoReFEM
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 59
    • Issues 59
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MoReFEM
  • CoreLibrary
  • MoReFEM
  • Issues
  • #1525
Closed
Open
Issue created Jun 09, 2020 by GILLES Sebastien@sgillesOwner

#1525 Avoid defining a "Model" for tests

So far, may tests are defining a mock model primarily just to initialize properly stuff.

However, for most of them we just need to:

  • Initialize properly the singletons with the data from the input data file.
  • Call initialization of GodOfDof, the class which does the bulk of the work.

So the model is really overkill in this case...

I have therefore tried to avoid using one for one specific case: the PetscVectorIO test, as a proof of concept.

It was quite a natural follow-up to #1524 (closed), and helps in a task in progress within #1443 (closed): clean-up the initialization API, which is a bit messy and was for the last years considered as a kind of black box.

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