I am defect. For some people I am a mild inconvenience and for some I am their worst nightmare, probably a life threatening nightmare. For many years, people like you have treated me as a hunting target and treated me as a non-living entity – without any emotion, say or dreams. Till now, I kept my silence but now I had it enough. TestingGeek has allowed me to tell my story to the world, to tell you truth about me and my feelings.

You call me so many names (And all of them are bad BTW), but do you know anything at all about me? Do you know where I lived before you forced me to live in your code – to be found, discussed, killed, ignored and humiliated?  People tell me so many things, but do you realize reasons for my existent? I know I am not desired, I know I am not welcomed and to be honest, I do not want to come anywhere near your (sometime dirty) code, requirements etc. But you force me to live in your requirements, code, network and so many unimaginable places because of your misunderstandings, lack of knowledge or plain sloppiness some time.

You do not realize, but I pay a great price for your sloppiness and your lack of understanding. I take blame for lost life, money and happiness for many users. Plane is crashed because there was a defect; transaction was not complete because there was a bug and so on. Why don’t you pause, think and say plane was crashed because someone did not do their job properly. I am there not because I love staying in your code, but because someone took short cut, invited me there to be found by someone else. I was invited, ignored and now I am blamed. Where is justice? Unfortunately defects cannot trial humans in their court, but I hope our fate will change.

My life is extremely comfortable till you guys put me in the code. After that, it’s all misery and my life becomes extremely miserable. From that moment onwards, I live my life in anticipation of to be found, broken in pieces, discussed and humiliation. I do not like being here and so always gives you hint of my presence. Sometime, I have power to give strong hints and it becomes impossible for you to ignore me. But sometime, you just do not recognize my hints, you over look what I say in log files, you don’t notice when I create slight flicker or make your system slow. You attribute things like these to something else and leave me there to rot, to get worsen. That doesn’t leave me any option but to gather strength and try harder. Most of the time I succeed and you notice me. Unfortunately I cannot understand your situation so some time by the time you notice me, I might have crashed a plane or ruined millions. So please, practice, observe and understand my hints. I will be very happy if you find me and kill me in such a way that I do not have to come again, but alas it doesn’t happen.

Most of the time, instead of killing me you just change my dress and location. Sometime, you even break me in to pieces and scatter me in your code base. Unfortunately, we do not follow the law of physics so some time when you break me in pieces, every piece could be bigger than the original itself. Even in pieces we communicate with each other, we affect each other and because of this you get confused. Rather than finding all the pieces, you take one piece and kill it or unfortunately break it in even more pieces…and cycle continues.

Buried in your millions of line of code, I wait patiently for my angles called testers who have skills and mandate to discover me. Given the right environment these angles could find most of us. But look, what have you done to my angles? You have converted them from angel to robot so rather than finding me, they are following some steps. If I am lucky, they will find me otherwise my angles will pass by me and ignore me, because someone has given them steps to follow rather than mandate to find me. Will I not feel angry about it? How would you feel if you struggle to survive in a sea and rescue boat follow the route given to them and ignores your plea? Well, that’s how I feel.

Sometime my angels create robot themselves and call it test automation. This can be extremely useful, but only if mandate for them is to find me rather than creating more robots. Unfortunately, for many people mandate is limited to the creation of these robots and they are worse for me. Well, it’s like missing rescue boat in periodic manner, after every check-in, after every few hours or on nightly basis.

I am not selfish and understand that sometime you just can’t kill me, but believe me I will be very happy if you can find me, discuss me meaningfully and take conscious decision to keep me in the code. Because, if you do that I’ll understand that I’ll never ever kill someone because of my presence, I’ll know that I will not ruin your millions. So as long as you have assessed risk associated with me staying in your code, I can live there happily. I just do not want to live there with feeling that I am not wanted here and I can possibly hurt someone.

Please, I do not want to stay in your code or system. I am extremely happy outside, don’t invite me inside. I know some of us are a bit naughty and will come without invitation. For those naughty defects, give our angels mandate to find them in best possible way rather than following steps or creating just robots. I am good at heart and do not want to hurt anyone, so please find me and get me out of your code base.

Remember, I am a defect buried in your code and waiting for you. Please be aware of my presence and keep your eyes open for me.

Waiting to be found – A defect.

Fuente: Testinggeek.com

Compartir

Artículos relacionados

• Softqanetwork lanza WorkInQA.com
• Diferencia entre un Software Test Engineer y Software Quality Engineer
• ISTQB Advanced (Test Manager) – Mapa Mental
• El meme de las 8 cosas acerca de tu vida

Hace unas semanas andaba preparando el examen de certificación ISTQB Advanced Level (Test Manager). Se trata de una titulación oficial que demuestra la cualificación de los candidatos en varias disciplinas:

• Software Testing Basics.
• Testing Process.
• Test Management.
• Reviews.
• Defect and Incident Management.
• Standards and Test Improvement Process.
• Test Tools and Automation.
• Team Composition.

Para preparar la certificación me hice un mapa mental con todos los conceptos básicos del temario, que podéis descargar siguiendo estos enlaces:

ISTQB Advanced Level – Test Manager (FreeMind format)

ISTQB Advanced Level – Test Manager (Xmind format)

Si te interesa el mapa mental en algún otro formato, puedo enviártelo.

Compartir

Artículos relacionados

• La vida de un defecto – Its defect speaking
• Softqanetwork lanza WorkInQA.com
• Diferencia entre un Software Test Engineer y Software Quality Engineer

Con esta perspectiva, Softqanetwork lanza WorkInQA.com, el portal de empleo especializado en Testing, Procesos y Quality Assurance, que fomenta la relación entre candidatos y empresas. WorkInQA.com se sitúa como punto de referencia en un contexto en el que cada vez se apuesta más por los mercados internacionales y en que la calidad de los productos adquiere una mayor importancia como componente diferenciador.

A través de WorkInQA.com podrá difundir sus ofertas de trabajo a un segmento de profesionales que puedan aportar valor real a su negocio.

Web: http://www.WorkInQA.com
Contacto: contact@workinqa.com

Compartir

Artículos relacionados

• La vida de un defecto – Its defect speaking
• Diferencia entre un Software Test Engineer y Software Quality Engineer
• Métricas de calidad en el código
• Liderazgo y trabajo en equipo
• ISTQB Advanced (Test Manager) – Mapa Mental
• ¿Cómo saber cuándo cambiar de trabajo?
• ¿Sube la calidad de los blogs aficionados o baja la profesionalidad de los medios tradicionales?

El tema no tendría mayor importancia si no fuese porqué muy a menudo ambos puestos (y responsabilidades) se confunden. Y es que todavía cobra mayor criticidad cuando las expectativas dentro de la organización no están claras respecto a ambos perfiles. En la mayoría de empresas se contratan STE, esperando que estos ejecuten el rol de SQE y esto entraña diferentes peligros. El mas importante: los STE precisan de un gran conocimiento sobre el aplicativo a probar, mientras que los SQE han de ser grandes conocedores del ciclo de vida de desarrollo de los productos.

A continuación podéis encontrar un pequeño resumen de las expectativas que deben cumplir ambos roles:

Software Test Engineer (STE)

• Objetivo: Verificar y validar que el producto cumple con las especificaciones.
• Entregables: Análisis del producto en lo que se refiere a los unidades  desarrolladas (componente, sub-sistema, sistema, aplicativo, …) y resultados de las ejecuciones de pruebas.

Software Quality Engineer (SQE)

• Objetivo: Verificar que el producto es desarrollado conforme a los procesos definidos, así como la revisar e implementar cambios en los procesos.
• Entregables: Análisis de las desviaciones en los procesos del proyecto e identificación de oportunidades de mejora.

Obviamente estas dos definiciones admiten modelados específicos a cada organización y pueden adaptarse a escenarios mas complejos o cambiantes.

Artículos relacionados

• La vida de un defecto – Its defect speaking
• Softqanetwork lanza WorkInQA.com
• ISTQB Advanced (Test Manager) – Mapa Mental
• Métodos de entrevista y el modelo de madurez CMM
• Factores implicados en la alineación entre tecnología y objetivos de negocio
• Alineamiento de las Tecnologías de la Información y Comunicación con los objetivos de negocio
• Reflexiones sobre la sobre software libre y las administraciones públicas
• Software libre: ¿perjudica el desarrollo profesional?