Blackbox automation testing should be part of any successful software development organization. Unit testing is great, but to cover the largest area of your software with the least effort you need to have blackbox automation testing. Not only that, but you also need to have an automation testing framework.
As Java developer, you are probably using a lot of frameworks. Spring or Hibernate can significantly reduce amount of boilerplate code.
In this post I will let the code do most of the talking and just tell you that I want to share a Groovy script for finding information from Maven pom.xml files embedded in JAR files. The reason for this is that I wanted to create a list of third-party libraries and their versions that are provided in a Mule server.
For many SDN and DevOps enthusiasts, the natural outcome of this wave of technological change is a highly-automated network that is well-orchestrated with surrounding systems and applications. One of the prevailing thoughts is that this level of automation is a well-formed abstraction layer.
DHH recently wrote a provocative piece that gave some views into how he does and doesn't test these days.
Ideally, Vagrant itself would optionally call scp directly to side-step the OSX issue. It would also be ideal if they supported S3 directly, as well. In fact, just let us write our own shell command/script to download the file.
Today’s interview from last week’s DevOps Days is with Matt Ray from Chef. Matt did a cool a presentation on the first day about how to introduce DevOps to traditional enterprises (see below) and I was able to grab him on the beginning of Day two to hear about his talk and the latest regarding Chef.
TDD doesn't create good design. You do. TDD can help expose design smells. You have to pay attention and fix them. TDD can push you toward facile solutions. You have to be careful not to make your design worse just to make testing better.
A few weeks ago I did a presentation entitled “Conway’s Law and Continuous Delivery” - although it was also at some point entitled “Conway’s Law and Organisational Change” or possibly “Conway’s Law and Change for Continuous Delivery” - to the Pipeline Conference in London.
Make sure you didn't miss anything with this list of the Best of the Week in the DevOps Zone (May 9 to May 15). This week's topics include test-driven development obstacles, TDD for refactoring, the Java 8 type "Optional", configuring Sonar in Ubuntu, and effective Puppet module management in Vagrant.
Things continue to evolve in the DevOps industry every day. In this month's update, leading enterprises embrace web-scale IT automation with Chef, Bamboo 5.5 released instant access for Stash repos, IMB launched their impressive cloud marketplace (including Zend and others), and #ChefConf 2014 was a hit.
Organizations struggling with project delivery, application availability and security maintenance typically also have an IT culture that struggles to understanding its own environment architecture.
In this article, the author will show an example of how a bug in the code can remain undetected as it goes into production, and then how analytics technologies and Augmented Search can be used to discover and troubleshoot the problem within minutes.
Recently I introduced to the team, with the help of a teammate the Pull Requests concept.
It takes some time to grasp the methodology and see the benefits.
So as the future architectures of massive-scale, distributed systems become clearer, let us finish where we started, with a little idle speculation on what happens next for Docker Inc. Of the big players with deep pockets who needs it the most? I don’t have the answer but I am watching eagerly to see how it unfolds.
A few days ago, David Heinemeier Hansson posted a very negative article on Test-Driven Development(TDD) which generated quite a bit of noise
A really simple way to add an additional layer of information to an architecture diagram (and to remove any ambiguity) is to annotate boxes with a very short statement of what their responsibilities are. A bulleted list (7 ± 2 items) or a short sentence work well.
If DevOps is a verb and DevOps is a change in culture, does it make sense for anybody to call themselves a DevOps startup? Sort of. Especially if they’ve done it before.
An actual deployment of a network requires attachment to things that are not pristine. It needs to be attached to existing cabling. It needs to interact with other network equipment, from other vendors. It will have servers, storage and in a campus setting wireless access points, PCs, VoIP phones, printers, etc.
There has been a lot of talk around whether or not DevOps can be used as a job title or a prescriptive requirement for a job position. Some opponents to DevOps titles say DevOps, like Agile, is a methodology and no one uses “Agile Engineers” as a title.
We’ve set up a simple Node.js application called codefish which contains some Jasmine specs. We’ll use screenshots of this application in this blog post. If you haven’t got your own project to set up but you want to follow along on your computer, just fork the repository.
During our lab, we wanted to implement an application with Akka and Scala, because we’re going to evaluate highly performing and scalable software architectures on the JVM. I
I still remember my first early forays into using vagrant and puppet together to provision local development environments. Everything was easy accept figuring out a proper way to bundle puppet modules with a project. Basically it was a three step phase of discovery.
Make sure you didn't miss anything with this list of the Best of the Week in the DevOps Zone (Apr. 18 to Apr. 24). This week's topics include the a article from the DZone lead research analyst on CD and automation, loading classes from modules, clojure, TDD and rails, and Linux config version control.
A summarized view (notes) of the Stateless EJB pooling and life-cycle. Useful for newbies