Book Image

DevOps with Windows Server 2016

Book Image

DevOps with Windows Server 2016

Overview of this book

Delivering applications swiftly is one of the major challenges faced in fast-paced business environments. Windows Server 2016 DevOps is the solution to these challenges as it helps organizations to respond faster in order to handle the competitive pressures by replacing error-prone manual tasks using automation. This book is a practical description and implementation of DevOps principles and practices using the features provided by Windows Server 2016 and VSTS vNext. It jumps straight into explaining the relevant tools and technologies needed to implement DevOps principles and practices. It implements all major DevOps practices and principles and takes readers through it from envisioning a project up to operations and further. It uses the latest and upcoming concepts and technologies from Microsoft and open source such as Docker, Windows Container, Nano Server, DSC, Pester, and VSTS vNext. By the end of this book, you will be well aware of the DevOps principles and practices and will have implemented all these principles practically for a sample application using the latest technologies on the Microsoft platform. You will be ready to start implementing DevOps within your project/engagement.
Table of Contents (20 chapters)
DevOps with Windows Server 2016
Credits
About the Author
Acknowledgments
About the Reviewer
Acknowledgments
www.PacktPub.com
Customer Feedback
Preface

Environment unit tests


After provisioning the resources, it is important to test them. Tests should be executed on these resources to verify that they are provisioned successfully, configured according to given values, and are in the expected desired state.

Chapter 5, Building a Sample Application, introduced the OnlinePharmacy.Configuration project within the overall sample solution. This project contains the Tests folder containing both unit and operational validation tests.

Pester was introduced in Chapter 3, DevOps Automation Primer. It is used to execute the test cases defined in this section. The UnitTests folder contains all the Pester tests. The test cases are defined in PowerShell script files, one for each resource that should be tested.

These tests can be executed manually by executing the scripts directly using a PowerShell console. It can also be executed using the VSTS release pipelines. The preferred mechanism to execute these tests is through the VSTS release pipeline. After...