InfoQ interviewed Boris Modylevsky about the importance of measuring code quality and how measurements can be used to improve quality, integrating static code analysis in continuous integration, testing coverage and test automation, and the benefits that continuous integration with integrated code analysis and test coverage can bring.
InfoQ ran a DevOps research question during Q4 of 2015, to find out which practices contribute the most to a healthy DevOps culture. The results show there are no predominant practices as DevOps initiatives are highly contextual.
InfoQ recently sat down with Steve Smith and discussed the ideas behind his recent blog post “End-to-End Testing Considered Harmful”. Smith talked about release testing being a form of ‘risk management theatre’, discussed the benefit of unit and acceptance testing, and stressed the value of monitoring at runtime versus the typically fragile and slow-running implementation of end-to-end testing.
Microsoft recently made their updated Azure Portal generally available (GA) after nearly nineteen months in “preview.” Before setting this to default portal experience for all customers, Microsoft says they focused on improving performance, reliability and usability.
At the Agile Testing Days 2015 Jose Lima from Redgate software shared his experiences with microservices. InfoQ interviewed him about advantages and disadvantages of developing products with microservices, how applying microservices has improved the quality of products, testing microservices and the skills that testers need, and his learnings from developing and testing microservices.
Device fragmentation can be a serious hindrance to providing great mobile user experiences. A review of the most common issues faced by developers.
The widespread adoption of Docker in infrastructure automation has led to a growing debate as to whether it supersedes configuration management. The consensus seems to be that both will co-exist in a complementary way.
James Lyndsay did a workshop titled "a nest of tests" at the Agile Testing Days 2015. In this workshop he explored how you can design large collections of tiny tests and visualize their output to test systems, and showed how tools can help you to do it. InfoQ interviewed him about this testing approach.
At the Agile Testing Days 2015 Richard Bradshaw explored how using the term “test automation” is restricting teams in exploiting the benefits of automation. InfoQ interviewed Bradshaw about the difference between testing and checking and why they are both important, how automation can support testing, using automation frameworks, and why we should always focus on the testing problem.
At DockerCon EU 2015, Laura Frank presented “Stop Being Lazy, and Test Your Software”. Frank proposed that testing software is necessary, no matter the size or status of your company, and introducing Docker to the development workflow can assist with writing and running testing frameworks more efficiently, and ultimately facilitate the delivery of high quality software products to customers.
Should you rebuilding or refactoring software?An interview with Wouter Lagerweij about what it is that makes refactoring so difficult, if rebuilding software is less risky than refactoring, and how continuous delivery fits with rebuilding software.
Technology leaders are moving towards Continuous Delivery and Agile to accelerate business innovation.This post talks about the importance of cultural shift in successful Continuous Delivery implementation in the organizations.
Based on their experience with arbitrarily shutting down servers or simulating the shutdown of an entire data center in production, Netflix has proposed a number of principles of chaos engineering.
Twitter has open sourced Diffy, an automated testing tool used in production for discovering potential bugs in new code running on Apache Trift and other HTTP-based services.
Remembering that automation is a side benefit and not the reason for BDD is one improvement to more closely follow the recommendations of BDD thought leaders, Joe Colantonio explains noticing six ways of improving work with a BDD mindset.