A build management project is a staging project used to build and test a test area or release. By default, build management projects support two levels of testing: integration testing and system testing. Therefore, when you create the build management projects for your application, you will usually create at least two versions of each project.
You can add more testing levels by adding a purpose and process rule for build management projects. For example, to add a performance testing level, create a purpose named Performance Testing for build management projects, create a process rule for the new purpose, then create a version of a build management project for it.
The first build management project, called the integration testing project, enables you to collect, build, and test the latest completed tasks checked in by developers. The members of this project are brought in through a query of all completed tasks.
See Creating the integration testing projects to set up the integration testing projects.
The second build management project, called the system testing project, enables you to collect, build, and test the application in more detail, to reach an agreed-upon quality standard. The members of this project are brought in through a carefully controlled process.
See Creating the system testing projects to set up the system testing project.
You might want to set build arguments for the integration testing projects or the system testing project. For example, you might want to build the integration test area with the debug flag or build the system test area with the optimize flag. For information on building, see Following build guidelines.
If you do not perform integration testing on all platforms, you do not need an integration build management project hierarchy for every platform.