Build Process

Calsoft typically follows the "bus model" made popular by Oracle. On long running stable projects, we define regular feature lists on a monthly / fortnightly basis, and do integration and QA cycles on "bus releases".

Each bus consists of a well-defined set of "features/labels" for each developer. This label is defined over a set of code files and the corresponding unit tests for that feature. We do nightly builds and use Tinderbox/UML to run our builds and do smoke testing for the same.

- Delivery Process Flow

The unit tests that developers write are put together to form a regression suite for the product. We keep the development of the code and its regression suite in sync to ensure that features are tested in unison as soon as they are entered into the build, allowing us to catch integration bugs early.

Calsoft has a lot of experience with developing regression suites, white-box testing, black box testing. The following diagram shows the complete test cycle that we use for our projects.

- Build Process Flow