<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on Dhaval Shah</title><link>https://www.dhaval-shah.com/categories/testing/</link><description>Recent content in Testing on Dhaval Shah</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Fri, 02 Aug 2019 17:21:13 +0000</lastBuildDate><atom:link href="https://www.dhaval-shah.com/categories/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Chaos Engineering – Demonstration with working example (Part-2)</title><link>https://www.dhaval-shah.com/chaos-engineering-demonstration-with-working-example/</link><pubDate>Fri, 02 Aug 2019 17:21:13 +0000</pubDate><guid>https://www.dhaval-shah.com/chaos-engineering-demonstration-with-working-example/</guid><description>Background From first part of blog we gathered understanding about basics of Chaos Engineering. Now we will further deep dive to understand how to perform Chaos Engineering with a working example - which to me is going to be quite interesting. First lets start with understanding basics of working example which will be used to demonstrate following-
How to perform chaos engineering within an application How to monitor the behavior of the system What to monitor whilst executing experiments on our system Bird's eye view of demo example</description></item><item><title>Chaos Engineering – A quick primer</title><link>https://www.dhaval-shah.com/chaos-engineering-a-quick-primer/</link><pubDate>Sun, 30 Jun 2019 18:13:30 +0000</pubDate><guid>https://www.dhaval-shah.com/chaos-engineering-a-quick-primer/</guid><description>Human body is vulnerable to lot of diseases. So in order to protect human beings from diseases vaccines have been invented. Vaccines mainly work due to process called 'Hormesis', by which system or organism adapts to harm in order to become stronger. Just as our body is susceptible to diseases and germs, so do our systems in software world. Hence vaccines and vaccination can be considered as an apt analogy for understanding Chaos Engineering.</description></item><item><title>Agile India 2019 Conference – Learning Experience</title><link>https://www.dhaval-shah.com/agile-india-2019-conference-learning-experience/</link><pubDate>Sun, 14 Apr 2019 19:42:30 +0000</pubDate><guid>https://www.dhaval-shah.com/agile-india-2019-conference-learning-experience/</guid><description>Personally speaking, I am of the belief that only way to excel (professionally) is to collaborate and learn from experts. Since I am constantly striving to improve professionally as Software Craftsman, I try my best to exercise available options. One such option is attending some good Technology Conferences - as they are the platforms from where the so called experts of industry share their distilled experience to the larger community.</description></item><item><title>Bootiful Test Driven Development</title><link>https://www.dhaval-shah.com/bootiful-test-driven-development/</link><pubDate>Sun, 11 Mar 2018 14:28:47 +0000</pubDate><guid>https://www.dhaval-shah.com/bootiful-test-driven-development/</guid><description>Software engineers have been ardently following Test Driven Development (TDD) as an XP practice for having necessary safety nets. I have even tried covering different schools of TDD with an example in one of my previous posts. Considering recent surge in using Spring Boot for developing Microservice applications, I felt a need to understand and learn how to do TDD whilst implementing Spring Boot application.
In order to understand how Spring Boot simplifies the overall process of doing TDD, we will consider a very simple use case -</description></item><item><title>Microservices and Consumer Driven Contract testing using Pact</title><link>https://www.dhaval-shah.com/microservices-and-consumer-driven-contract-testing-using-pact/</link><pubDate>Mon, 10 Jul 2017 20:37:52 +0000</pubDate><guid>https://www.dhaval-shah.com/microservices-and-consumer-driven-contract-testing-using-pact/</guid><description>Background As per the current trends, Microservice Architecture has become a common paradigm using which enterprise applications are built. With this paradigm shift, an application is going to have myriad set of independent and autonomous (micro)services. So how does a developer do testing within Microservice Architecture? Answer is very obvious -
Create integration tests that invokes microservice under test which will internally call dependent microservices Get all the services under test up and running Start executing integration test which invokes microservice under test With this approach, the entire developer level integration testing will have following disadvantages -</description></item></channel></rss>