Note

BitKeeper comes with an extensive regressions suite and new changes should be validated against those tests and the tests should be extended for any new code.

The regressions make some assumptions about the machine where they are run. This guide explains how to configure your machine. We are trying to remove some of these requirements so this document will get updated in the future.

Setup

Install bk

Some tests assume Bitkeeper is installed on the current machine in the current user's PATH.

Work from a BitKeeper repository

The regressions assume they are running from the official BitKeeper repository and do not work correctly when run from an unpacked tarball or a git clone. So do something like this:

bk clone bk://bkbits.net/u/bk/dev dev
cd dev/src

Create a /build

The regressions expect a /build filesystem that is writable by anyone. A simple way to create this is:

One of the problems was in t.importcvs when running the CVS test we require you to comment out the cvsadmin group. That was fine for our machines, but obviously not going to work in general. We try to run 'cvs admin' and that will fail if that group is defined and the user is not in it.

The test should be changed to check if the user has membership in that group and if not skip the test rather than erroring.