Through regular daily product build-to-date, we can try to eliminate many types of problems. Anyone can view the current version of the product and immediately know what is the current status and progress of the project. You can get a clear position as to what is currently being done and what the possible problems we face just by downloading the current version and use the various functions or features. Maintenance and repair of every built version of the product, as well as creating the tools necessary to allow this process can cost both time and money, but is certainly worth the cost.
With every built release the team will know right away whether certain new elements do not damage the existing state code and other components. This approach allows you to maintain a high quality of work on the project. It should also be set some time in the stable version would be established to run the tests, which should confirm the quality of the release. These tests are often in everyday language are called “smoke tests” – a reference to the way in which the tested elements and electronic components that are connected to the voltage to see if any parts are not overheat and smoke.
For each building should be carried out a set of tests to determine the quality. We can distinguish three degrees of success so the tests:
- well: all the tests have been successfully
- mixed: some tests have been successfully
- bad: few or none of the tests passed.
Any error that has been identified as the cause of the transition is not a test should have included information about the issue and given appropriate priority.
All these issues of quality tests should be among the criteria for the output stage of the project. At the beginning of the project, exit criteria may be relaxed, for example, may be an acceptable situation in which there is only one good release week. However, over time criteria should grow. Daily testing issues with the quality of these issues are part of the project, in particular the quality of the product.