What tools/libraries do you run along with your build to assess and maintain quality?
您与构建一起运行哪些工具/库来评估和维护质量?
As part of my CI (Cruise Control) builds I run:
Simian
Nunit
Ncover
Ndepend
FxCop
as part of Nant
作为我的CI(巡航控制)版本的一部分,我运行:Simian Nunit Ncover Ndepend FxCop作为Nant的一部分
I am looking for tools to instrument complexities, metrics, etc .
我正在寻找工具来检测复杂性,指标等。
7 个解决方案
#1
also dotProfiler and you can use buitin metric in visual studio team suite
还有dotProfiler,你可以在visual studio团队套件中使用buitin metric
#3
The only thing I run as part of my regular build is Nunit, and some simple tweaks to deal with version maintenance.
我作为常规版本的一部分运行的唯一东西是Nunit,以及一些简单的调整来处理版本维护。
My view is that the rest of the tools are useful when trying to solve a specific problem, but that you shouldn't spend all your time worrying about arbitrary numbers, "zone of pain", etc.
我的观点是,其他工具在尝试解决特定问题时非常有用,但您不应该花费所有时间来担心任意数字,“痛苦区域”等。
Don't get me wrong - I very much use the other tools (or variants of them, such as dotTrace) - but more "on demand" (with code coverage being the most regular that I use).
不要误解我的意思 - 我非常使用其他工具(或者它们的变体,例如dotTrace) - 但更多的是“按需”(代码覆盖率是我使用的最常规)。
#6
Why don't you use some NDepend's CQLinq rules to address all facets of quality (metric, structure, coverage, evolution, side effects, dead code, naming coherence...). See the list of around 200 default CQLinq rules proposed here.
为什么不使用一些NDepend的CQLinq规则来解决质量的所有方面(度量,结构,覆盖范围,进化,副作用,死代码,命名一致性......)。请参阅此处提供的大约200个默认CQLinq规则的列表。
#7
UppercuT.
It uses the following to analyze code:
它使用以下内容来分析代码:
- NUnit OR MbUnit
- NCover
- NDepend
NUnit或MbUnit
UppercuT uses NAnt to build and it is the insanely easy to use Build Framework!
UppercuT使用NAnt构建,它是一个非常容易使用的Build Framework!
http://code.google.com/p/uppercut/
Some good explanations here: UppercuT
这里有一些很好的解释:UppercuT
#1
also dotProfiler and you can use buitin metric in visual studio team suite
还有dotProfiler,你可以在visual studio团队套件中使用buitin metric
#2
#3
The only thing I run as part of my regular build is Nunit, and some simple tweaks to deal with version maintenance.
我作为常规版本的一部分运行的唯一东西是Nunit,以及一些简单的调整来处理版本维护。
My view is that the rest of the tools are useful when trying to solve a specific problem, but that you shouldn't spend all your time worrying about arbitrary numbers, "zone of pain", etc.
我的观点是,其他工具在尝试解决特定问题时非常有用,但您不应该花费所有时间来担心任意数字,“痛苦区域”等。
Don't get me wrong - I very much use the other tools (or variants of them, such as dotTrace) - but more "on demand" (with code coverage being the most regular that I use).
不要误解我的意思 - 我非常使用其他工具(或者它们的变体,例如dotTrace) - 但更多的是“按需”(代码覆盖率是我使用的最常规)。
#4
I just heard of StyleCop today on SO
我今天刚才听说过StyleCop
#5
One I saw yesterday
Vil
我昨天看到了一个
#6
Why don't you use some NDepend's CQLinq rules to address all facets of quality (metric, structure, coverage, evolution, side effects, dead code, naming coherence...). See the list of around 200 default CQLinq rules proposed here.
为什么不使用一些NDepend的CQLinq规则来解决质量的所有方面(度量,结构,覆盖范围,进化,副作用,死代码,命名一致性......)。请参阅此处提供的大约200个默认CQLinq规则的列表。
#7
UppercuT.
It uses the following to analyze code:
它使用以下内容来分析代码:
- NUnit OR MbUnit
- NCover
- NDepend
NUnit或MbUnit
UppercuT uses NAnt to build and it is the insanely easy to use Build Framework!
UppercuT使用NAnt构建,它是一个非常容易使用的Build Framework!
http://code.google.com/p/uppercut/
Some good explanations here: UppercuT
这里有一些很好的解释:UppercuT