The trend of software development is moving towards frequent releases backed up by automated functional testing. Continuous Testing (CT), a key process of DevOps, executes automated end-to-end (UI) as regression testing, frequently on new builds. If all tests pass, the software is ready for a production release. there are test failures, the team must act quickly on the feedback. This book presents a practical approach to implementing real Continuous Testing. Topics include: Why do traditional CI servers, e.g. Jenkins, always fail to manage UI test executions? Set up a BuildWise (free, open-source) CT server to run Selenium tests in minutes Sequential Build, run selected tests on the CT server machine Custom test executions with Rake ParallelBuild, distribute tests to build agents to run them in parallel CT best practices, such as Dynamic Ordering, Auto-Retry, Manual-Retry, ..., etc. Advice on setting up a parallel testing lab
Continuous Testing for DevOps Professionals is the definitive guide for DevOps teams and covers the best practices required to excel at Continuous Testing (CT) at each step of the DevOps pipeline. It was developed in collaboration with top industry experts from across the DevOps domain from leading companies such as CloudBees, Tricentis, Testim.io, Test.ai, Perfecto, and many more. The book is aimed at all DevOps practitioners, including software developers, testers, operations managers, and IT/business executives. It consists of 4 sections: 1. Fundamentals of Continuous Testing 2. Continuous Testing for Web Apps 3. Continuous Testing for Mobile Apps 4. Advancing Continuous Testing All profits from Continuous Testing for DevOps Professionals will be donated to code.org, which is a nonprofit dedicated to expanding access to computer science in schools and increasing participation by women and underrepresented minorities.
Using Continuous Delivery, you can bring software into production more rapidly, with greater reliability. A Practical Guide to Continuous Delivery is a 100% practical guide to building Continuous Delivery pipelines that automate rollouts, improve reproducibility, and dramatically reduce risk. Eberhard Wolff introduces a proven Continuous Delivery technology stack, including Docker, Chef, Vagrant, Jenkins, Graphite, the ELK stack, JBehave, and Gatling. He guides you through applying these technologies throughout build, continuous integration, load testing, acceptance testing, and monitoring. Wolff’s start-to-finish example projects offer the basis for your own experimentation, pilot programs, and full-fledged deployments. A Practical Guide to Continuous Delivery is for everyone who wants to introduce Continuous Delivery, with or without DevOps. For managers, it introduces core processes, requirements, benefits, and technical consequences. Developers, administrators, and architects will gain essential skills for implementing and managing pipelines, and for integrating Continuous Delivery smoothly into software architectures and IT organizations. Understand the problems that Continuous Delivery solves, and how it solves them Establish an infrastructure for maximum software automation Leverage virtualization and Platform as a Service (PAAS) cloud solutions Implement build automation and continuous integration with Gradle, Maven, and Jenkins Perform static code reviews with SonarQube and repositories to store build artifacts Establish automated GUI and textual acceptance testing with behavior-driven design Ensure appropriate performance via capacity testing Check new features and problems with exploratory testing Minimize risk throughout automated production software rollouts Gather and analyze metrics and logs with Elasticsearch, Logstash, Kibana (ELK), and Graphite Manage the introduction of Continuous Delivery into your enterprise Architect software to facilitate Continuous Delivery of new capabilities
Build and use systems that safely automate software delivery from testing through release with this jargon-busting guide to continuous delivery pipelines. In Grokking Continuous Delivery you will learn how to: Design effective CD pipelines for new and legacy projects Keep your software projects release-ready Maintain effective tests Scale CD across multiple applications Ensure pipelines give the right signals at the right time Use version control as the source of truth Safely automate deployments with metrics Describe CD in a way that makes sense to your colleagues Grokking Continuous Delivery teaches you the design and purpose of continuous delivery systems that you can use with any language or stack. You’ll learn directly from your mentor Christie Wilson, Google engineer and co-creator of the Tekton CI/CD framework. Using crystal-clear, well-illustrated examples, Christie lays out the practical nuts and bolts of continuous delivery for developers and pipeline designers. In each chapter, you’ll uncover the proper approaches to solve the real-world challenges of setting up a CD pipeline. With this book as your roadmap, you’ll have a clear plan for bringing CD to your team without the need for costly trial-and-error experimentation. About the technology Keep your codebase release-ready. A continuous delivery pipeline automates version control, testing, and deployment with minimal developer intervention. Master the tools and practices of continuous delivery, and you’ll be able to add features and push updates quickly and consistently. About the book Grokking Continuous Delivery is a friendly guide to setting up and working with a continuous delivery pipeline. Each chapter takes on a different scenario you’ll face when setting up a CD system, with real-world examples like automated scaling and testing legacy applications. Taking a tool-agnostic approach, author Christie Wilson guides you each step of the way with illustrations, crystal-clear explanations, and practical exercises to lock in what you’re learning. What's inside Design effective CD pipelines for new and legacy projects Ensure your pipelines give the right signals at the right times Version control as the source of truth Safely automate deployments About the reader For software engineers who want to add CD to their development process. About the author Christie Wilson is a software engineer at Google, where she co-created Tekton, a cloud-native CI/CD platform built on Kubernetes. Table of Contents PART 1 Introducing continuous delivery 1 Welcome to Grokking Continuous Delivery 2 A basic pipeline PART 2 Keeping software in a deliverable state at all times 3 Version control is the only way to roll 4 Use linting effectively 5 Dealing with noisy tests 6 Speeding up slow test suites 7 Give the right signals at the right times PART 3 Making delivery easy 8 Easy delivery starts with version control 9 Building securely and reliably 10 Deploying confidently PART 4 CD design 11 Starter packs: From zero to CD 12 Scripts are code, too 13 Pipeline design
Even with the most extreme automation, we simply don't have time for the "test everything" approach. It's impossible to test every possible path through a modern business application every time that we want to release. Fortunately, we don't need to. If we rethink our testing approach, we can get a thorough assessment of a release candidate's business risk with much less testing than most companies are doing today. Enterprise Continuous Testing: Transforming Testing for Agile and DevOps introduces a Continuous Testing strategy that helps enterprises accelerate and prioritize testing to meet the needs of fast-paced Agile and DevOps initiatives. Software testing has traditionally been the enemy of speed and innovation--a slow, costly process that delays releases while delivering questionable business value. This new strategy helps you test smarter, so testing provides rapid insight into what matters most to the business. Target AudienceThis book is written for senior quality managers and business executives who need to achieve the optimal balance between speed and quality when delivering the software that drives the modern business. It provides a roadmap for how to accelerate delivery with high confidence and low business risk.In summary: If you want to realign your Global 2000 organization's quality process with the unrelenting drive towards accelerated delivery speed and "Continuous Everything," then you're in the right place.
For any software developer who has spent days in “integration hell,” cobbling together myriad software components, Continuous Integration: Improving Software Quality and Reducing Risk illustrates how to transform integration from a necessary evil into an everyday part of the development process. The key, as the authors show, is to integrate regularly and often using continuous integration (CI) practices and techniques. The authors first examine the concept of CI and its practices from the ground up and then move on to explore other effective processes performed by CI systems, such as database integration, testing, inspection, deployment, and feedback. Through more than forty CI-related practices using application examples in different languages, readers learn that CI leads to more rapid software development, produces deployable software at every step in the development lifecycle, and reduces the time between defect introduction and detection, saving time and lowering costs. With successful implementation of CI, developers reduce risks and repetitive manual processes, and teams receive better project visibility. The book covers How to make integration a “non-event” on your software development projects How to reduce the amount of repetitive processes you perform when building your software Practices and techniques for using CI effectively with your teams Reducing the risks of late defect discovery, low-quality software, lack of visibility, and lack of deployable software Assessments of different CI servers and related tools on the market The book’s companion Web site, www.integratebutton.com, provides updates and code examples.
Winner of the 2011 Jolt Excellence Award! Getting software released to users is often a painful, risky, and time-consuming process. This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours— sometimes even minutes–no matter what the size of a project or the complexity of its code base. Jez Humble and David Farley begin by presenting the foundations of a rapid, reliable, low-risk delivery process. Next, they introduce the “deployment pipeline,” an automated process for managing all changes, from check-in to release. Finally, they discuss the “ecosystem” needed to support continuous delivery, from infrastructure, data and configuration management to governance. The authors introduce state-of-the-art techniques, including automated infrastructure management and data migration, and the use of virtualization. For each, they review key issues, identify best practices, and demonstrate how to mitigate risks. Coverage includes • Automating all facets of building, integrating, testing, and deploying software • Implementing deployment pipelines at team and organizational levels • Improving collaboration between developers, testers, and operations • Developing features incrementally on large and distributed teams • Implementing an effective configuration management strategy • Automating acceptance testing, from analysis to implementation • Testing capacity and other non-functional requirements • Implementing continuous deployment and zero-downtime releases • Managing infrastructure, data, components and dependencies • Navigating risk management, compliance, and auditing Whether you’re a developer, systems administrator, tester, or manager, this book will help your organization move from idea to release faster than ever—so you can deliver value to your business rapidly and reliably.
Best Practices for Implementing Continuous Integration with Hudson Optimize productivity while reducing risk and complexity by adopting a highly agile, "automate everything" software design philosophy. Hudson Continuous Integration in Practice shows you how to streamline and stabilize each process in your development lifecycle. Get expert tips for deploying a Hudson server, managing test and reporting frameworks, using source code management (SCM), and incorporating third-party CI tools. Distributed builds, plugin development, and system administration are also covered in this Oracle Press guide. Install, configure, and secure Hudson Automate build, integration, release, and deployment processes Set up jobs and add SCM from the Web-based GUI Administer QA tools, issue trackers, and build notifiers Incorporate IDEs, browsers, desktops, and mobile devices Publish Hudson build artifacts to Oracle Middleware utilities Work with plug-in manager and develop your own plugins Create custom dashboards and organize your jobs with views Develop a custom publisher, recorder, and notifier for your jobs
"If you haven't had the good fortune to be coached by a strong leader or product coach, this book can help fill that gap and set you on the path to success." - Marty Cagan How do you know that you are making a product or service that your customers want? How do you ensure that you are improving it over time? How do you guarantee that your team is creating value for your customers in a way that creates value for your business? In this book, you'll learn a structured and sustainable approach to continuous discovery that will help you answer each of these questions, giving you the confidence to act while also preparing you to be wrong. You'll learn to balance action with doubt so that you can get started without being blindsided by what you don't get right. If you want to discover products that customers love-that also deliver business results-this book is for you.
While few people deny the benefits of test automation, comprehensive automated testing via UI (browser for web applications) is rarely implemented in software projects. Common reasons for projects' failed attempts on test automation are: Difficult to learn - test scripts are complex and testing tools are not easy to use Hard to maintain - UI tests are vulnerable to application changes Long feedback loop - automated tests take too long to run To succeed in automated testing via UI, software projects need to overcome all these 3 chellenges. This book presents a practical approach to implementing test automation for web applications. Topics include: Developing easy to read and maintain Watir/Selenium tests using next-generation functional testing tool Page object model Functional Testing Refactorings Cross-browser testing against IE, Firefox and Chrome Setting up continuous testing server to manage execution of a large number of automated UI tests Requirement traceability matrix Strategies on team collaboration and test automation adoption in projects and organizations
