Continuous construction practices in Agile development: published in STPS 6th, in the article fly into agile development with agile testing, Glenn Jones shared with us the practice of continuous building in their agile projects: (1) Whenever a developer signs in code, no matter how small the changes are, continuous building will be performed. If a code change is submitted during the build process, it will be included in the next build. (2) After continuous building, some unit tests, some functional tests, and some interface tests will be run to ensure that the main paths and key interfaces work normally. (3) run the build every 20 minutes. Therefore, you need to select some test cases for execution, and select some tests for each module, for complicated modules that are easily invalidated due to dependency on other modules, a test case is selected. Continuous building saves time for developers. Because developers are constantly refactoring code and adding code to cope with new requirements and the impact of code changes by other developers. If the frequency of continuous building decreases, for example, once a day, some developers may modify the code, which may damage some functions, other developers may not be able to test their newly added code. Many developers spend a lot of time looking at what causes errors. On the contrary, continuous building can help save time by quickly locating problems, allowing developers to quickly correct errors in their code, this reduces the impact on the efficiency of other developers.
