This is one problem for which we don't have an elegant solution yet:

what is the best way to craft a name for a generated test?

Let's see an example; given the following parameterized unit test,

[PexMethod] void Test(int i) {
    if (i == 123) throw ArgumentException();
}

Pex would generate 2 tests: i = 0, i = 123. So it seems doable to infer test names such as

A less pithy, and arguably far more constructive, answer to the question "are we doing enough refactoring?" can be find by examining how the quality of our code changes over time.

Take package-level coupling and cohesion, for example. if we want to objectively gauge if we're doing enough to keep packages cohesive and loosely coupled enough for our requirements, we can monitor those aspects of quality as the project progresses and identify where the trend might be headed.

Ejb3Unit is a JUnit extention and can execute automated standalone junit tests for all JEE or Ejb3 projects. This release contains multiple bug fixes and now supports multiple tables for CSV data sets.

I've been a student of the electric guitar for about 20 years now.

I started learning after I was inspired by players like Frank Zappa, Steve Vai, Joe Satriani, Yngwie Malmsteen, Vinnie Moore, Paul Gilbert and others of a certain school of guitar playing commonly referred to as shredding. Shredders play their guitars very fast - often in a neo-classical style that owes more to classical violinists than the blues-based rock guitarists who inspired them. (Although, they can shred the blues, too.)

Here are three unresolved debates that many people seem to have agreed to stop having:When do Agile teams need to be deftly led in the right direction, and when can managers/leaders/ScrumMasters/those-responsible-for-a-budget just sit back and let them figure it out?On the spectrum between intensely-focused specialists and generalists who do everything they do with the same [...]