持续集成CI相关的几个概念

持续集成

https://en.wikipedia.org/wiki/Continuous_integration

为什么要持续?

持续集成， 可以避免集成地狱（由于工作的源码 和 库中的源码的差异导致）， 提倡提前集成，并且经常集成。

在集成到主分支之前， 在CI服务器上做一次完整的构建 和 运行通过 所有的单元测试。

Continuous integration involves integrating early and often, so as to avoid the pitfalls of "integration hell". The practice aims to reduce rework and thus reduce cost and time.^[4]

A complementary practice to CI is that before submitting work, each programmer must do a complete build and run (and pass) all unit tests. Integration tests are usually run automatically on a CI server when it detects a new commit.

除了在集成过程中做 单元测试 和 集成测试， 这些过程也被运行： 静态测试、动态测试、 度量和记录性能， 从源码中导出格式化文档。

In addition to running the unit and integration tests, such processes run additional static and dynamic tests, measure and profile performance, extract and format documentation from the source code and facilitate manual QA processes. This continuous application of quality control aims to improve the quality of software, and to reduce the time taken to deliver it, by replacing the traditional practice of applying quality control after completing all development.

持续集成，保证合入代码主分支代码的质量。

持续发布和持续部署

在持续集成的基础上， 衍生出软件末游流程的改进概念，持续发布和持续部署。

In the same vein, the practice of continuous delivery further extends CI by making sure the software checked in on the mainline is always in a state that can be deployed to users and makes the actual deployment process very rapid.

VerifyCI & MergeCI

持续集成 分为两个阶段， 一个是合入之前的 模块级别 质量保证， 另外一个是主分支的 质量保证。

前者称为 VerifyCI  --- 代码合入主分支前，代码在工作镜像上，通过单元测试、构建等过程。

后者称为 MergeCI --- 持续集成要求，每天合入主分支多次， 主分支构建多次， 此CI需要保证主分支的质量。 毕竟， 主分支集成属于系统测试范畴。

CRT == continuous regression testing

持续回归测试

regression testing

回归测试，当软件被改动后， 需要保证之前的通过的测试用例，仍然是通过的。

软件的改动，包括 软件增强、打补丁、配置改变。

Regression testing is a type of software testing which verifies that software, which was previously developed and tested, still performs correctly after it was changed or interfaced with other software. Changes may include software enhancements, patches, configuration changes, etc.

回归测试，用于测试系统的有效性， 测试用例通过系统性的选择， 选择测试最小集覆盖特定的变化。

非回归测试， 目的是，在引入或者更新一个给定的软件应用， 改变是否是期望的效果。

我的理解：

回归测试 -- 面向存量功能。

非回归测试 -- 面向增量功能。

Regression testing can be performed to test a system efficiently by systematically selecting the appropriate minimum set of tests needed to adequately cover a particular change.

In contrast, non-regression testing aims to verify whether, after introducing or updating a given software application, the change has had the intended effect.

continuous regression testing

持续回归测试， 利用自动化测试的工具， 定期或者按照条件触发 执行回归测试。

VerifyCI阶段工具

cppunit

https://www.freedesktop.org/wiki/Software/cppunit/

执行单元测试

CppUnit is the C++ port of the famous JUnit framework for unit testing. Test output is in XML for automatic testing and GUI based for supervised tests.

This is a continuation of the original cppunit project.

1. cppunit test framework
2. Developers
3. Contact

cppcheck

http://cppcheck.sourceforge.net/

静态代码检查工具。 不检查语法错误， 检查若干类型的bug，只检查错误， 不检查正确的。

Cppcheck is a static analysis tool for C/C++ code. Unlike C/C++ compilers and many other analysis tools it does not detect syntax errors in the code. Cppcheck primarily detects the types of bugs that the compilers normally do not detect. The goal is to detect only real errors in the code (i.e. have zero false positives).

AStyle

http://astyle.sourceforge.net/

艺术造型工具，是一款源码 缩进、 格式化、 美化工具。 支持C C++ JAVA.

Artistic Style is a source code indenter, formatter, and beautifier for the C, C++, C++/CLI, Objective‑C, C# and Java programming languages.

When indenting source code, we as programmers have a tendency to use both spaces and tab characters to create the wanted indentation. Moreover, some editors by default insert spaces instead of tabs when pressing the tab key. Other editors (Emacs for example) have the ability to "pretty up" lines by automatically setting up the white space before the code on the line, possibly inserting spaces in code that up to now used only tabs for indentation.

The NUMBER of spaces for each tab character in the source code can change between editors (unless the user sets up the number to his liking...). One of the standard problems programmers face when moving from one editor to another is that code containing both spaces and tabs, that was perfectly indented, suddenly becomes a mess to look at. Even if you as a programmer take care to ONLY use spaces or tabs, looking at other people's source code can still be problematic.

To address this problem, Artistic Style was created – a filter written in C++ that automatically re-indents and re-formats C / C++ / Objective‑C / C++/CLI / C# / Java source files. It can be used from a command line, or it can be incorporated as a library in another program.

SourceMonitor

http://www.campwoodsw.com/sourcemonitor.html

通过扫描源码，得出多少代码 和 确认你模块的相对复杂度。 其可以确认有可能有缺陷的代码，然后以此发起代码走查。

此工具使用　　C++实现， 每秒扫描一万行代码。

The freeware program SourceMonitor lets you see inside your software source code to find out how much code you have and to identify the relative complexity of your modules. For example, you can use SourceMonitor to identify the code that is most likely to contain defects and thus warrants formal review. SourceMonitor, written in C++, runs through your code at high speed, typically more than 10,000 lines of code per second. SourceMonitor provides the following:

• Collects metrics in a fast, single pass through source files.
• Measures metrics for source code written in C++, C, C#, VB.NET, Java, Delphi, Visual Basic (VB6) or HTML.
• Includes method and function level metrics for C++, C, C#, VB.NET, Java, and Delphi.
• Offers Modified Complexity metric option.
• Saves metrics in checkpoints for comparison during software development projects.
• Displays and prints metrics in tables and charts, including Kiviat diagrams.
• Operates within a standard Windows GUI or inside your scripts using XML command files.
• Exports metrics to XML or CSV (comma-separated-value) files for further processing with other tools.