Thank you.

Your uploaded files are waiting for moderation.

<< Go Back

You need to register or login to access this content.

Continuous Testing in Hewlett Packard Enterprise

Reading Time: 1 minute

Technological revolutions bring real challenges for software development, testing and operations teams. These influences include: the Internet of Things, Software as a Service, and modern delivery practices such as DevOps. Organizations are being asked to release new application features to market rapidly, even continuously, without sacrificing quality. This task is achieved by testers and developers collaborating to achieve consistently high quality in their lean, Agile and DevOps delivery processes. They are testing continuously throughout the entire lifecycle – from development all the way though to production.

Continuous Testing means running tests at each stage in the pipeline, giving the team feedback to improve quality and increase their velocity. Tests are triggered automatically by events such as code check-in. The faster defects are found, the faster they can be addressed.  Continuous testing doesn’t happen by itself. Instead it requires a significant shift for development teams to succeed.

This eBook explores the concept of continuous testing and what it involves. It describes how Hewlett Packard Enterprise Software development teams adopted Continuous Testing throughout the development process to achieve faster delivery and higher levels of quality.

Key Takeaways

  • Understand the concept & benefits of Continuous Testing
  • Discover how  implements Continuous Testing to improve quality & increase velocity
  • Learn how you can get started with implementing Continuous Testing in your organisation
Editor's Image

Malcolm Isaacs

Malcolm Isaacs is a senior researcher in Hewlett Packard Enterprise Software’s Application Delivery Management (ADM) team, with a particular interest in Agile, DevOps, and software quality. During the course of his 25+ years career in software development, Malcolm has held various positions, including software engineer, team leader, and architect. In 2003, he joined Mercury (later acquired by HP), where he worked on a number of products specializing in supporting traditional and agile software development life cycles, from planning through deployment. You can follow @MalcolmIsaacs on Twitter, reach out to him on LinkedIn, and read his articles on TechBeacon and on the Hewlett Packard Enterprise blogs.

Leave a Reply

Skip to toolbar