This is part of a series of articles I started with Quality Assurance and Automated Testing in Open Source Software.
The GHC team uses Trac
to manage their project.
The main developer page
provides a lot of information on how to get involved.
To get the source look at the Getting The Sources page. It has the detailed instructions but there are many of them and each one takes a long time. So be patient!
Writing and running tests on the
GHC Test framework
is documented rather well.
The test framework is written in Python. For each test file the author has to give an expected behavior which (such as normal, skip, expect_broken(#trac bug number), expect_broken_if_platform(bug_number, platform), etc... These are all Python functions provided by the framework.
The GHC team uses Buildbot
for automatic smoke testing.
So far I managed to setup the BuildBot slave but it seems the build did not start in the scheduled time. Once the buildbot is running I'll be able to see the results on the status page.
I still would like to see how test are running, maybe write a simple one and I would like to get my buildbot slave do its job.
Published on 2007-08-22 by Gabor Szabo blog comments powered by Disqus