Build Server

Continuous integration (CI) is the practice, in software engineering, of merging all developer working copies with a shared mainline several times a day onto a build server.

Windows Active Directory and NCover Code Central

As teams developing in the the .NET framework, a large percentage of our customers are also using other Microsoft tools, services and applications. One of the more popular services our clients use is Windows Active Directory and we are frequently asked how NCover can…   Continue Reading

NCover 5.1 Beta Program

When we originally released NCover 5 last year, we were excited to share a lot of great new features including Condition Coverage and even more ways to share coverage results across the organization. In addition, we put a lot of work into making NCover…   Continue Reading

Integrating NCover Pre-Instrumentation Into Your Build Process

Pre-Instrumentation for Continuous Integration In a recent post describing NCover Pre-Instrumentation, we introduced you to coverage collection without an in-memory profiler. The specific use cases and advantages are well-detailed in that post. Now that this tool is in the arsenal, the next question we’ll…   Continue Reading

Getting Started with .NET Code Coverage

We live and breathe code coverage and the pursuit of building quality code. Since we have been doing it for years, we forget that each and every day new people discover and are getting started with .NET code coverage. With that in mind, we…   Continue Reading

Build Agent Unattended Deployment of NCover 4

Build server automation tools for continuous integration (CI) are plenteous. Teams bounce from one to another based on pricing and features, and would grab a new brass ring each time they rebuild their CI server if they could. It’s the nature of the beast….   Continue Reading