CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury! Testing (automation) is one of the important practices that needs to be setup correctly for CD to be successful. But, this is tricky and requires a lot of discipline, rigor and hard work by all the team members involved the product delivery. The Test Automation Pyramid is a great concept that helps teams focus on the "right" type of automation.

To add to the never-ending challenges, a new architecture style has evolved - Microservices Architecture. While there is no precise definition to explain Microservices style, it essentially talks about how to break a monolith application into smaller, independent pieces - usually based on business capability, automated deployment, and various other factors.

In teams building a complex product using the Microservice Architecture approach, the Testing approach also needs to evolve to be effective and validate the functionality quickly, and effectively.

But why does the Testing approach needs to be different for Microservice Architecture?
Here is an example: If your product architecture is something similar as seen here, or here, to make testing effective, and enable fast feedback, you need to break down the testing approach from an end-product (monolith black-box) into smaller components - in this case - at individual service, combination of services, etc. level.

In this workshop, learn, via a game-based activity, correlated with a case study of an Enterprise (, a large Bank), the Testing approach required to take them on the journey to achieving CD in the Microservice world. We will also learn how to break down the test automation pyramid at a Microservice level into smaller test automation pyramids - i.e. Micro-Pyramids to enable early feedback about quality of the product.

1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

Here is the structure of the session:

  • Play a game (2 small iterations) to demonstrate and discuss the learnings
  • Introduction of Microservices Architecture
  • Describe the case-study of an Enterprise on the path to implement CD using a Microservice Architecture


  • Walk-through the Test Strategy for this Enterprise
  • Different types of testing required (Starting from Unit, and all the way up to UI, NFRs, etc.)
  • Importance of selecting the right tools and technology for Testing
  • How does Manual / Exploratory testing fit in this?

Learning Outcome

  • Understanding of Microservice Architecture
  • Create a Test Strategy for complex domains / Enterprises on a journey to implement CD in Microservice landscape
  • Key takeaways to ensure the Test Strategy will help achieve CD!
    • Walk-through the Test Strategy for this Enterprise
    • Different types of testing required (Starting from Unit, and all the way up to UI, NFRs, etc.)
    • Importance of selecting the right tools and technology for Testing
    • How does Manual / Exploratory testing fit in this?

Target Audience

Managers, Leads, Architects, Hand-on team members (devs / qas / product owners)

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Tony Xavier

    Challenges and Best Practices: Creating Customer Focused Documentation in an Agile Framework

    Tony Xavier
    Tony Xavier
    schedule 1 year ago
    Sold Out!
    45 mins

    Agile is an increasingly popular development method primarily used by software companies. In Agile software development, work is confined to a regular, repeatable work cycle, known as Sprint. A sprint typically lasts for two to three weeks. In Agile, development teams strive to deliver a fully functioning, high quality, and potentially shippable product increment at the end of each sprint. Hence, product documentation becomes an essential part of the sprint deliverable to meet stakeholder requirement. Since, the primary focus of Agile development is to deliver products with high quality, technical communicators are expected to create customer focused documentation with high quality.

    Creating Customer focused documents involves paying great attention to needs and opinions of customers, and creating documents with a purpose. As writers we must ensure that the documents we create focus on the needs of the actual customers of the document and provides value. As writers we must identify who the potential customer(s) for our documentation are, what they require, and create minimal documentation that they actually need. By understanding the needs of our customers we will be able to deliver customer focused documentation with high quality. However, the combination of Agile’s high speed of development, short delivery cycles, and limited requirements documentation presents a unique set of challenges in creating customer-focused documentation.

    This paper highlights some of the challenges writers face and provides best practices that can be used in creating customer-focused documentation in an Agile framework.