Let’s test Ubuntu NOW!

Making Ubuntu better, if possible

Mago is in Karmic!!

with 2 comments

Yes, if you updated your Karmic repositories lately, you can install Mago just typing “sudo apt-get install mago”. What does that mean? Not much, for the moment.

We have packaged the library and harness, but not the tests. Once you have installed Mago in your machine, you can start writing tests using the library, you will be able to run the tests with the Mago harness and get nice reports in XML and HTML. You won’t have the already written tests, though. Tests change a lot, so it does not make sense to keep them in the repositories, which are quite static. PPAs are a much better place for tests, which I am planning to maintain.

I still have a lot of work to be done regarding this: I have to set up the PPA for the tests and update the documentation at the Mago site, to start. Why did I push Mago into Karmic, then? There are two main reason: Feature Freeze and Holidays. Ubuntu development schedule has an important date called Feature Freeze, after which no new packages are generally accepted and only bug fixes are supposed to get uploaded. Karmic FF is happening August 27th, but I will be on holidays since August 14th, so it was now or never (or Karmic+1).

The main advantage of having Mago in the repositories is that, if a project wants to use it as part of the testing of their daily builds, they can set Mago as a Build-Depends of the project and forget about whether Mago is installed or not in the build machine. And, don’t worry, I will be updating the documentation and setting up the tests PPAs after my holidays, but, in the mean time, Mago is there, ready before Feature Freeze. Happy testing!

Written by Ara Pulido

August 11, 2009 at 7:11 am

Posted in mago

Tagged with ,

2 Responses

Subscribe to comments with RSS.

  1. Congratulations on this milestone.

    I’m not sure if it works properly in WordPress yet, but don’t forget you can use apturl to provide links that your readers can click on to install a package, instead of “sudo apt-get” commands.

    Matt Zimmerman

    August 11, 2009 at 1:05 pm

  2. Excellent! One promising idea for Mago that I talked about a bit at UDS is integrating Mago directly into a package build script for use as both a testing framework and as a profiling guide for GCC Profile Guided Optimization. Doing this could give a cpu-bound package a substantial performance boost essentially for free.

    Scott Ritchie

    August 12, 2009 at 3:06 am


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: