My Experience With HOTS For Smart QA

In this year [2025] apart from attending the meetups, I joined two programs. One is HyBIST and the other is HOTS.  These two programs helped me to pause and rethink on certain topics, my practices and approaching. 

• HyBIST -- Hypothesis-Based Immersive Session Testing
• HOTS for Smart QA -- Higher Order Thinking Skills

In this blog post, I'm sharing my experience with HOTS.  

I start by expressing my gratitude to Thiruvengadam Ashok and Keshava Murthy.  The efforts and time these two are investing to consistently update and build the HOTS has to be recognized and appreciated.

I was part of HOTS 5.  It is the fifth edition of this program with 30 topics.  We had around 40 hours of discussions.  This edition had 18 sessions.

Pic: On the last day of HOTS 5 Cohort Session

HOTS, Engineering and Thinking

In my opinion, HOTS is not just confined to software test engineers though the program title is HOTS for Smart QA.

• It is to anyone in the discipline of Software Engineering.  
• A software test engineer will have an edge as one can find at least one more test engineer in HOTS.

HOTS is a program where one is put to varying thinking orders and dimensions from different perspectives. 

• The topics and discussion in HOTS starts from the why the need of a software to what it takes to consistently deliver value from deployed software.

In a way, it is a kind of rewriting one's own experience and lessons learned from others experience.  

• On rewriting it, how will one go ahead to engineer the solution in her or his work -- is a gist of HOTS outcome.  

When one gets this gist, one will realize, the software engineering is not just coupled to programming, testing, DevOps and business.  

• Instead, it is social engineering which involves the awareness and skills of different disciplines.  
• I learn, it takes years of practice to become aware of this.
• By being part of the HOTS discussion, it opens up one to this awareness in the early days of one's career.

Programming, testing, product engineering, orchestration and business's service delivery is not just technology and code.  It is a  social engineering which demands skills beyond programming and testing is echoed implicitly after each cohort sessions.  

Hosts and HOTS

Ashok and Keshav are giving their time for HOTS outside of their work-life and family life.

• It is not easy, to do this, as a routine for the scheduled program as HOTS.  
• These two cannot bunk a class in HOTS.  
• Hope you get the picture of how committed this program is!

The hosts are punctual to the classes.  

• Keshav shares the information and any updates on time in the messaging group, so that, the attendees are aware of the topics and can prepare for it.  
• Ashok ensures to remind the attendees about the upcoming class on the previous day of the class.  

Apart from this, these two take care of administrative tasks to run the classes smoothly.  

• I did not have any trouble or problem during the online classes and in accessing the resources of HOTS.

The hosts are available and will respond in the messaging group for the queries posted.  

• I have seen, the hosts picking up the questions which were posted in the messaging group and discussing it in the class.  
• The hosts do not ignore; they make sure we get the clarity and interpretations with perspectives on the questions.

I have seen the attendees gently not agreeing to certain perspective in the discussions.  

• And, the hosts welcome it and appreciate it.  
• I did not see anyone being judged or labeled in the HOTS.  
• All are treated and considered equal.  
• We are given the opportunities to share, and we are asked to pick the opportunity to share our thoughts.  
• So well and effectively the HOTS classes are moderated and regulated by the two hosts.

On top of this, the experiences of Ashok and Keshav in the industry, engineering, software testing and engineering, and life bring vivid richness to the HOTS.

My Hands-On Experience of HOTS

• I was not aware of the word 'cohort'.  I got to know it from the HOTS.
• Each session is a cohort; I have no second thought in it.
• The attendees in HOTS come from different
• Organizations, roles, backgrounds, understandings, practices, thought process, problem-solving approaches, perspectives, experiences and awareness.
• I prepared for each cohort sessions.
• I read, analyzed and interpreted the topics and its details.
• I made my points and noted the questions to share.
• This gave me a space to interpret each peers thoughts and their points.
• I had my take back from each peers irrespective of their experiences and roles.
• I had take backs from each sessions. 
• I don't remember a session where I sat idle.  
• I was engaged completely in each sessions.
• Each sessions have put me into reflection, retrospective, regression, relaxing, critical and lateral analysis modes.
• I did not bunk any cohort sessions.  I made sure, I attended each sessions.
• When I was late by 15 minutes to a couple of sessions, I made sure to know what was discussed.
• It is that fresh each sessions are and the perspectives from it!
• There is no right or wrong in any thing shared -- this was told by hosts to all of us.
• It is how we are placed in the context makes it close or not close to what looks the solution or acceptable reasoning.
• We peers correlated and connected the different perspectives and learned from it.
• The disagreeing to anyone's thought happens professionally and it will be acknowledged.
• I observed, the disagreeing or agreeing was to the thought and not to a person. This is important to notice here!
• Each attendees welcomed the perspectives and awareness of other peers in the cohort.
• When I worked on the nudges and reflection questions,
• It helped me to recall my works.
• That way, it helped me to eliminate what I had to and start with a different mindset for today's needs.
• I could go deep into each of these exercises and think critically, or, figure out what I can do differently to solve the same problem.
• I also made use of HOTS 5 to exercise and improvise my communication skills.
• It helped me a lot here!
• These below fundamental skills of all disciplines were exercised in each sessions.
• Questioning, Interpreting, Hypothesis, Reasoning, Logical Analysis, Pattern Recognition, Communication and Presentation.
• Every area of Software Engineering was touched and discussed.
• For example, 
• How critical is the time analysis and drawing the analogy of Big O notations in software engineering.
• There is no randomness thought it has the word Random
• There is a definite defined and accepted boundaries in the said random.
• An example of Random Forest algorithm and how it works.
• And more such topics
• The hosts did not rush to complete the topics of the week.
• Instead, the hosts ensured, there was a value oriented discussion on each topic.
• At times, the cohort discussed just one topic for 2 hours.
• It was not an easy emotion for me on the last day of HOTS 5.
• I miss the Tuesday discussions which started sharp at 8:30 PM IST.
• My key take back from the HOTS 5 are,
• The perspectives each peer shared in how they attempted to understand the problem before solving it.
• The representation of tests in the layers to ease the communication.

I thank with gratitude to Ashok, Keshav and all other peers of HOTS 5.  Your time, presence and interpretation has helped me a lot!  I'm building upon it.

References:

1. https://smartqa.community/
2. https://smartqa.community/hots/
3. https://www.linkedin.com/in/ashokstag
4. https://linkedin.com/in/keshava-murthy-k-n-a623034

Workshop Experience: Effective Problem Solving for Leaders and Managers

 

This writing is about my experience attending the workshop Problem Solving for Leaders and Managers by Ajay Balamurugadas, which was organized by Manu Mantra in HSR Layout, Bengaluru. I thank Ajay for the help and coordination he gave me to attend the workshop.

Disclaimer

I'm not asked and paid by anyone to write the experience report for this workshop. I'm writing it to document -- my learning, reflection, and refraction I have in me on attending the workshop.

About the workshop

I know Gerald M. Weinberg and his team did the Problem Solving Leadership (PSL) workshop. I came to know about this workshop from fellow testers in the community and posts of Gerald M. Weinberg. Ajay had been to the USA for the PSL workshop.

I could not attend the first batch of Ajay's workshop. I requested Ajay to update me for the next workshop; he did update me. He helped me further to be part of the workshop.  

Attending the workshop, I learn, Ajay has got it to his style and context, and it is unique.  It was one day workshop

Ajay posted details of the workshop. Now, I had an opportunity to learn what it has and what I can make out of it.  

Why did I attend this workshop?

Here is why I wanted to attend this workshop:

1. Learn from one who is applying what he has learned from the PSL workshop
2. Learn the approaches he has in solving the problems
3. Learn how one arrives at decision making
4. How the trainer uses skill and benefits from it as a manager/leader?

What I made out of this workshop?

I wanted to listen and avoid talking unnecessarily. I was attentive in the workshop and observed what the trainer and fellow trainees shared. The workshop started with a problem in the training room. The whiteboard was not usable; using the projector was not going to serve, and the trainer had to come up with a way to start the workshop.

Ajay solved it! As a result, what the trainer wrote or shared was available as notes. My wife follows a similar approach when there is no whiteboard. The workshop started with a question -- "What is a problem?"

I share a few of my learning here:

1. Problem Identification - CLOSE mnemonic
2. Solutions to a problem
3. Problem perspective, solving, and traps
4. Team, situations, understanding people
5. Models and tools to assist

My experience and learning

I like the way how Ajay handles himself in recent days. The how and why of it is evident to me now after attending his workshop. This workshop helped me to restructure my problem-solving models and approaches wherever needed.

There were new aspects that I did not know. I could pick and learn them from this workshop. I got what I was looking for from this workshop.

If you have never come across any session or mentor to assist in solving the problems, this workshop can be the first step.

Workshop Experience: Web Application Security Testing

 

This writing is my experience report of the workshop Web Application Security Testing conducted by Verity Software with Rahul Verma as a trainer. I had attended this workshop in November 2011. I registered for it again and was part of the workshop for the second time in September 2020. I thank Vinay Baid and Anil Nahata of Verity Software for coordinating and helping me to attend this workshop.

I and Web Testing for Security

I started testing for web applications in 2008 by learning what the browser is, its internals, and by understanding the web technologies. While doing this, I was working on projects which built web systems for -- SalesForce, Healthcare - Insurance, Reporting, and BI Reporting systems.  

One of the projects was supporting only for IE (IE6 & 7). The other projects web was supposed to support desktop Firefox, Chrome, and Safari. In the project, my task was to test for functionality.

In parallel, I picked testing for the security of these web applications. I referred to OWASP and its contents. I was building my mindset for security testing; I tested for web application security. I found the security bugs!

Disclaimer

I'm not paid by anyone to write this post and no one asked me to write one. I'm writing it has my workshop experience and learning I made out of it. I'm writing it to document my experience from this workshop.

About the workshop

I saw the post in 2011 from Rahul Verma about his workshop -- Web Application Security Testing, two days workshop. I registered for it in 2011; it helped me. In 2020 September, I did attend the same two days workshop from Rahul Verma and conducted by Verity Software this time. The detail of this hands-on workshop is available in the Verity Software's website.

  

I did not feel it is a repetition. In these eight years, my thought process has changed. I see that I have progressed in my learning in these eight years. Yet, I did not experience it as a repetition. 

The only differences that I could see are:

• In 2011, it was in a hotel at Kormangala; 2020's workshop was online as an effect of the COVID19 pandemic.
• In the physical workshop, the trainer moved around each table and looked into the trainee's practicing; in an online format, he helped by asking how we are doing the hands-on exercises.
• In the physical workshop then, the trainer had given a laptop if needed with software that needs to be used and installed; in an online format, we trainees had our laptop and seated at home, and accessed the practice system hosted on a cloud via remote desktop.
• In the physical workshop, he could see us, our eyes and our face, and understand what's happening with us; in an online format, he had turned on his camera, and trainees had turned off their camera.
• In the physical workshop, there was networking between the trainees; in an online format, no networking, and sharing between the trainees.
• In the physical workshop, he wrote on whiteboard and in a projected text editor and explained; in an online format, he used the Sublime editor to write and explained his thoughts on the shared screen.
• In the physical workshop, there was silence, we trainees listened to him; in an online format, at times we had trainees microphone turned on and could hear the background sound (I don't call it as noise!).
• In the physical, we did not see any break or lag in the trainer's voice; in an online format, we could see the lag in the trainer's and trainee's video and voice (latency, bandwidth, streaming & internet!).

Otherwise, I made my notes as I listened to him then and today. It was the first online workshop for the trainer Rahul Verma.

Why did I attend this workshop?

Here are my reasons why I attended this workshop:

• To check on my fundamentals, thought process, and mindset in Web Application Security Testing.
• To see the difference in me and my practice after I attended the previous workshop.
• To learn certain concepts better from a practitioner who practices web application security testing.
• To listen to Rahul Verma:
• He doesn't do sugar coat.
• Says what he knows and what he practices.
• His way of explanations and the way he looks at the fundamentals before security.
• His experiences and what kind of security information he finds and how.
• I did not connect to it well in 2011 as I connected to it today.  I was grasping slowly and thinking about what I do as Rahul Verma spoke.  I did not repeat this mistake in the 2020's workshop.
• Today, I received it better as I'm practicing it, and I could relate my work when he discussed subjects and topics in the workshop.

What I made out of this workshop?

I said to myself to unlearn and not to think with what I know as I listened to the trainer. I went with an open and listening mind to this workshop. I did make sure to keep myself attentive in the workshop. I share a few of my learning here:

• My fundamentals got revisited; registered it better in my thought and mind.
• Understanding and the way I see what I see is with more clarity and observations.
• The topics which look buzzy and complicated have become much simpler now to understand and work on it.
• My mindset is realigning with the unlearning I had in the workshop.
• I wanted to re-arrange my thinking here if I had to, and I did it listening to Rahul Verma for the second time.
• Before learning security testing, the fundamentals of the web were taken seriously and discussed it.
• I cannot write in detail about it here. Probably if I do that, it may impact the trainer and organization conducting the workshop.
• The fundamentals he discusses here are needed -- stepping stones.
• As we know, tools assist in testing better, but it does not test on behalf of a tester. Yet using the tool in security testing is helpful in context up to a limit, and later it is human who has to test for security. 
• I did not see anything I listened to as a repeat for me.

I got what I wanted from this workshop. It is on me now how I practice and lead myself ahead.

My experience and learning

What the trainer spoke is available in books and on the web. What's not available is the thought process and how to approach it by understanding. The demonstration of a practitioner has to be experienced in person if possible; it brings a different and unique value in the trainee. My peace is paced well and tuned. 

The value added by the security testing of a Test Engineer/SDET and Security Testing specialist is unique and needed. My idea of encouraging and assisting the Test Engineer/SDET to practice Security Testing is much strong and clear now. I will continue to practice Security Testing as a Test Engineer/SDET, and sure I will add my unique values early in the work I do.

I have got the confidence now that if I attend it another time, I won't experience it as repeated to me.  It will be new and unique.

If you can afford and attend this workshop from Rahul Verma, do attend.  It will help to build the fundamentals and mindset needed for the Security Testing and Web Application Security Testing.

Workshop Experience: Certified Selenium Engineer

 

This writing is my experience report of workshop Certified Selenium Engineer conducted by Verity Software and Rahul Verma as a trainer.  I could not attend the scheduled workshop, once.  Vinay Baid from Verify Software allowed me to attend the workshop on another date.  I thank him and Verity Software for the help.  In this, conversation, Anil Nahata helped me by coordination and I thank him as well.

Disclaimer

I have not been paid or asked to write this blog post.  I have decided to share my experience and take away from the workshop which I have attended.  I'm doing it, to have my learning experience recorded in brief.  As well, it can help the trainer in a way that her/his workshop will reach more people.

About the workshop

This workshop is on Selenium having the title "Certified Selenium Engineer".  More information about the workshop can be found on the website of Verity Software.  Per my experience, the Verity team is approachable and they coordinate learning the context of workshop attendee.

It was a three days workshop and it was conducted in a hotel at Koramangala, Bengaluru.  Following the workshop, there was a mock test and then a certification test on the third day.  The questions needed thinking to solve and to analyze and choose an answer  Not all questions were straight.

I did not feel the paper as tough.  It engaged me well and made me think.  On understanding the fundamentals well and with the practice that one does in the workshop, the test paper can be easily attempted.

Why did I attend the workshop?

Here are my reasons why I attended this workshop

• Rahul Verma
• I see Rahul Verma as a serious and thoughtful practitioner in the Software Testing space
• Listening to what he has to share in the workshop
• I know he will not just talk in and around Selenium topics that were mentioned in the workshop details
• What can I unlearn and learn listening to him?
• There will more and beyond Selenium, in using Selenium better for sure
• I needed this; I wanted to listen to this; I wanted to see how he thinks and interprets
• I said myself do not be biased with words and thoughts of Rahul Verma
• Think about what he says
• Interpret on what he says
• Understand what he says
• Think what you (Ravisuriya) think
• I see whatever he spoke in the workshop, it makes very senseful

What I made out of this workshop?

I got what I wanted from the workshop.  I made sure, I make most of it and I was attentive to it.  I share a few of them here:

• I said myself come with an open mind; forget whatever you know for a while; unlearn and look from a fresh mind
• I did not open my mouth to talk except for asking questions; I had kept my mind open and attentive
• I did not like missing any word spoken in the tutorial be it from trainer and attendees
• Rahul Verma shared beyond Selenium's basics
• Rahul Verma spoke about Programming in fact and how to use programming for making the best out of a Selenium library
• Starting with
• What is the web?
• How the web works?
• What the web page is?
• What is DOM, HTML, CSS?
• What is an element, tag, attribute, and value in the HTML?
• What constitutes the browser?
• What is Selenium?
• The architecture of Selenium and JSON Wire Protocol
• Design Patterns and Design Pattern used in Selenium library
• What is said in the syllabus were covered with examples
• Not just examples of automation using Selenium
• But also with an example of what to do and not do - this is a treasure!
• This is what I want to listen from the practitioner's experience
• Framework and Test Authoring
• If I did write everything in detail and how the topics were discussed, it might look like an exaggeration; but it is no exaggeration
• It has to be experienced at least once from the practitioner's training

My experience and learning

Whatever Rahul Verma spoke it is available in books and web content that talks about Selenium.  The difference is

• Concepts were said in simple terms
• Examples shared for the topic spoken were from his work experience
• Programming - do's and don'ts with each example and concepts
• Keeping it simple, workable, and learnable
• If want to be strong in the fundamentals of Selenium, this workshop helps

For the kind of my mindset of learning style and expectation, this workshop from the trainer gave me satisfaction.  I'm happy!