Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S spearhead
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Dynamic Exposure
  • OpenBuildingMap
  • spearhead
  • Issues
  • #1

Closed
Open
Created Nov 03, 2021 by Felix Delattre@fdOwner0 of 1 task completed0/1 task

Follow-up from "Added tests for diff analyzer"

The following discussion from !18 (merged) should be addressed:

  • @marius started a discussion:

    Not part of this MR but I recommend to use the pytestconfig fixture which contains the rootdir which can be used e.g. here to get absolute paths to files.

    Just as an incentive how to make this more flexible. Checkout https://docs.pytest.org/en/6.2.x/customize.html on 'finding the rootdir':

    The internal Config object (accessible via hooks or through the pytestconfig fixture) will subsequently carry these attributes:

    config.rootpath: the determined root directory, guaranteed to exist.
    
    config.inipath: the determined configfile, may be None (it is named inipath for historical reasons).
Assignee
Assign to
Time tracking