When to Start the Automation in Software Testing?

The Question of a Decade?

Today, when I draft this post, the calendar date is 14th February 2023.  If I look back to 10 years ago and ask myself what are the questions in and around Software Testing and Automation, I see this question.  What is that question?

When to start the automation?

We answer, hear, read, and discuss this question, today too!

Often, the opinion that comes out is, ".... to automate when it is stable".  Note that it is an opinion, not an answer or a fact accepted universally.

To Start Automation when it is "Stable"!?

My learning is,

Do not think of starting the automation when it is "stable".

The "stable" is an assumption we tend to believe by the outcome of using the system.  The binaries are never "stable".

The binaries appear to not show any risks and problems for the way one is using it in a context.  To be more precise, we are not seeing the risks and problems that binaries are showing us in other dimensions.  That is, the dimensions that we are not aware of or the dimensions that we are not focusing on.

When to Start the Automation?

I learn,

Start the automation, when the system is testable!

This leads to me the questions:

• What is testable?
• When it is testable?

Understanding testability helps me to learn and identify its child attribute -- automatability.  That is, understanding testability helps me to learn the order of "testable".

Testability does not mean "stable".  Testable does not mean "stable".

But the assumption "stable" means there are some characteristics of testability, automatability, and order of testable.

Automate when you learn, it is testable, and identify a layer of testability.  This helps to pick the better seam [that is the appropriate layer(s)] for automation in a given context.

Keep the automation structure ready, so that intent of a test can be expressed via code as we identify [a layer of] testability.

Maybe, this is what people say LEFT or SHIFT LEFT or START LEFT.  Or, could be out of the SHIFT LEFT BOX!

Inspiration and the Mentor Who Guided Me -- Part 3

 

Here is the first blog post of this series where I share how I started my Software Testing career.  I continue with the next question in this blog post.   The second question from Trending in Testing is -- "Who is your inspiration or mentor to guide you towards your journey?".

To start, I will thank my fellow testers and programmers with whom I worked and working today.  They influence my practice to get better each time.  I continue to learn from them.

People and Networking

I had just stepped into the second year of my Software Testing career.  One evening, I went to the desk of my friend and colleague Kantharaja MP.  He was reading the blog Thinking Tester by Shrinivas Kulkarni.  I got curious and asked what it is.  I did not know what the blog is then.  He explained to me what the blog is.  I got to know Shrinivas Kulkarni, James Bach, Pradeep Soundararajan, Ashok T, Rahul Verma, and Michael Bolton from the blog of Shrini.

Further, I got to know Vipul Kocher, Rahul Mirakur, Meeta Prakash, Ben Simo, Scott Barber, Gerald Marvin Weinberg, Martin Fowler, and Dr. Cem Kaner.  I connected with these practitioners and started to observe their practice.  Thanks, Kantharaja MP.

As I continued, I met Ajay Balamurugadas, Santhosh Tuppad, Parimala Hariprasad, and more friends who joined this network.

I'm continuing to connect with practitioners every day.  I interact, I observe.  I'm learning from each person with whom I interact.  I'm learning by observing the work of practitioners with whom I do not interact in person.

Mentor and Mentoring

I see, we must set out to find the mentor in our journey!  Find your mentors.  Yes, I said mentors and not a mentor.

My Mentor

I did not have a mentor.

I wish, I had a mentor who could connect, understand and help me to be competent, and know the craft, industry, and skills.  I continued to practice and learn from my mistakes, and by observing other practitioners.

I was seen as fun and the topic of fun for my attire, how I spoke and I write the English.  This made me distant from people whom I approached seeking help.  Today, I understand, could be this is the help I was offered for being better and I feel good about it.  I continue to respect them.  These people have inspired me to practice better.  I silently observed how they practiced and I experimented to develop my ways to practice.

I seek and step up to learn from all people when I see that, I can learn from a person or they can help me to learn.  This is doing good for me!

Today, I seek the help of people in the community by approaching them for their suggestions and guidance.  I give the credits and say their name in public and this is important.  I apply the suggestion, guidance, and what I learn from this appropriately based on the need and demand of context.

Ravisuriya as a Mentor

Today, 

• I want to be a mentor who understands the mentee and assists in the practice
• I want to connect with a mentee and listen

I understand,

• Each person is unique and comes with different
• emotions
• mindset
• attitude
• family situations
• personal life situations
• physical health conditions
• mental health conditions
• aspirations
• problems witnessed, and 
• connecting frequency levels
• and, it varies every day with a person

I try to connect, listen, learn, and assist where I can.  I'm a jovial person but at the same time, I'm committed and disciplined when it comes to practice and working.  I see the fun where we all enjoy and get involved in the learning, practice, and work.

Working with a Mentee

I do not associate and work with a mentee by seeing:

• her or his social identity
• how his or her English is
• how she or he appears in dressing
• how she or he socializes and opens up to conversing  

All these are needed in the professional life of a Software Engineer.  I do not deny it.  These have to be groomed every day.  Today, I want to and will dress better than I did in the early 2000s.  I speak!  I express what I have, feel and think, and communicate.

But, it is not a mandate to me for listening to a person (mentee) and get started unless I can't make enough time to assist.  These all will change gradually when one sees self and puts in efforts to get better.  And, a mentor has a role to play here as well.

If mocked for this, probably the mentee or whoever wants to be a mentee will build the distance and more barriers.  This will disturb the communication and relationship between the mentor and the mentee.  All have different conditions and environments in which we grew up and it has an influence on a person (mentee and mentor).

I look for how serious, disciplined, and committed is the mentee in progressing where she or he wants to aspire.  I see the communication is consistent in whatever form between the mentee and mentor.  By the way, communication is not English; the spoken language is one of the mediums through which we communicate.  And, English is one medium to communicate in the communication.

I try to see how can I assist and to what extent.  If I can, I will assist; if I do not have the skills to assist, I will try to connect them with other practitioners who can help better than me.  I talk and make sure we smile together in discussions.

I do not make fun of a person who asked for help and assistance.  I wish no others undergo what I went through.

Find your Mentors

Having a mentor helps very much! 

Find your mentors. Have more than one mentors who have

• the different thought processes,
• ideologies,
• thinking style and pattern,
• different experiences in the area of your practice,
• contrasting questions and approaching ways to learn and solve a problem,
• practitioners of different roles in your field of practice and work,
• practitioners who are not from your field of practice and work,
• and, now you continue to add more to this list ...

Most of the time one will fall into the trap of having a mentor who has got similar thought process and ideology.  This is good.  But, it is never enough to see the perceptions of your subject, work, and practice.

Connect to people of different ages and more importantly who have gone through what you are going through and also who have not gone through it.  

You and your mentor should be able to connect and offer what you both can exchange in return.  Mentorship is a relationship and a partnership where you share and receive.

I try to learn consistently that, the mentor does not have to be older in age and industry experience than I have.  A mentor is one who is able to give and share what I'm looking for in the journey and thereby helps to grow and transform me into a better version each time.

Find your mentors!  Connect to them.

How I Paved my Path into Software Testing! -- Part 2

 

I did not want to cut short sharing my experience for the below question.  I want to write what I want, to share about my journey to my first Software Testing job.  The question from Trending in Testing: -- "Could you please share your story about how you paved your path into Software Testing?"

College and Job Hunt

In 4^th semester, I decided to take Software Testing as my job.  I practiced Java 2 then, and using Core Java is one of my skills.  But, in college, we were said not to pick Software Testing as a career and job but instead to pick programming as a job.  The way I debugged my own code, it showed me that I’m doing better in testing each time.

On graduating B.E. in the year 2005, I walked to the public library to read the Times Ascent every Wednesday. I made a paper booklet that fitted my pocket and I wrote the email-id of companies who published (advertised) the openings and hiring for Software Engineers. All the openings advertised were for experienced software engineers.  I made note of all these email-id published in the Times of India's, Times Ascent. I hardly remember any call for freshers then on Times Ascent.  I did write a cold email to every advertisement for a Software Engineer job published in Times Ascent.

I walked to Software Companies in Bengaluru, asking for the email-id of the HR or email-id to share my fresher resume. I noted them in the booklet I had in my pocket. I gave the hard copy of my resume to the front office staff and asked them to share it with HR. Also, I mailed my resume later and asked for an interview opportunity saying how I will add value though I'm a fresher. I did not hear back!

Then, browsing at the internet centre was on the 52 KBPS modern telephone line and priced at 40 to 45 INR per hour. I had to mail around 30 to 45 individual emails in an hour with that choking internet. I had a credit account in the internet center as I extended 15 to 20 minutes each time, and it cost me 25 INR more. Today, do we have internet centers today in cities?  We do it all on a smartphone now most time.

Interview and My First Job

Those were the days that saw 6000+ freshers in a walk-in drive.  On one Wednesday, I saw an advertisement in Times Ascent from Datacard Software India Pvt. Ltd., looking for senior and lead engineers in Java. I wrote an email and shared my resume saying I'm a fresher and can use Java to program. I did not hear back from Datacard. 

After two months, I got a call from Radhika Muralidharan, the HR head of Datacard, India, asking if I was available for giving the interview. I said, YES!  

The first round was Java programming, and it had ten programs. I wrote the programs, all ten programs; I could see the confidence in me. I got a call after a week for the second round.  

In the second round, the interview panel had Srinivasan Rao the MD of Datacard Software India, and Vasu, the engineering manager. The questions were on Linked List and Double Linked List. I had the idea for these Data Structures; I wrote the programs for traversing the list and nodes.  But, I was not pleased with the logic, and I took 30+ minutes for two questions. The questions were about my logic, and I said, "it does not look good to me". 

This is the feedback I received in this round -- "You are good in Core Java; now you will have to work on Data Structures and optimize the same".   I acknowledged and accepted it.   But, I was confident in the way how I tested the logic I wrote for Linked List and Double Linked List and how I reasoned my logic is not a good one and why so.  I was said to leave as I did not meet the expectation.  I was not happy!  I practiced the data structures better.  I did not even know that data structures are a need and it is most expected in the interviews, then.

I continued my job hunt in walk-ins that saw 6000+ freshers. Three weeks later, I got a call from Radhika Muralidharan. She asked if I'm still looking out for a job, and if yes can I collect the offer letter at 4:30 PM. I said YES!

I was 30 minutes early for my interviews and on the day to collect the offer letter. Radhika spoke to me and asked to be seated in the meeting room. After 10 minutes, Srinivasan Rao came to the meeting room with an offer letter. He said, "What if I offer you the role of Testing?"

Ah! I needed a job. I wanted to be in Software Testing. I was offered a job in Software Testing. I said, "Sir, I will be happy, and I will do my best."  

He said, "Your skills are unique; you and we can benefit from your testing. Can you join on 6th July?".   I said, "I will start tomorrow." I still remember how Radhika and Srinivasan smiled at me when I said that.

I'm happy Software Testing choose me.  I'm happy that I got a job, and I got what I wanted as my job! I'm a Software Test Engineer by choice.  I'm glad, Software Testing is still holding me and uplifting me each day.  I'm a student of Software Testing & Engineering.

I Convey My Thanks and Gratitude

I thank Radhika for looking at my email and for the opportunity she gave me to give my interview. If she had not marked my email to call me for an interview, I don't know!  I thank Srinivasan Rao for the opportunity he gave me. I remember these two people, and they are in my thoughts. I'm grateful for the confidence they had in hiring me. Thank you, Radhika and Srini.  This job helped me to help my family.  I asked my mother to stop making agarbatti's and relax; she was doing it to support the family.  My first salary was 13000 INR.

I had four rupees in my pocket that evening. I looked for a coin telephone box on MG Road. I called my mother to tell her I got a job. up  I called my childhood friend Kantharaju to say I got a job; he picked me that day back home.  

I was on a project the next day with requirements, test cases, and design documents. The tasks were defined with timelines to deliver. Kalyan Kumar, the project manager gave me the book "Effective Methods for Software Testing" by William E Perry. He marked the chapters to complete reading in a week. That is the first book that I read to know and understand the approach and process in software testing.

I started my Software Testing career happily.  I m a Software Tester Engineer by choice.  I believe, Software Testing chose me and I'm grateful for it.  I'm a student of Software Testing and continuing my practice confidently amidst all the chaos that is surrounding Software Testing as a practice and career, today.  

And, this is how I started my Software Testing career.

Questions from Trending in Testing -- Part 1

 

This series of blog posts was supposed to be an article for a testing community.  I'm sharing it here on my blog as I could not finish it on time and respond to the moderator of the community.

On reading these questions, I wrote a draft for it.  I saw what I wrote could not fit into one post.  I tried to make it into one post.  But, doing so, I felt, I'm not doing justice to myself, to Treding in Testing for asking me to write, and to the reader who will be reading it.

As a writer or author of an article or blog, for first I have to enjoy my writing and its content, right?  I have to feel it.  Only then, the readers might feel what I write.  I did not get this feeling when I tried to fit it into one post.  Because, the questions were so contentful in itself. How to bring the value for those good questions?

I decided, I should be giving the credits to Trending in Testing and to make these each questions into a blog post, so that I do justice for the questions, to Trending in Testing, and to myself.

Search for Trending in Testing and read the interview of other practicing Software Test Engineers. Thank you, Trending in Testing for asking me these questions and any credits for this will be to you.

I was asked the below questions and I'm making each question as one blog post.

1. Could you please share your story about how you paved your path into Software Testing?
• Blog: How I Paved my Path into Software Testing! -- Part 2
2. Who is your inspiration or mentor to guide you towards your journey?
• Blog: Inspiration and the Mentor Who Guided Me -- Part 3
3. What are the common challenges that you face as a Software Tester? How do you overcome them?
• Blog: Common Challenges as a Software Tester; How I Overcome it -- Part 4
• Blog: Practice: The Top 5 Challenges I See For Today -- Part 4A
• Blog: Business: The Top 5 Challenges I See For Tdoay -- Part 4B
• Blog: Project: The Top 5 Challenges I See For Today -- Part 4C
4. What can people in the same role do to upskill themselves so that they can keep pace with the changing trends?
• Blog: To Be Contemporary in Software Testing & Engineering -- Part 5
5. According to you, what are the important factors to consider for becoming successful in Software Testing?
• Blog: What is Success to me in Software Testing? -- Part 6
6. What are the upcoming trends in Software Testing that our audience should know about?
• Blog: Difference between Software Testing and Upcoming Trends in Software Test Engineering -- Part 7
7. What advice would you like to give to aspiring testing enthusiasts regarding how they can pave their way in the industry and be successful?
• Blog: The Advice to Test Engineer in Me -- Part 8

HTTP Request Methods - DOT 3P HCG

 

Today, in the morning session with a mentee, she asked, "I have difficulty in remembering all the HTTP request methods and what it does. How can I make it simple?"  

I had the same question in the end of 2009 when I started testing the applications built using the HTTP.

Learning, and Registering the Learning

When I read, I forget it, because it is not yet registered in me consciously.  How to learn in a way so that it registers in me? I had this question.  Especially, when I started my career, I had this challenge.

In the college days, I had formed a tricks and hacks to remember and the mnemonic was one of them.  In 2008, I came across mnemonics in Software Testing.  I saw the mnemonic used by practitioners in Software Testing as one of the learning techniques and to register and retrieve the learning.

I repeat my learning in multiple approaches until I understand a concept. Then I form a layer where I make it simple for me to register it, in me, and to retrieve.

I applied the same with the HTTP request methods.  It became simple to me to recall and use it in my test designs when needed.

DOT 3P HCG

I helped myself by framing the mnemonic DOT 3P HCG in 2010.  I had difficulty in recalling the HGC part. For this, I said to myself -- head, chest, and gut.  That HCG became smooth in registering.  Finally, I could recall all the HTTP request methods with this mnemonic.

DOT 3P HCG stands for:

• D: DELETE
• to delete the resource specified
• O: OPTIONS
• describes the communication options for the targeted source
• T: TRACE
• used for diagnostic purpose and does a loop-back test along the path to target resource

• P: POST
• to submit an entity to specified resource
• P: PUT
• to upload/update an entity that is saved on server at a specified endpoint
• P: PATCH
• to do a partial modification to a resource

• H: HEAD
• Ask for a response which is identical to GET but without a response body
• For example, fetching the expiry date in a header as a response so that it can be used in the next request's header or a payload
• C: CONNECT
• To establish a tunnel with a endpoint or server for communication
• G: GET
• To request a representation (an information copy) of specified resource

As the HTTP request methods name are verbal, I can recall easily the purpose of each method.  I shared the same today with a mentee.  She could register it in a minute and recall these HTTP request methods and its purpose.

She is happy and says it is so simple now to recall the HTTP methods and its purpose.

Testability Revisited

 

I read the below question on The Test Chat's Telegram group.

When you start working on a project, what steps do you take to establish the testability of the product?

This question is helpful in learning how we see the Testability of a product.  It is a common perception to see the product with testability and then to test the product using the testability.

But, in reality, the testability is associated more with the tests; the tests which are used to test a product being developed or developed.

So, when we talk about testability, we need to be more aware of the test that we will be designing to test the software.  This test should be quick and easy to execute with the help of the programmed or available testability factors and their attributes.

You can find more blog posts in and around testability here in Testing Garage.  Testability in software engineering and systems is one of my research areas.

Testability

I understand Testability as

• How easy it is easy to test by an engineer
• In a given context and skills of an engineer
• With the being used test approach and strategy

Note: The context can keep including factors as we add more and continue to test

It is not about if one can test the software or not.  It is all about software that is easily tested.  How easy?  That is one of the testability factors in software design and programming.

Test and Testability

Unless I know the test, I will not be certain about the Testability.  Testability does not drive tests.  It aids the execution of the test and it is a heuristic.  If the test is designed well to the context and if the testability is used well in the test's context, the execution of a test can be quick and easy.

The tests

• make use of available Testability
• helps to strengthen the Testability
• add more Testability in different seams/layers of the engineering and product

From here it will be two ways; the tests and testability will complement each other.  Further, it leads to developing and including more specific and deterministic tests and testability types in respective seam/layers.

Testability and Automatability

Testability can be classified further into several categories.  Based on the purpose and what to evaluate we will have to identify Testability in respective categories and need to use it.

As a software engineer one is bound to think testability with software programming and infrastructure.  But, testability in software engineering is not just bound to software programming.

The testability is diverse and available across engineering activities.  It is used in all engineering activities.  Maybe, for a software engineer who is hands-on with programming and testing, they infer Testability most times with programming and infrastructure.

I see, the Testability always exists to an extent.  But, can it be identified and used in the way I approach, design, execute and evaluate my test?  That is the point to explore.

If it is testable to some extent, then we are using some Testability attribute(s).

If there is Testability in a seam/layer, then there is an Automatbility in that seam/layer to an extent.

If it is automatable then there is some attribute of Testability in that seam/layer.  Again, the question comes to knowing and learning -- What am I testing and automating? Why? How? When? Where?

This discovers seams/layers to test and automate.  It leads to identifying the tests.  Then, to identify and build more Testability and Automatability.

A written program feature essentially will have an automatable characteristic and space.  If it is automatable, then it is making use of and extending the testability.

In summary,

• Know the test to know and identify the Testability better
• Know the Testability to automate better
• Know the Automatability to assist your testing better.

Context-Free Questions to Identify Testability

To know and have better Testability, here are a few things that I will want to know:

1. What is the test?
• What am I testing and what am I supposed to test?
• How is this test designed to learn and evaluate the system?
• What are the data, states, and events that I'm experimenting, exploring, and experiencing as I test this system with help of this test?
• How can I make this testing quick and easy?
• What should I use to make my testing quick and easy with this test?
• How should I use it to make my testing quick and easy with this test?
• When and where should I use it to make my testing quick and easy with this test?
2. Why am I testing this?
3. What happens if I test this and do not test this?
4. What is the value loss I will incur if not tested?
5. What is the value loss I will incur if I do not understand and learn the outcome of the test?
6. What changes the dimensions of my tests?
7. How can I learn the product better from this test?
8. What information am I learning from this test?
9. What information, heuristics, and Oracle help me and stakeholders to analyze and decide better?
10. Do I actually know the product from the perspectives of
• tech
• business
• user
• risks
• problems
• protocols
• guidelines
• environment
• money
• benefits
• exploitations
• team developing it
• and, more that I can add to the context of the product and project

To summarize, know the test and know how the test is designed.  It helps to identify better testability at the right layer/seam of the software system and engineering.  If there is no effective testability at that seam/layer, it helps to build one.  That way, the automatability also gets built in that seam/layer if the team collaborates well.

Technically, What is a Bug?

 

I'm mentoring the Software Test Engineers.  In one of the pair sessions with a mentee, we were discussing the technical aspects of one technology.  We started to test the application and a mentee said, she found a bug.

She explained the bug.  Further, she asked how, can I explain this bug technically.  And, going ahead, she asked, "Can you technically tell what a bug is?"  

Technically, What is a Bug?

I have come across various definitions of a bug from other software testing practitioners.  If I have to tell technically what a bug is, I put it this way:

• A bug, is a logical incident experienced
• It is logical because the programming instructions written are logical
• Technically, the bug is a logical incident

 

My Work, My Fit, and Company's Goals

 

I, My Role and Expectations

At least once a day, it is useful to think about oneself.  I started doing this late in my life and career. I started doing it in recent years.  If I do not think about myself, I will be lost very soon.  This is not selfishness; it is self-care, which is what I'm learning.

It is essential for me to think about myself, because:

• It helps me to see what I'm
• It helps me to see where I moved today
• Does this move help me personally?
• Does this move help me professionally?
• What benefits does it bring me?
• What benefits does it bring to those with whom I associate and work together?
• Does it keep me in sound mental and physical health?
• Did I learn today?
• Something new?
• Anything I refined and unlearned?
• Does it bring any costs and cons to me?
• Am I fit?
• Fit to where?
• Fit to what?
• Fit? How?
• Fit? Why?
• Fit? When

In all the roles I take in my personal and professional life, I'm evaluated at some point in time.  I will be judged for:

• Did I fit?
• Did I do my role
• Did I meet the expectation?

The problem is not that I'm evaluated.

The problem is I'm evaluated without saying what makes me fit to be in the association and how I will have to meet the expectation.  Some associations can remove us while some cannot.

When I say this, I want to say this -- the word family is often misunderstood; not all associations can be a family although the word family is used often in associations.  This is reality and not a fact!

Does family eliminate me if I do not fit in?  I don't know!  At least the hope is, family is where I can be myself; without the thought of me being judged and evaluated for what I take and bring to the family.  My family as well have expectations from me in the different roles I live in with them.

When I can see this in my family, why don't I see this in the place where I work together with other people?

Do I fit in here for what I make out of this place (company) and take it to my family, home, and my life?

I wish my home and school had helped me learn this question early in my life!  I expect it now because I realize the "value of fit", now, that is, after I graduated and started to work with people in the organizations.

I consistently learn that every one of us is replaceable in any association, be it family or a workplace.  And, it moves on; it does not stop.  If not replaceable, it is manageable to continue and move on.

When we are in the association, how fit we are so that it is hard to replace?  Maybe that's a price (value) tag and a necessity of one!

The Response, That I Should Evaluate

As a responsible colleague and team member, I promote the discussion of this question at least once a month.  I ask this question to whom I report at work.

I will have this question in every one-on-one catch-up that I will have with my reporting manager.  And, I expect a response to this question and want it recorded for future reference.

What is that question?

How does my work fit in with the company's goals?

Evaluating the response:

• How do I evaluate the response to this question?
• What should I do on the evaluation of the response?
• Why should I evaluate the response?
• What should be my next course of action?
• After all, what is my response to this question and how do I evaluate it?

To get promoted to the next roles,

• I need to be solving the problem of my higher (or next) role
• I need to have the capability (skills) to solve problems of my higher role

But this is not a question of promotion.  It is the question of being fit for the company's goals.

While I get promoted or to be promoted, my work may still not fit with the company's goals.  Identifying this early helps.

I have learned, sometimes the promotion does not necessarily come with the fit for the company's goals.  But then eventually the fit will be evaluated at one stage by someone in the company together with a promotion given.

This has led me to ask this question consistently and then evaluate the response with the business, political and rational mindsets.

I say the same to my team, that is, ask this question for yourself and to the reporting manager.  Evaluate the response that comes to you.

Should you ask this question to your reporting manager in each month's one-on-one catch-up?

The Fit Equation Changes

In the team and company, we believe:

• We are contributing
• We are a value-adding fit type
  

We keep saying to ourselves how we make a great fit and difference.  Isn't it?

This "fit equation" keeps changing every day or quarter or year or appraisal cycle.  I learn, this "fit equation" keeps changing rather than evolving.

Adapting to this consistent change and delivering is evolving.  This is my understanding for today.

Biases, Communication, and Problem Solving

We all are in biased mindsets and perceptions at any point in time.  The people in the company need help to break these mindsets so that one's fit equation is questioned and assessed regularly.  In my opinion, this is a great assistance that a manager and a leader can give to her/his people.

I expect the managers and leaders to ask the company:

• What the company wants from the people?

We people in the company and in the team, let us ask the manager and leaders:

• What the company expects from me?
• What is my fit equation?
• Does the current work that I'm delivering fits the company's goals?

I have heard most times from people saying, "I was said that I did not fit with the company's goal".

How will one know what is the company's goals and how can one align with them unless it is communicated and recorded professionally?  I see, to start it needs communication, clarity, and affirmation first from both ends.

Does this solve the problem?  No!  It gives an onset to understand the problem and the differences to fix.  With this, the manager and leader can help the team, and vice versa, in solving the problem.  Thereby contributing to the company's goals by aligning with them.

If you are a manager or a leader, make sure you have this as an essential practice in monthly catch-up to assess this fit equation and let know your people.  I love seeing this initiative from managers and leaders.

This is one of the leader's fitness to be in the role to assist people and the company.  By doing so, we will help the company, business, employees, investors, and customers.

To reset this post's intent equation:

• How the work expected from me fit in with the company's goals?
• How does the work I'm doing fit in with the company's goals?

I'm Open to Mentoring the Software Test Engineers

 

Hello!

I hope you are doing well.  With this blog post, I want to let you know that I'm open to mentoring Software Test Engineers from this November 2022.  I will have a minimal fee for the mentoring that I do.  If the fee is bothering you, do not worry!  You move forward for The First Catch Up.

The First Catch Up

Before we start the mentoring sessions, I would like to listen to you until I and you get an insight that we have listened enough.  From the discussion and listening, it will be evident to us whether can we pair up in the mentoring session or not for the time being.  If I see that you need mentoring from another orientation, I will connect you to the appropriate mentor.

This is to assist you better and to let me know how I can assist you.  For the first catch up, we can connect on a call.  Please use below QR Code to connect on Telegram.  If you are not on Telegram, I'm just one email away. Here is my email -- ravisuriya1 at gmail dot com.

My Telegram ID to Connect for The First Catch Up

I and Mentoring

I have been a hands-on Software Test Engineer for 15 years now and continuing my practice.  In my practice, I have put myself into different contexts and demands of software development and engineering.  Working with a two-member organization, start-ups, and enterprise organizations, I understand the dynamics of engineering and can adapt to it.  

In doing so, I  have tested and continuing my testing with the monolith, microservices, and distributed systems.  Put me in any domain and seam (layer) here, I can test and automate here by learning what is needed.  I can share this learning and practice of me with you.

Do you expect motivation from me?  I'm motivated and I will share what is motivating me.  To keep my motivation up and consistent, I'm disciplined.  I look to commitment in your discipline to be motivated to take both of us forward.  It is our job and not just of you or me.

This keeps me up and high and not the minimal fee that I take from you.

And, do not stick on to one mentor. Find your mentors with contrasting thoughts and practices.  It helps a lot.

How and the New Beginning, Not the End

Anything has to be time-bound and with milestones to accomplish.  When I'm mentoring with defined and evaluated milestones, we will be along with the time.  Though mentoring does not come to end, the picked activities have to see a new beginning and challenges, rather than continuing the same discussions and practice.

If we are not seeing this, then we have something not going right for our goal.  We will be evaluating it consistently week-on-week.

It is not about seeing the results.  It is about understanding where we are in seeing ourselves in where we have to be.  It is a journey. The result that we experience is just one minute part of this exploring journey

In simple, we will be outside of our comfort zone!  I said, ours comfort zones!

The Fee

As I mentioned, you will have to pay a minimal fee monthly basis only if you choose me to mentor you and we both work together in this activity.  It is a minimal fee that I will tell you on connecting.  There is no fee for The First Catch Up.

Why the wait?  Let us catch up and listen to each other.