The TESTING issue of the JAX magazine has arrived
What are the most common testing mistakes? How much testing is enough? And what should you name your tests? Find all the answers in this latest issue of JAX Magazine.
Only nerds like tests.
That’s right, if you actually enjoy tests, then you must be some kind of hardcore nerd-geek. Because nobody normal likes tests.
Hang on though – nerds have long since been cool and influential, both in Hollywood movies and Silicon Valley. After all, the most powerful CEOs in the world are nerds these days. So whether we like it or not, if any of us want to make it big in tech, we all need to do some soul searching, befriend our inner nerd and find our suppressed love of testing.
And yet in spite of their undeniable role in the success of software, the test is still one of the most hated aspects of software development. “All too often test code is seen as a second class citizen not deserving of the love and care that production code receives,” says Colin Vipurs, author of Tests need love too. “This leads to brittle and unmaintainable test suites that hamper instead of helping the development process.”
That’s why we’ve dedicated the latest JAX Magazine issue entirely to the topic of testing.
For Spring users, Nicolas Fränkel shows us how Spring application tests have three layers – a bit like dreams in Inception. The above-mentioned author Colin Vipurs has a few lessons for us about naming in testing and tells us why you should never ever name your test “Test1”. Testing pro Daniel Witkowski takes a look at the most common mistakes made during performance testing.
And finally for those of us that never know quite when to stop testing, we have an introduction to an Eclipse plug-in that helps you evaluate how much time you’re spending (not wasting) on tests.
To get the digital issue, simply register with your email address and enter the details you receive by email.
Tests need love too
Naming and testing
How much testing is enough?
Initial steps in testing analytics
A closer look at the three ways of testing Spring MVC applications
JVM and application bottlenecks
Why it’s difficult to find performance problems during pre-production tests