Build, test, and deploy your entire product at any time with the push
of a button.
Your build should be comprehensive but not complex. Make it compile
source code, run tests, configure registry settings, initialize
database schemas, set up web servers, launch processes, build
installers, and deploy. Your IDE won't do all this, so learn to use a
dedicated build tool. Make sure your build works when disconnected
from the network, too.
Builds should be fast. If not, look at your tests. End-to-end
integration tests are the typical culprit. Replace them with faster,
more maintainable unit tests.
See the description of the new BuildScript.
There are some legacy projects which have "acceptance tests" which run
in 5-10 minutes (in the case of RiskGroups, because of Modgen
inflexibility) or even days (in the case of ParamSpaceExplorer,
because of its failure to distinguish acceptance tests from production
runs).
| «Main Page | • Queries? Email: Roger Mateer | • Last Modified: 2011/08/10 | • All rights reserved © SACEMA 2011 |