Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Building Microservices with .NET Core

You're reading from   Building Microservices with .NET Core Develop skills in Reactive Microservices, database scaling, Azure Microservices, and more

Arrow left icon
Product type Paperback
Published in Jun 2017
Publisher Packt
ISBN-13 9781785887833
Length 274 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (4):
Arrow left icon
Soumya Mukherjee Soumya Mukherjee
Author Profile Icon Soumya Mukherjee
Soumya Mukherjee
Gaurav Aroraa Gaurav Aroraa
Author Profile Icon Gaurav Aroraa
Gaurav Aroraa
Lalit Kale Lalit Kale
Author Profile Icon Lalit Kale
Lalit Kale
Manish Kanwar Manish Kanwar
Author Profile Icon Manish Kanwar
Manish Kanwar
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. What Are Microservices? 2. Building Microservices FREE CHAPTER 3. Integration Techniques 4. Testing Strategies 5. Deployment 6. Security 7. Monitoring 8. Scaling 9. Reactive Microservices 10. Creating a Complete Microservice Solution

Testing strategies (testing approach)

As mentioned in the prerequisites section of Chapter 1, What are Microservices?, deployment and QA requirements would become more demanding. The only way to effectively handle this scenario would be through preemptive planning. I have always favored the representation of the QA team during the early requirement gathering and design phase. In the case of microservices, it becomes a necessity to have a close collaboration between the architecture group and the QA group. Not only would the QA group input be helpful, but the QA group would be able to draw up a strategy to test the microservices effectively.

Test strategies are nothing but a map or outlined plan that describes the complete approach of testing.

Different systems require different testing approaches. It is not possible to implement a pure testing approach to a system that is developed using a newer approach rather...

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 $19.99/month. Cancel anytime
Banner background image