One of the challenges for a test automation newbie is the change of mindset; from a developer to tester and vice versa. I encountered this the first time I wrote my very first test automation script. I did some manual exploratory testing using mouse and keyboard, I visualized a certain repeatable intact scenario, recorded mouse and keyboard interactions, then played back the script and a neat automated test report popped with the passed and failed results, and I couldn't be happier :)


As I finished my delicious launch, an email popped with an unpleasant content: Please test the functionality when the bla bla bla is not bla bla bla. Now wait, recording will not do me this. The only way I can do it is by writing my own new java class. So I rolled my sleeves up and started coding.


Hours and hours passed, and noticed that my thinking is dangerously drifting into a developer mindset. I remember some testing guru saying : "A good developer is not a good tester", but am I not a developer now? How can I develop a good automation script and keep in mind my third eye sharp and active?


Through practice, I learned that in order to write a good automation script, and at the same time, the automation script tests it's intended functionality, you need to learn to change the way you think and to keep remembering that you are after all a tester and not a developer.

While writing an automation script that involves coding intervention, think as a developer and keep yourself contained in the quality theme. This is manifested when you run this script against your application. At this moment, abandon your developer mindset and think only about the test results.


This may seem easily said, and yes it is, but through practice an oxymoron of test developer can be achieved.

Quality is the key of product success or failure, our job is to ensure the quality of the product is conducted, in other words assure that product has met its requirements. Literally, has met its requirements, which means Quality Assurance should have major role in each area participates in producing the product and do whatever it takes to achieve this goal.

Therefore, Quality consists of more than one area, one major area is testing, and many types of testing can be applied on any software products to ensure the quality is as expected.


Who is talking about Software product testing?!!! You mean those tools built for help us in daily works and jobs?!

Yes these tools and products were tested to ensure customer satisfaction and needs have been met. In fact, most of tools we usually use passed in Software Development Life Cycle.

Software Development Life Cycle?!! has QA role in this SDLC?!!

Yes each part created and developed should be tested to make sure it is functioning properly, therefore in each Project life cycle there would be testing phase.

During this phase, we apply many tests on this product and ensure it will survive in real life, such as functional, System, regression, performance, automation, integration, white box, black box, ad hoc and smoke testing. There are more types of tests can be executed on software products and it depends on nature of the product and the purpose.


So Software Quality Assurance has standards, basics, terms and theories?

Quality assurance is found to force standards, so Quality Assurance has its own techniques, methodologies, processes, concepts, terms and standards.

So cheer up, TestSquad was found to build strong knowledge in anything related to Software Quality and together we write SUCCESS letters in the page.

The Big Question that concerns us always
How to have BETTER QUALITY in LIFE?

The answers of this question lies under how, why and when …

The definition of Quality varies a lot

Sample of the answers that you can get around QUALITY...

* Quality is Job #1
* Quality, It's a Way of Life
* Quality is a degree of excellence – WEBSTER
* Quality is the totality of features and characteristics of a product or service that bear on its ability to satisfy given needs. - American Society for Quality
* Quality of design
* Quality of the process
* Quality is the customers' perception of the value of the suppliers' work output
* Error-free
* Quality is doing the right things right and is uniquely defined by each individual

* Clean, precise and flawless
* Quality is a fulfillment of expectation
* Quality is the expression of human excellence.

Many definitions of Quality, this word can be defined depending on what you are talking about

To software testing we know:
* (Producer’s Point of View): Meeting requirements - Philip Crosby
* (Customer’s point of View): FIT for use - Joseph M. Juran

I reach to say that QUALITY IS EVERYONE'S RESPONSIBILITY
Every one can create his own definition of Quality, something that satisfies in all areas of life - Quality is in the eyes of the beholder

Quality People Live with this Word

My Definition is…
QUALITY of Mind to be... Creative, Innovative, Outspoken, Ambitious

Find your Own Definition…
TestSquad will help you to START … DEFINE QUALITY!!