Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
mat
mat
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • mat
  • matmat
  • Issues
  • #10065

Closed
Open
Opened Jun 10, 2016 by intrigeri@intrigeriMaintainer

Make test suite work once copied out of the build tree

Debian now has autopkgtest (http://dep.debian.net/deps/dep8/), that are very useful to detect e.g. when a dependency update breaks a package, or when runtime dependencies are missing. Ideally one would write real integration tests meant to be run against the installed package, but a first step when adding autopkgtests for a given package is often to simply run the existing upstream test suite against the installed package.

I've tried copying the @test@ directory out of the source tree and to run @test.py@, but in the current state of things it doesn't work: the test suite hardcodes things like @../mat@ and @../mat.desktop@. Would it be possible to fall back to the location where these files are installed, whenever the test suite detects it is not running from inside the source tree?

(from redmine: created on 2015-08-20, closed on 2015-12-30)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mat/mat#10065