Test vs Validation………..

As a software developer, I belong to the world of micro and nano reactions and observations, as we (Software engineers) create to and fro reactions (definitely by this I mean software functionality, i.e. users' request and applications' response).

During my development career, every day before I go through the words "test" and "validate"  once ready with deliverables. 

What are these actually? Simply literary words or do they carry weight?

My answers: yes, they do.

Description:

Whenever I create or make changes pertaining to application, I do a cat eye observation of it. I am saying like this because by that time, I know I am the expert who knows the application’s behavior and flow. It may be code wise or UI wise but yes, I know. That's why, what I do, I term it as "validation". 

But when it comes to normal user, they don't care how it should happen? They wary of how is it behaving? They don't bother about what's the flow; they worry about is it good? Is it comfortable? Is it posing any threat to my information? For the sake of these doubts, they do a round-around of the application. In my opinion, what they do is what we call "testing". They test the application, they test their comfort with the application, and they test their doubts and try to clarify them.