Augmented Testing: 26th ATA Bengaluru Meetup at Fiserv

This blog post is about the software testing meetup which resumed after 5 years.  It is ATA's 26th Bengaluru Meetup held on 28th February 2026.  

The last meetup [25th ATA Bengaluru Meetup] was on 29th February 2020.  Do you see the date and gap?  That was pre-COVID days meetup.

It is a good feel to experience the restart and resuming!  This is living the hope.  

I tell you what it takes to run one meetup; read here.  Now, imagine running the meetups month on month as a ritual.  Do you feel it?

26th ATA Bengaluru Meetup, 28th Feb 2026 at Fiserv office in Bengaluru

26th ATA Bengaluru Meetup

In excitement I registered for this edition of ATA meetup.  I read the agenda, venue and date.  I started to feel it.  

The meetup was scheduled to start at 3 PM IST -- unusual and it helped me to travel and be on time from my distant place.  I reached by 2:24 PM IST.

1.  Meetup Updates

• Team ATA gave regular update on the meetup with all details.
• I did not have any confusion.

2.  Venue and Hospitality

• Fiserv office in Bengaluru.
• The security and admin staff of Fiserv were highly cordial and professional.
• I did not face any problem with check-in and checkout.
• The admin staff helped us with information.
• Ankur Raj, Balaji Kanamanapalli Venkata and Moulya Charegowda of Fiserv hosted and spoke to each of us.
• The seating and accessories for workshop was well arranged and organized.
• We got high snacks to beat the stomach hunger along with space to network.
• Thanks, Fiserv!  You imprinted a cherishing memory in me.
• I will attend the meetups you host.

3.  Meetup's Panel Discussion and Workshop

• 26th Meetup's theme
• Augmented Testing: How AI Is Changing Quality?
• Panel Discussion
• Discussion on the questions from community.
• Panel members
• Ajay Balamurugadas, Balaji Kanamanapalli Venkata, and Deepthi K
• Moderated by Aditya Garg
• We meetup attendees were encouraged to share our thoughts during the panel  discussion.
• This made it lively and active participation.
• Such experiences and initiation can happen only in the meetups.
• The panel is of opinion
• AI is of help and way forward.
• AI is effective when we input the effective data.
• What to consider when evaluating the AI solutions and how it is not same as we evaluate any tool or language.
• Have human in place and use the AI to the best possible level in a context.
• AI speeds the execution.
• The efficacy of outcome is dependent on input.
• How to see and use the AI solutions.
• AI, jobs and impact.
• Test Engineer now as a orchestrator of AI solutions and testing.
• Ethical AI and practice.
• Guardrails around AI.
• Hands-on Workshop
• We were given laptops by Fiserv for this workshop.
• Ankur and Moulya led the workshop.
• The workshop was around how to write better and effective prompts to LLMs.
• Copilot was prompted with hands-on exercise.
• Explained how to use the heuristics AUTOMAT and CO-STAR to build the prompt.
• This workshop was useful to me.
• I saw a couple of attendees prompting for the first time.
• It helped them!
• The purpose of workshop is served.
• Moulya and Ankur gave me space to share my thoughts to the attendees during the hands-on workshop.
• I thank them for this.
• They were in good spirit and encouraged me to share.
• I conveyed this to them and expressed my gratitude.

4.  My Experience

• Wow!
• I'm happy, I was in 26th ATA meetup.
• I'm glad to experience the Fiserv's people, hospitality and spirit.
• I shared insights on,
• SLMs and its help in specific to a context in contrast to LLMs.
• Why it is not easy to stop using the AI going forward?
• Why the compliances around AI is a challenge?
• The factor of 'interest' along with cost vs value.
• Cost vs Value vs Interest
• Interest drives further though the cost is high and value is not experienced.
• In case of AI, the interest is driving irrespective of the value and cost for now.
• This is my experience, observation and learning for today.
• How we end up writing the prompts and miss what we actually want to test?
• Why it is important to know how the system is orchestrated, communicates and functions along with domain knowledge?
• I shared an example and walked through the incidents.
• I cannot end this section without thanking Moulya and Ankur for giving me the space to express and share my thoughts.
• Moulya you are a team and person with whom I wish to work.
• I feel how considerate you are in listening and facilitating the best to come for all us in meetup.  Thanks!
• Balaji you are a team and person with whom I wish to work.
• I could see how open you were to know and listened asking my bits and experiences.  Thanks!
• I met Manoj MV of PostQode after a decade.  Wow!  I conveyed, how thankful I'm to him.
• I met Aditya Garg in person.
• I wanted to discuss with him on few topics; it did not happen this time.
• I met Ajay.
• Though we did not converse, we knew we are in touch and could feel it.
• I had a long discussion with Sushmitha and Vimala.
• I had a discussion with Ram from Capgemini on performance testing models.
• Had a quick chat with Jwala and recalled our last meetup.
• A brief talk with Arjun, Balaji and  Penchaliaha.
• I had a good networking and connecting.
  

How Fiserv is integrating AI solutions with testing and engineering -- the impact and changes.  My request to ATA and Fiserv is to host one more edition and share their exploration and solving.

I cannot end without the mention of security staff of Fiserv.  The lady was smiling, professional and helped us through check-in and checkout with information.  Fiserv, please do convey our greetings and message to her.

The other staffs who helped us in the meetup area and cafeteria were smiling.  That smile and warm welcome gesture tell a lot about the office floor.  

I'm looking forward for the 27th ATA Bengaluru Meetup.

Thank you, ATA.  Thank you, Fiserv.  Thank you, community.

Volunteering Meetups: An Experience and a Recurring Ritual

 

I attend meetups consistently.  I observe, conferences give information; meetups give the transformation.  

I have discovered that the informal and interactive format of meetup helps me express myself, connect deeply with others, and build a stronger network than in conferences.

As someone who organizes and volunteers at meetup in Bengaluru, I have seen firsthand what it takes to make them thrive and succeed.  In this post, I will share a glimpse of behind the scenes and why these gatherings matter so much to our tech community.

What is a Meetup?

A meetup is an informal community-driven gathering where people with shared common interests come together to share, learn, collaborate, network and grow.  Unlike conferences, the meetups emphasize on openness and active participation.  

Usually the meetups are a regular happening -- often month after month and it is recurring.  The community drives, foster and sustains it with its energy.

Conversations here are not one way lecturing; they are dynamic exchanges where everyone's voice is valued.

Most meetups do not charge and are free to attend.  Yet, the meetup delivers amazing hospitality and hosting.

Once you attend a meetup which helps you to be aware and contemporary, you will start searching for more meetups in the community.  That's how the meetups function, work and hold you together in your growth journey.

Ravi as a Meetup Volunteer

As a meetup volunteer, I see myself less as a moderator and more as a community curator.  My role is not about control; it is about creating space.

I work on facilitation -- assisting so that knowledge, ideas and experience flow from community back into the community.  The people are already enabled; what they need is a platform, a spark, a rhythm and that's where I work.

I try my best for the communities of software testing and software engineering.

Meetup Volunteer's Priorities

Here are the first few priorities I work on.

1. Have I created an atmosphere and space where people can connect and collaborate with ease?
• How do I foster comfort, conversation, and the confidence to share?
• The real challenge is "tagging" connections -- quickly introducing individuals to help them find common ground.
• Initial facilitation creates a ripple effect -- once people are connected, they will network independently in future meetups.
2. How to surface the available knowledge within the community?
• My goal is not to find the speakers.
• If I did so, I will make the meetup a mini conferences; it fails the purpose of the meetups.
• Identifying the "Quiet Experts"
• I collaborate to know who can surface the knowledge and share.
• It is all about collaborating with members to assist them surface and share their unique insights.
• I work to build time and structure for the community to share the knowledge it already possesses.
3. It is okay when we do not have an answer. We will solve it in the upcoming meetups.
• As a volunteer, I do not work to give answers.
• Instead, we community work to solve problems.
• Sometimes, we do not get solution for questions in a meetup.
• But, we follow it up, get an approach and potential solutions in the upcoming meetups.
• This is not see in the conferences.
4. What if all registered people do not turn up to a meetup?
• In a meetup we do not take attendance.
• Instead, we work on connecting, networking, collaborating and sharing.
• Say 10 out of 40 people turned up the meetup.  
• The goal is how we 10 can deeply connect and partner to help self and the community.
• I facilitate here much deeper and stronger on purpose.
• This is an asset we build.
• In the meetup, number of people is not success; the connection we make is!
5. How should I function so that this meetup will recur?
• I will be planning for the next meetup sessions in the ongoing meetup.
• It is a ritual that recurs month on month.
• If I run meetup as a conference, people will feel disconnected.
• People do not enjoy the powerfulness of informality and knowledge packed meetup.
• I work on how to remember the names of people.  I talk to them by calling their names in next meetup.
• People feel connected and associated when I do so.
6. Leaving the meetup venue clean and organized.
• As a volunteer, it is me who will be last to leave the meetup.
• People would have spilled the coffee, tea and eateries.
• I pick it and move to trash bin.
• Erasing the white boards, moving the chairs, pens, duster, cables, turning off the lights and moving the cups to wash basin.
• I do this, if this is not done by the people.
• Look for any items which people have left in the venue.
• Collect it and hand over to them.
• Why I do this?
• It is a mark of respect and my duty to leave the venue clean and organized.
• That way, the venue sponsor will be happy to give us the space next month with hospitality.

Volunteer and Payment

I am not paid for doing all this by the community which organized the meetup.  Neither it is observed, recognized and appreciated.  But, the security and home staff of the venue got much closer to me to work as a team in running the meetup.  

Most times the meetup organizing community do not think of the efforts I put and travel to run a meetup.  Yet, I do it for the software testing community and my happiness!

Delivering a Meetup

As a volunteer, I'm more of a community curator than moderator and organizer.  

I facilitate [not enable] the sharing of knowledge, thoughts and work from the community to the community.

Running the meetup is a collaboration and team work together with the community.  This team work will have multiple challenges to solve. Some of the challenges mention are,

• Passion and commitment
• Funds
• Venue sponsor
• Surfacing the speakers to share the knowledge
• And, speakers who finally makes on the day
• The topics and how it is relevant for the today's need and audience
• Meetup campaign execution
• Attendees
• The audience reach
• Reaching the meetup's information to the right audience
• Registration
• Maintaining the data sanity
• Keeping the audience excited
• Pre-meetup engagement
• Getting the audience to the meetup on the day
• Engagement of the venue sponsor, speakers and audience during pre-meetup, in the meetup and post meetup
• Venue management
• Meeting the venue's administration expectation
• Arrangements and facilities
• Hospitality
• Leaving the venue clean and sane
• Agenda of the meetup
• Keeping it balanced so that it serves audience interest and time with a take back to their desk and apply it
• Volunteers available on the day to host and facilitate the meetup
• Travel of people to the meetup
• Promotions do happen in meetup
• Who is being promoted, why, how and when?
• This has to be evaluated by the volunteers and meetup organizers
• Too much of it, it leaves behind not a good impression in the audience
• Why?
• Meetup should not be a place for promotion by large and solely
• It is a happening where people of common shared interest gather and collaborate informally to learn, share and grow
• Finding the balance here is critical
• The volunteers have a role to play to keep the meetup organizer see the interest of community and not just the business branding 
• And, more as you add to it.

To end here,  I do not get why this phrase is used in announcements -- "last but not the least".

The meetup organizer and volunteers are not last and the least.  They are part of the meetup in each phase.  Without the commitment and passion of the volunteers and meetup organizers, the meetup is not ready to deliver.  

Yeah, finding that volunteer who is super charged and passionate is like spotting a wishing star!

In gist, this is how the meetups are delivered by a passionate and committed volunteers from the community.

My Learning from Agile Testing Alliance's 12th Bengaluru Meetup

I attended Agile Testing Alliance's 12th Bengaluru Meetup hosted at Moolya Software Testing Pvt. Ltd., office on 25th March 2017. I got to know about this meetup from the Facebook share by Moolya and made my mind to be there. The audience in the meetup were software testers, Agile trainer or coach, and technical lead.

Below listed presentation came in time between 9:40 am IST to 12:50 pm IST

• Welcome and introduction to Agile Testing Alliance, by Nishi Grover Garg
• Challenges of Agile for a Manger, by Preeth Pandalay, Techno Agilist, Agile Coach & Trainer
• Behavior Driven Development: What, Why & How - from a tester's perspective, by Vinay Krishna, Agile Technology Coach
• Problem Solving Techniques: An attempt to apply ideas across disciplines, by Ajay Balamurugadas, Tyto Software
• Creating 100 mindmaps in 1 minute, a demo by, Dharamalingam K, Moolya Software Testing Pvt. Ltd
• Concluding the meetup and vote of thanks, by Nishi Grover Garag

Brief lines on presentations from my notes

I'm listing few points here out of my notes. It was engaging sessions and I had to make sure that I will listen, I make notes and tweet to people if any who were curious to know what's happening in the meetup.

Nishi Grover Garg : Introduction to ATA and welcome note

• She introduced herself and shared about the Agile Testing Alliance and what it does
• Said about the recent testing conference that was held i.e. GTR Pune 2017
• Shared about the different certifications and the assistance from ATA

Preeth Pandalay : Challenges of Agile for a Manager

• Started with management structure, management hierarchy and bureaucracy
• Spoke about management in 21st century and in technology era
• Shared his views on traditional structure of management and Agile management structure
• From there, he spoke about traditional manager and Agile manager
• Mentioned about the network based management and said it as organization structure 2.0
• Then he said about Agile Team Cross Functional and mentioned Katrina Clokie's blog which speaks about this
• With that he said, Agile team is self organized
• He shared statistics of Agile helping to solve and deliver better
• With the statistics walk through, he says, Agile works
• Audience had question around -- "Management yet to getting adapted to Agile and teams are on Agile. How to solve this so team gets much more support?"

Vinay Krishna : BDD -- What, Why, How - a tester's perspective

• Started by asking do you know what is BDD and then said it is another buzz word and jargon
• Says, "in this era we all are programmers and need to write code; testing is a specialization now."
• He said about the surprises that software development brings and highlighted on "assumptions" what people make in team
• Started a group activity saying to draw start having 12 points and later he asked "why you did not ask questions but assumed?"
• Says, bug + feature = beature
• misunderstanding at all levels
• lack of effective communication
• difficulty in communication
• lots of assumptions
• Then he shared, BDD = shared understanding by discussing examples
• Continuing his talk, he said, for start have at least three amigos -- Business Analyst, Programmer and Tester
• Also says, it is useful if identified and used more than three amigos
• Shared about how important a scenario and use of Gherkins
• Mentioned on BDD framework saying,
• Feature File
• Step defintion (glue code) 
• Actual implementation
• Started another group activity and asked to identify the scenarios for a ATM transaction
• He said to avoid UI tests with BDD
• Shared few myths around BDD
• BDD is automation of functional testing
• Using Cucumber is BDD
• BDD is replacement of functional testing
• Took questions from audience around
• Difference between unit testing and BDD
• Around usefulness on BDD
• Deriving the benefits of BDD in performance and security testing
• Limitations of BDD

Ajay Balamurugadas : Problem Solving Techniques: An attempt to apply ideas across disciplines

• Starts by asking, "How do you solve problem? Take a minute and let me know."
• Audience started interacting
• There were no slide and it was a white board and interactive session througout
• Then he mentioned about a crisp definition for "what is problem?" of Jerry Weinberg
• difference between expectation and reality
• He mentioned about Problem Solving Leadership workshop by Jerry Weinberg
• He says, "focus on things which can be controlled"
• From here, he asked the audience to pick any one problem, so that he demonstrates how to solve it
• The audience picked -- why less number of attendees to the meetup
• He started to brainstorm around this problem while audience interactively shared their thoughts on how to solve it
• Nishi Grover Garg, said this is useful and it will be used from the next upcoming meetup
• Moving from here, he said about four techniques which can be used in solving the problem
1. Attributes and Improvement
• by, Robert P Crawford
• Further with examples he said
• identify the problem and list out the attributes of the problem
• work on the improvement of the problem
• If you miss out an imporant attribute, problem might not be solved
2. Six Thinking Hats
• by, Edwared de Bono
• Mentioned about 6 different thinking hats -- White, Black, Yellow, Green, Blue and Red
• Briefed what each hats means and what they signify
• He recommended to avoid using Black hat immediately after the use of Green hat
3. Questioning
• He said the importance of questioning
• Mentioned about Osborn Questioning
4. SCAMPER
• A mnemonic
• S - substitute
• C - combine
• A - adapt
• M - magnify
• P - put
• E - eliminate
• R - rearrange, reverse
• Later he shared one more mnemonic which he made while on the way to meetup
• PROBLEM
• P - perception
• R - reasoning
• O - opportunity
• B - beware of assumptions & problems caused by solving the problems
• L - lawfulness
• E - exploratory
• M - management
• He took the questions from audience on the techniques and applying it

Dharamalingam K : Creating 100 mindmaps in 1 minute, a demo

• Walked through swiftly on what is Mindmap and where it can be used
• He shared about the problem what he and his team encountered when wanting to build a mindmap for a product's feature
• Then, he said how he built the mindmap via Python program
• He ran a quick demo which showed creation of mindmaps
• He took the questions from audience
• On mindmap
• On the complexity and how to do this via programming

Nishi Grover Garg : Concluding the meetup and vote of thanks

• She thanked the audience who made for the meetup
• Said about the Agile Testing Alliance and benefits the people can get from ceritification

I took below to my desk from this meetup

• How to handle myself in teams which claims to run on Agile
• How to coordinate and deliver my best in the environment which claims to run on Agile
• How to focus on my work irrespective of Agile or not Agile and assist fellow testers and stakeholders
• Thoughts and questions around BDD apart from functional testing
• A mind which says to explore on this
• To focus on things which is in my control and where I can deliver
• Do not take responsibility without having the authority
• I repeated this to myself again
• To read and build skills from below resources shared by Ajay
• Attributes and Improve, by Robert P Crawford
• Game Storming, by Dave Gray, Sunni Brown, James Macanufo
• To explore and use what I can to learn in the web -- http://humansystemsinaction.com

Post meetup hours, was part of three interactive discussing sessions with Ajay and Pranav. I did learn discussing to Ajay and Pranav on fundamental topics of software testing, programming and practice.


Here is a pic from the meetup

Attendees of Agile Testing Alliance's 12th Bengaluru Meetup hosted at Moolya