Devops Book Review: Team Topologies

 Here are my insights from reading the team topologies book: *         I never knew that organizational structures mirrored communication paths! Interesting revelation!! This is based on Conway’s law. For example our QE team was reporting to a Head of Quality who in turn reported to Head of TPM. Then we had a reorg and now the QE team was moved under Head of Infra. Applying Conway’s law, Infrastructure team is more of a enabling team and that is similar to what QEs do - they enable developers to produce better quality products! Have you ever wondered why teams go through rounds of reorgs? Reorgs within companies happen to improve team interaction modes and the 3 main interaction modes are: *          Collaboration *         X-as-a service *         Facilitating QEs are either embedded within feature teams or centralized in some companies.  These are not necessarily related to company culture alone but due to the following 4 fundamental topologies: *          Stream aligned team : Teams

Testing Tour #6: Accessibility Testing with Viv Richards!

  This year has definitely been a rollercoaster ride and I wanted to have small victories to signify that I have been resilient during  times of distress. One of those was to wrap up my testing tour which I had happily kickstarted in the beginning of the year!  Huge thanks to Viv, for agreeing to be on my testing tour and ending the year on a high note! Cheers! :) Viv and I took the role of driver and navigator interchangeably, which led to a wonderful pairing and learning session. We discussed  and played around with the chrome lens plugin and MAC OSX inbuilt voiceover capability.  Chrome lens plugin Viv explained to me about the power of chrome lens plugin - ChromeLens is a set of developer tools that allow developers to code  websites better suited for the visually impaired. The three tools that are currently available are: Filters to experience a website as a blind or colorblind person. Scanners to audit the accessibility readiness of a website.  Trackers to visually show the path

Testing Tour #5: Exploring the observability world with Abby Bangser!

  Abby was such a pleasure to work with! We originally planned to discuss about observability but when we started our session,  as I was already familiar with the tools (as we use it at work), Abby quickly shifted gears and asked how she could help me.  The challenge I was facing then was to extract the test failure count from jenkins test results and project it on a dashboard    in Grafana. Being new to Grafana and wavefront query language, I shared my objective with Abby. I learnt that the Wavefront Query Language  lets you retrieve and display the data that has been ingested into Wavefront. Time series data The query language is particularly well suited to time series data, because it accommodates the  periodicity, potential irregularity, and streaming nature of that data type. Histograms The query language includes functions for manipulating histograms. Traces and spans Use the tracing UI to query traces and spans. So, what is a query?  In order to understand that, we examined t

Testing Tour #4: Writing a book with Lisa Crispin

Lisa Crispin is popularly known as the co-author of her book on Agile Testing.  In this short session, we explored what motivated Lisa to write her book and her pointers for upcoming  writers!  Problem/Objective/Motive:  Lisa mentioned that when she was working as a tester, she had a lot of questions about implementing  agile methodologies within her team but there was no single book that could answer all of the questions!  Hence the book provides solutions to those questions.  Well, with time, not many folks had the time to flip through 550 pages of the Agile Testing manifesto,  hence she focused on condensing it to a 100 page version.  How to generate ideas Lisa gave good pointers around using a mind map to jot down about the topics anyone wants to write  about. The mind map will give you a visual idea of what/where the content goes into. Mindmeister is a  software tool that helps you draw mind maps in the digital world.  She also shared her experience

Testing Tour #3: Exploring API testing with Maaret Pyhäjärvi

I had a 60 min session with Maaret where we initially discussed my goal for this session - which was  to explore any open source API and write unit tests. Given Maaret comes with extensive experience,  she suggested to start simple using the Gilded Rose Kata for our session.  She already had the project setup on her laptop, so when we paired via zoom, we were able to  switch control to write tests on her IDE. The first 20-25 mins, we spent trying to understand the  requirements outlined here .  Introduction : Gilded Rose is an inn in a prominent city where they buy and sell goods.  Our task is to test this system based on the rules laid out.These were the basic ground rules: All items have a SellIn value which denotes the number of days we have to sell the item All items have a Quality value denoting how valuable it is At the end of each day, our system lowers both values for each item There were more rules concerning each type of item - which is where it gets inter

Testing Tour #2: Pairing with Lisa Crispin: Contributing to Gherkin open source documentation

PR Link : Duration : 60 mins My second session with Lisa Crispin turned out to be a strong style pairing session as each of us  assumed the driver/navigator role. Lisa was already working on adding better documentation on explaining declarative vs imperative style  of Gherkin. Am a complete noob with regard to Cucumber/Gherkin and Lisa was briefly explained  the what/how behind it. Her PR was already in progress and she needed help navigating via IntelliJ  and git commands which I was familiar with. Based on my understanding: Cucumber is a testing tool that supports behavior driven development.  BDD is a way for software teams to close the gap between business and technical people. It defines  application behavior using simple English text defined by a language called Gherkin .  Cucumber was initially implemented in Ruby and then extended to Java framework and it supports  JUnit as well. All the stakeholders: developers,