Disclaimer: this is not a TDD vs. BDD post – now that we’ve got that out of the way let’s discuss the thing I hate most about BDD…
I’m going to try to explain the alternatives for Trunk Based Development (TBD) in terms of branch layout. There’s few different styles, that different types of development organization might try to implement.
Today, DZone released its latest Refcard: Getting Started with Scala. If you're interested in learning more about Scala or sharpening your skills, we decided to dig into the DZone archives and find some of the most popular posts we've had on the topic.
When we talk about testability we usually mean "hard to test". That is a whole discussion by itself, because "hard to test" is also subjective. If we follow the theme of testing as an investment to minimize future maintenance costs, then "hard to test" translates to "Costly to test" or "risky to test".
Crowdsourcing has had a pretty big impact upon most industries, but perhaps software development has seen a bigger impact than most. The rise of social coding sites such as BitBucket and GitHub have transformed the way software projects are undertaken.
The developer survey from DZone's 2014 Guide to Continuous Delivery gave us a few more insights than we were able to include in the guide. For a bit more detail on tool usage in Continuous Delivery, we've created this new infographic.
The traditional Ops toolkit often involves a range of tools that help monitor trends in KPIs as well as tools that perform different periodic health checks on key components of your systems.
I recently put together an end-to-end demo showing step-by-step how to set up a Continuous Delivery pipeline to help automate your deployments and shorten your cycle times for getting code from development to production.
Influence debugging is an efficient active debugging method by which you can ignore a large part of your code during bug hunting. You can go backward along influences exclusively until you catch the bug. Tricky missing code errors can also be detected by this new method.
Often developers writing code that they think is useful and relevant while they are not listening to their target audience, in this case not the end users of the systems but the people that are maintaining the platforms. The people that work on a daily base with these tools.
The selection of a more modular architecture tends to result in an organization with more (smaller) teams.
How you can use the Graph analysis and visualization Tool Gephi to have a look into the Package Dependency structure of your Java Project with a "graph perspective."
While Spock can be used for some property-based testing, ScalaCheck and ScalaTest may be your best option.
Property based testing is an alternative approach to testing, complementingexample based testing
In this post I would like to show an example of how to use JUnit Rule to make testing easier.
This article represents top 4 security vulnerabilities related coding practice to avoid while you are programming with Java language.
If you are a web developer, it is a no brainer that much of your professional life will be spent using Java. Thus, this article lists 15 Java tools that can make your life easier.
Ruby unit testing feels very nice and natural to write with RSpec. However I still love Java (or for this particular example anything with strong typing) and is still my main language, and in many cases is superior to Ruby.
I was recently reminded of a key insight included in a presentation from the Datical team at IBM Innovate 2014. They automate migration of databases changes (and naturally have an integration with UrbanCode Deploy).
An overview of the modern error tracking tools for Java developers: Raygun, Sentry, Takipi, Airbrake and Stack Hunter
Many of you readers are familiar with the Open/Closed principle. But so often, I encounter database connections not closed. Here are a few tips to keep that from happening.
Designing automated testing tools can be a difficult task. Not only do you have to surface all of the complexities involved in a variety of test structures but you also have to make all of those complexities accessible to a variety of audiences.
Typesafe is conducting another survey - part II of a survey, that is - regarding the adoption and users of Java 8. It's a quick survey, just two questions, and we should be hearing results within a few weeks.
Java 8 has added features such as lambdas and type inference. This makes the language less verbose and cleaner, however it comes with more side effects as you don't have to be as explicit in what you are doing.