planetgeek.ch

CategorySourceanalysis

How to find misplaced or misnamed unit tests with NDepend

By Urs Enzler
In .NET, Clean Code, Sourceanalysis
August 31, 2012
5 Min read
H

In my current project, we do a lot of refactoring to keep the source code as simple and understandable as possible. This involves a lot of renaming of classes and moving classes between namespaces to structure the code in a better understandable way (here is explained how we structure our code). Sometimes, this results in unit tests not renamed or moved along with the production classes they test.
Therefore, I wrote some NDepend queries that show us these misplaced or misnamed test classes.

Read on

.NET Open Source Projects and Coding Guidelines

By Urs Enzler
In .NET, Clean Code, Sourceanalysis
July 27, 2011
2 Min read

In my projects, we use a lot of open source libraries like Ninject, xUnit, Machine.Specifications, FluentAssertions, StyleCop, Moq, statLight, AgUnit and of course the project I lead myself: bbv.Common. These projects are really cool. But sometimes of course, we need something that they do not (yet) provide. Like adding Machine.Specification support in FluentAssertions or a faster runner for xUnit unit tests under silverlight with AgUnit and statLight. Therfore, we download the source code and...

Read on

Custom StyleCop Rules

By Thomas
In .NET, Software, Sourceanalysis
July 19, 2009
4 Min read
C

Microsoft’s StyleCop is a code style and consistency analysis tool for C#. The tool integrates into the Visual Studio IDE, or can be run on the command line. StyleCop ships with a default set of rules enforcing common style guidelines.
This article describes how to write custom StyleCop rules.

Read on
planetgeek.ch

Recent Posts