Plumbr is all about detecting performance problems from within Java applications.
If you have to test methods handling complex objects or voluminous data, you easily end up with a bunch of unreadable assert statements. The visual approach featured by MagicTest allows you to write such tests very efficiently. To prove this, the author invites you to a testing challenge.
Many organizations require a secure infrastructure. I’ve yet to meet a customer that says that security isn’t a concern. But, the decision on “how secure?” should be closely associated with a risk analysis for your organization.
The source is a few months old, and these kinds of collections usual concern the author, but in this article you'll find a collection of 28 free eBooks on game programming.
Sometimes you want to set the state of your project back to a previous commit, but keep the history of all the preceding changes. You want to make a commit that reverses all the changes between your previous commit and the current HEAD.
We developers spend a lot of time and energy adding logging to our application in order to prove that it's working okay and to figure out what went wrong when an exception occurs.
Connection and resource pooling is a key value proposition of modern application servers like GlassFish and WebLogic to significantly boost scalability
Sometimes you just want to create a quick web project in IntelliJ IDEA, and you would use their wizard and with web or Java EE module as starter project.
I would like share a few thoughts about designing tutorials for an Android game app
It is tricky to manage JBoss with a provisioner such as Puppet or Ansible because its domain.xml contains not only rather static configuration but also sections that change quite often such as deployments.
Writing tests belongs to a developer's daily life - but it just takes just too much time. The visual approach featured by MagicTest makes testing so efficient that is almost fun. To prove this, I invite you to a testing challenge. Can your preferred testing framework meet the challenge and testing becomes a breeze as well?
Peter Spung (@paspung) has started a great series on DevOps speaking to the middle management layers.
Use version controlling/source control even if one developer exists. This issue brings change tracking and versioning of the application continuously.
Celery ships with an configuration option called CELERY_ALWAYS_EAGER which causes all tasks to be executed immediately instead of being asynchronously executed on workers. This can be very useful for unit tests. Instead of running a real message queue and separate worker processes, your unit tests can execute all in one process and still run the necessary tasks.
The WebLogic Server 12c has very nice support for Maven now. The doc for this is kinda hidden though, so here is a direct link http://docs.oracle.com/middleware/1212/core/MAVEN
Refactoring is difficult and not everyone can do it.
Agile teams embracing TDD thought-process to design and implement their product features have realized significant improvements in code and design quality. Still waiting and thinking about TDD?
This article deals with different approaches to load multiple versions of the same class.
This article describes an approach for creating live documentation for Java projects. One of the easiest way is to use a BDD framework - but which one? Hopefully this article will answer your questions...
Java is a minimalist language with deliberately less features than other languages, never the less it has edge cases which strange effects, and even some common cases with surprising effects to trip up the unwary.
I would have said “Test Driven Development” but I want to make it clear that what I’m talking about is writing test first, or at least simultaneous to writing the code. Not sometime after, even if that after is immediately after.
Technical logging is usually not tested.
A great development manager once said, "It's just software." That simple statement tells a much larger story. Software development for most companies is all about time and money. Most requests can be satisfied but developers have a tendency to rebut with "no" when they believe the work is too difficult, requires extensive time, or for a variety of other concerns.
When I first heard about unit testing using a framework like JUnit, I thought it was such a simple and powerful concept.
If you ever need to persuade management why it might be better to deploy a larger change in multiple stages and push it to customers gradually, read on.