In July of this year Cruise, General Motor Co’s self-driving unit, delayed the commercial deployment of cars past its target date of 2019 as the vehicles required more testing before they could be safely on the road. In a blog post on the news Dan Ammann, Cruise’s CEO, wrote, “When you’re working on the large scale deployment of mission critical safety systems, the mindset of ‘move fast and break things’ certainly doesn’t cut it.”
Sometimes I feel as if I’m the Forrest Gump of quality assurance (QA). Since 1998, I’ve been through the beginning of automated integration testing and service virtualization through being a co-founder of Class I.Q. (now IBM Greenhat). I’ve been through the first phases of an automated testing center of excellence (ACOE). I’ve been there for the start of risk-based testing, and I’ve been a part of the transformation of QA from a somewhat necessary function to something that is now the core and chief concern of any company putting out quality software and apps.
Note: Test engineers Reena Kuni and Jeannette Smith also contributed to this blog.
TestPlant CTO, Antony Edwards, was interviewed by Mobile World Live at Mobile World Congress in Barcelona this year. Antony talks about the key trends in mobile and IoT, and how testing needs to change in order to be more focused on UX.
Today we are excited to bring you a guest blog post from Dr Greg Law, at Undo. TestPlant announced a technology partnership with Undo on August 17, 2016. To read more about the partnership, click here.
The rise of test-driven development, agile methodologies, continuous integration and continuous deployment are transforming how software is created and provided to customers. Simultaneously, the spread of software into more and more of the devices around us and the interconnectivity of those devices means that the sector is growing in scale, complexity and importance. These factors are having an enormous impact on testing and QA departments. If more software is being produced and needs to be deployed in shorter and shorter timeframes, traditional testing methodologies have to change, hence the rise of automation in the testing process.
Today we are excited to bring you a guest blog post from Kevin Dunne, VP, Strategy and Business Development at QASymphony. TestPlant announced a technology partnership with QASymphony on July 12, 2016. To read more about the partnership, click here.
- - -
Agile is everywhere, with VersionOne reporting that 95% of surveyed organizations are practicing agile methodologies within their teams. Though Agile does means getting products to market efficiently, it does not mean doing so with reduced quality, as almost half of the organizations surveyed mentioned moving to Agile to increase quality within their applications.
I recently presented at the Northern Lights conference in Manchester. This conference was hosted by the BCS (British Computing Society), and my talk was “Tools. Techniques. Trouble? Why test automation is getting more difficult, and what can be done about it.” You may have seen my blog post from ahead of the show, but if you haven’t yet, you can find it here.
I focussed on automating user interactions with the System under Test (SUT) and automating the creation of test scripts but not the automation of the testing process itself. I addressed both functional and load testing.
For those who weren’t there, here are the key points that I covered in my presentation: