the repository and the database. Just a random example: when dak
processes an upload to unstable it makes sure the upload has a higher
version number than already present in unstable. We currently have no
way of testing such code automatically.
This is where the Summer of Code project comes in: we want you to write
a framework for such tests and also to implement some.
To makes these tests reproducible, they should probably be run in a
clean environment. This means automatically setting up a dak instance,
including a postgresql database (maybe even setup a temporary PostgreSQL
installation automatically so one does not need special permissions to
run the testsuite).
Some tests would need some packages already installed into the temporary
dak instance. Take the example from above: a version comparision with
the version already in the archive would be boring if the archive was
empty. You need to figure out some way to do this.
I hope you get a rough idea what we want. Feel free to ask if you want
to know more. If you are interested, you might want to try and setup a
dak instance by hand and play around a bit with it. There's a short
README in the setup directory in dak's Git repository[4]. You also need
some basic knowledge about creating Debian packages as these will be
needed for the tests (not much needed there as our test packages will be
almost empty).
[4] git clone https://ftp-master.debian.org/git/dak.git
Ansgar