The Unsaid Difference Between the Terms UAT and EUT

 

I read this in Telegram chat of The Test Chat:

I am listening to a very interesting conversation about testing. The bone of contention is - UAT (User Acceptance Testing) is same/or not to End User Testing. What do you think?

 

My Opinion as a Blog Post

I learn, writing this opinion of me as a blog post is of use and value adding to the community.  So I write this mini blog post.

The discussion around this topic do exist since I started my career.  Maybe, it will continue as well.  And, that is not a problem.

The concern I see is, how these terms are being interpreted in the discussion. And, this discussion will continue for years to come.

I attempt to share my thoughts on how I look at these terms -- UAT and EUT.

Introspecting the Terms UAT and EUT

Here is how would I start to understand these terms and learn.  I use the approach "Replace and Interpret".  When I experienced difficulty and ambiguity in practice of subject and concept, this approach crossed my mind.  Today, I use it consistently in my Software Test Engineering practice.

For example, I see the below few on replacing the word "testing".

• User Acceptance Automation
• End User Automation
• User Acceptance Driving
• End User Driving
• User Acceptance Singing
• End User Singing
• User Acceptance Programming
  
• End User Programming
• User Acceptance Vehicle
  
• End User Vehicle
• User Acceptance Utensils
• End User Utensils

I can keep identifying such replacements. I try to learn by replacing the words, idea, thoughts, or what is seen as fit to replace.  Doing so, I see the differences in what it means in different contexts.  Isn't so?

Prior to understanding and learning these words, I learn and understand the thoughts of people who are using these words and the differences they see.  The learning of this difference helps me much than the difference of the two terms -- UAT and EUT.

I see, the discussion on this topic and words has not changed much since 15 years.

Today, in the time of 10 days sprint (or two weeks sprint), do someone have an opportunity with time to carry these -- UAT or/and EUT?  Which product/system get the space for the UAT or/and EUT?

We have to learn these terms (UAT & EUT) from that system/product's perspective rather learning as generalization in Software Engineering and Software Test Engineering.

Do not start and establish the discussion and understanding of these terms by associating it to Software Testing right away; and, then call it out as a [generic] activity of Software Test Engineering. 

Introspect these words from the perspective and context of the product/system you are testing.  Look out for its necessity and purpose of being executed.  If you see these two are different activities for a system/product's context, it has a purpose for being different activities in that context.

This is my thought and opinion on these terms for now.

To stop here, I see the "Testing" is common to both [of these words].

Maven For Software Test Engineers - 101

 

Why 101s?

In the initial days of my career, I looked and referred to multiple sources to understand the technology stack.  As I progressed, I looked for someone who can help me in understanding what I'm reading and to clarify the questions I witnessed.  The understanding of concepts took time when I actually started using it and especially when debugging.

Today, if I look at that, I ask myself

• How can I make my learning experience a happy one?
• How can I capture the fundamentals and have a smooth revision of it when in need?
• What can I have for my reference when I'm implementing the fundamentals?
• How can I increase the speed in which I do all these?

If seen, I want to help myself to be better and effective when solving a problem by implementing what I'm learning.

Maybe, other software test engineers too have same question.  Don't you?

I'm learning new stuffs, and also unlearning what I'm learning.  I create the 101s for myself.  I see the software testing community can also make use of these 101s that I'm building.

Why You Need Maven 101?

• Today, it is a common sight that one quickly picks up a boilerplate code and run it
• Especially with the software test engineers, who wants to start/practice automation
• Pick a framework and run a command
• Execute the program successfully
• Or, get stuck in between and do not know why is that command
• Or, see an error with that command and not sure what that command is doing
• What is the difference between these commands and what does it do?
• As this, one can get into different contexts where one gets trapped; not blocked
• How to help self to navigate out from here?
• I see this 101s can come to help

Anytime, you picked a Maven project and built it?  For example, a Selenium code written as a Maven project.  Do we know what Maven is and why the Maven project here?  And, what these different Maven command means and what it does?  For having this understanding, this Maven 101 comes to your help.

Maven for Software Test Engineers 101

I have my Maven 101 here.  I refer to this source when I revise my fundamentals.  This can be of help to you as well and also can be a start point.

This has helped me to understand the different build life cycles and how a Maven command is all about the plugins.

I have provided the Reference section which is also a credit that I give them for helping me to unlearn and learn better.