At QCon London 2016 Peter Alvaro and Kolton Andrus shared lessons learned from a fruitful collaboration between academia and industry, which ultimately resulted in the creation of a novel method for automating failure injection testing at Netflix. Core learnings included: work backwards from what you know; meet in the middle; and adapt the theory to the reality.
The world is naturally chaotic, and we should both plan for and test that our systems can handle this chaos, Rachel Reese claimed at the recent QCon London conference describing how Jet, an e-commerce company launched in July 2015, work with microservices and chaos engineering.
On February 25th, 2016 Microsoft announced updates to their Operations Management Suite (OMS). The updates, in this particular iteration of the service, are focused on the security and audit portions of the suite and target the user experience, additional capabilities and features.
Peter Thorngren, from Volvo Trucks, explains how the future world of smart trucks and autonomous transportation systems rely deeply on continuous delivery techniques like virtualization, test automation and continuous integration.
RightScale just released the results of their annual “State of the Cloud” survey which identifies trends in cloud adoption and usage. The key findings? Organizations are investing in both public and private clouds, security is no longer the number one challenge to adoption, Docker and Ansible are growing in popularity, and central IT departments are taking on a greater role in decision making.
At the Agile Practitioners 2016 conference Huib Schoots talked about testability. He stated that low testability, anything that makes our software hard to test, slows teams down, and explored how testability can be increased.
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.