Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learn PowerShell Core 6.0

You're reading from  Learn PowerShell Core 6.0

Product type Book
Published in Jul 2018
Publisher Packt
ISBN-13 9781788838986
Pages 552 pages
Edition 1st Edition
Languages
Authors (2):
David das Neves David das Neves
Profile icon David das Neves
Jan-Hendrik Peters Jan-Hendrik Peters
Profile icon Jan-Hendrik Peters
View More author details
Toc

Table of Contents (26) Chapters close

Title Page
Dedication
Packt Upsell
Contributors
Preface
1. Current PowerShell Versions 2. PowerShell ISE Versus VSCode 3. Basic Coding Techniques 4. Advanced Coding Techniques 5. Writing Reusable Code 6. Working with Data 7. Understanding PowerShell Security 8. Just Enough Administration 9. DevOps with PowerShell 10. Creating Your Own PowerShell Repository 11. VSCode and PowerShell Release Pipelines 12. PowerShell Desired State Configuration 13. Working with Windows 14. Working with Azure 15. Connecting to Microsoft Online Services 16. Working with SCCM and SQL Server 17. PowerShell Deep Dives 1. PowerShell ISE Hotkeys 2. Assessments 3. Other Books You May Enjoy Index

Test-driven development


Test-driven development plays a very important role in DevOps. The Wikipedia definition (https://en.wikipedia.org/wiki/Test-driven_development) of test-driven development is this:

"A software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases, then the software is improved to pass the new tests, only."

By knowing your requirements so well that you can write test cases that accurately reflect those requirements, you automatically write fitting code. This is usually done by developing solid test cases first that test the so-called happy path. All code is then developed so that the test cases pass.

The benefit of this approach is that no unnecessary code is produced, since the code only needs to satisfy the requirements. TDD also leads to modularization of the code. This is something we do in PowerShell anyway and that should by now sound familiar; functions and cmdlets should only have...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}