A recent post in Reddit sparked a debate between the traditional testing framework JUnit and upstart Spock with the central theme, “What’s wrong with JUnit?”
InfoQ interviewed Diomidis Spinellis, author of the books Code Reading and Code Quality, about finding and fixing errors in software, principles for debugging software and how to improve the effectiveness of debugging, how to write code that requires less debugging, and what managers can do to support error prevention and handling.
Explaining Craftsmanship techniques is hard, especially to Senior Management and Executives. Since understanding is usually key to a mindset shift and technical practices are the way to develop good quality software, it's very important to explain them. Mike Bowler facilitated a workshop on how to use Lego for technical practices during the 7th Agile Games Conference.
VersionOne have released the results of the 10th annual State of Agile survey. Based on over 3800 responses from around the globe the results indicate that agile methods deliver tangible benefits; they are steadily becoming the default approach to software development and are starting to expand to areas outside software.
Android Studio 2.0 comes with several new features and improvements: Instant Run, integration with a Google service for testing on real devices, faster emulator, faster builds, GPU profiler and debugger, support for deep linking and others.
This post summarizes the experience of a university professor who gave up on TDD and Uncle Bob’s rebuttal of his arguments.
Although Selenium is a popular library for UI testing, issues about fragile and unreliable tests are common. InfoQ reached out Chris Holt, creator of canopy, to learn more about the F# library built on top of Selenium.
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.
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.
An interview with Erin McManus and Ryan McKergow about the need for business analysis in agile, how agile impacts the role of the business analyst, the changes that they have seen in business analysis when agile is being adopted, and specific business analysis practices that that they can recommend for agile teams.
VersionOne have announced their Winter 2016 release which includes support for SAFe 4.0 along with more features which support both strategic and team level use of the product. InfoQ spoke to Lee Cunningham (Director, Enterprise Agile) and Mark Rogge (Director of Sales) about the release and why the changes in SAFe 4.0 are considered to be so significant.
The JUnit Lambda Team has recently announced the alpha release of JUnit 5, a new major version for the popular unit testing framework. Changes in the new version are mostly focused at removing the common obstacles that JUnit 4 presented to developers, while also modifying the framework to allow for easier changes in the future. Integration with build tools and IDEs still needs some further work.
Failure testing should be a critical part of running your microservices, Kolton Andrus stated in his presentation at the recent Microservices Practitioner Summit. Verifying that your services behave as you expect is something you should do to prevent outages.
Tarcio Saraiva and Adam Crough talked about crafting quality software at the 1st Conference in Melbourne, Australia. InfoQ asked them to share their views on what software quality is, and to explain the business benefits and how it can be managed. InfoQ also asked them about the role for testing, how continuous integration supports quality, and advice for delivering high quality software products.
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.