Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7837681
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T14:47:46+00:00 2026-06-02T14:47:46+00:00

I have build a Debian package out of a Python project which depends on

  • 0

I have build a Debian package out of a Python project which depends on a bunch of Debian packages to work.
The Python project also contains unit and integration tests (using py.test).

Since my project depends on some Debian packages, I need to have these packages installed inside the test environment and they should verify that my module works correctly together with these packages (I want to make sure that my module does not break on updates of these libs).

I want to put the configuration and execution of these test environments into a Makefile. These tests should be runnable both on a developer workstation and on an Jenkins-powered Integration Server.

My current approach for a complete integrationtest of my package is to:

  1. Create a pBuilder environment
  2. Install dependencies from Debian-controlfile into pBuilder env
  3. Inside this pBuilder-environment launch py.test, also using virtualenv / tox to test different Python interpreter versions
  4. collect test-results from test environment (py.test can generate nice JUnit-like test output which Jenkins can publish easily)

Unfortunately I could not find any hints how to realize this stuff – especially how to do 3). All documentation I could find was just about building the package, not about running tests.

Can anyone provide me some hints how I can build up such a test setup? Also, I want to know if it makes sense at all to do what I aim to do. How do others test integration of (Python) modules with other Debian packages?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T14:47:47+00:00Added an answer on June 2, 2026 at 2:47 pm

    I assume that you want to run the test-suite while building the packaging.

    1) Add a check target to your package’s Makefile, which runs your actual testsuite including all the virtualenv/tox magic; e.g.:

    .PHONY: check
    check:
        ./runtests.sh
    

    with the runtests.sh script running the interpreter checks and then launching py.test

    2) Configure your debian/rules to actually run the tests

    2a) If you use CDBS, add the following line at the beginning of your debian/rules

    DEB_MAKE_CHECK_TARGET = check
    

    2b) If you use debhelper, then the dh_auto_test script should automagically run the tests for you (provided there is a check target in your Makefile)

    2c) If you have a custom debian/rules, run the “check” target after a successfull build

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a very simple python package that I build into debian packages using
I have a debian/control file which includes: Build-Depends: ... libboost1.35-dev, libboost-date-time1.35-dev, ... This stops
I have the following Ruby script that creates a Debian package, which works fine:
I have a visual studio-2010 project which contains lots of source files and header
I have a website that needs to build a debian package and move it
I have build C# program that work with RAPI (communication to PPC or WinCE)
I used to use Backbone.js as an easy MVC framework which have build-in routing
I'm trying to build a Debian package, but I've got this weird pseudo-directory problem.
hi there i have a problem to generate a debian package i have 2
i have build a small function whose work is to change banner image path

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.