Picture this: You start your business full of excitement, you’ve got an amazing product or service, and you decide it’s time to “go digital.” So, you create an Instagram page, slap together a free website template, and set up WhatsApp Business with an automatic message saying, “Hello, welcome! How can we help you?”

Days go by… and nothing.

No clients, your website loads slower than a turtle on bad WiFi, and you start wondering if digitalization is just a myth created by big corporations to make you waste money.

Relax, you’re not alone.

Going digital is key to growing in today’s world, but many businesses fail because they make some basic mistakes. Here are the most common ones and, more importantly, how to avoid them without losing your mind.

1. Thinking that just being on social media is enough

A lot of entrepreneurs believe that simply creating an Instagram account means they have a “digital presence.” Wrong. If you don’t have a strategy, you’re just taking up space on the internet.

How to avoid this?

Clearly define who you’re talking to, what problem you solve, and how to communicate that in a simple, engaging way. And no, just posting pictures of your product with a price tag is NOT a strategy.

2. Not optimizing your website (or worse, not having one at all)

A poorly designed website can scare off potential clients faster than a full-priced item on Black Friday. If your site looks like it was built in the early 2000s, doesn’t load properly on mobile, or fails to explain what you do, you’ve lost the battle before it even starts.

How to avoid this?

Make sure your website is clear, fast, and functional. You don’t need anything too fancy, but it should help customers find what they need in seconds.

3. Ignoring the customer experience

Ever messaged a business on WhatsApp and got a reply three days later? Or worse, they respond like they’re doing you a favor?

How to avoid this?

Automate where necessary, but don’t forget the human touch. Chatbots can be useful, but nobody wants to talk to a robot that sounds like a 90s voicemail machine.

4. Not tracking what’s actually working

If you’re posting on social media, have a website, and an active WhatsApp line but don’t analyze the results, you’re basically driving blind.

How to avoid this?

Check basic metrics: How many people visit your site? Where do they come from? Which social media posts get the most engagement? Adjust based on this data.

So, how can you digitalize your business without failing?

• Start with a clear strategy.

• Make sure your website and social media are functional and attractive.

• Focus on the customer experience.

• Track what’s working and adjust accordingly.

It’s not about being everywhere – it’s about being where it truly makes a difference. And if all of this sounds overwhelming, don’t worry. I’m here to help you optimize your business without the headaches.

Drop a comment below and let me know which of these mistakes you’ve seen (or made – no shame, we’ve all been there). Let’s talk!

To get started with web automation, it is important to know the different ways to find and access web elements. This time we will learn in a simple way, how to find elements using CSS selectors and the Chrome Developer tool.

You should not be an expert in CSS or web programming, to start with just having basic knowledge will be more than enough. You can refer to the official documentation for details https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors

Among the CSS selectors, we will see that we can select using the ID of the element, the class, the path queries, and nth-child (). Let’s see in a simple way how you can use them.

CSS — ID selector:

Select the element that corresponds to the ID; which must be unique. To find the element, right-click on the element and then click on the Inspect option: By clicking on Inspect, a tab will open where it will show us the details of all the elements.

To access an element by ID, we put a # + i dname, in this case #search_query_top .

A useful way to find elements is using CSS selector — Class:

By specifying the class it will bring us all the elements that have the specified attribute. To search by classes, you must add (.) + Classname, in this case, it would be .search_query

It is also possible to specify what type of elements we want, for example, input.search_query, this would show us only the elements of type input that contain this attribute.

To find elements by Tag name — CSS Selector:

We just have to look for the tag name that we want to see in this case ul. It is possible to perform more specific scenarios of elements; that as you understand how CSS works you can make different combinations

Another way to use CSS Selector is with Path Queries:

This option gives us the path of the element using the order of the HTML tags in which they are found; for example:

Chrome developer tool gives us the option to generate this location of the element, but for practice, I prefer to do it manually.

At this point where we have a list of elements, but we only want to access a record from that list is where we can implement nth-child (elementPosition), for example:

In this scenario, we see that we are accessing the element that is in position 3 of the list.

If you are automating web applications, you will see that handling CSS selectors will be very important.

I hope you find it useful.

Thank you for reading my blog.

As we know, all careers in technology require a higher level of dedication and effort; since new things always come out and you have to be updating yourself to keep updated with new things.

But what happens when you already have children, a husband, and at the same time you have a full time job?

In my own experience, sometimes I feel exhausted and the truth is that time does not spare me. To keep an organized routine is what has helped me to continue learning, writing on my blog, and the most important thing spending quality time with my family.

Some tips that worked for me :

1. Set weekly goals that help me grow professionally

For example: If you desire to learn about Selenium Webdriver” search for tutorials or reading materials and have it on hand so when the time to study comes you don't have to waste time surfing on the internet.

2. Related to my son:

I established a bedtime routine for my child, so he has to go to sleep at 8:45- 9:00 pm. (even if he’s not sleepy, he goes to bed at that time).

So, my study/writing time starts at 9:30–11:00 pm. Depending on how fast I want to finish the material to study I can set more time. (I do this routine Monday — Friday). These are my personal experiences on how I deal with my child and organized my time.

I should emphasized that this is not always perfect; There are many variations and situations around that can prevent one day from sitting down to study…. and that’s OK too!! RELAX!!

In this time where we have so much access to information and what other professionals do; you could feel pressure to keep productivity; remember your conditions are unique; set your own goals, look for what works for you in order to achieve what YOU really want.

And don't forget these are hard times, it is an experience totally new for all of us, it is ok to just do NOTHING; just allow yourself to live this stage.

No matter how hard it looks now, I know you can and You will!!

What I love the most of this section #QATALKING is that I learn a lot, and sometimes it helps to change my mind in some topics (ex. writing detailed test cases).

This time I had the opportunity to interview Brijesh Deb, a Senior Testing Consultant with a lot of experience and knowledge to share. I knew about him on Linkedin and his posts are incredible and I know you can learn from his way of thinking about testing

So.. Let’s start!!!!

Q. Tell us about yourself. How and when you started into tech?

I am Brijesh Deb. I am from India and I live in the Netherlands. I started my journey almost 2 decades ago and started off working as a content developer, then did a brief stint as a developer before starting off as a tester and I have been a tester ever since. It has been a fun journey thus far.

Q. What’s your actual position?

I am a Senior Test Consultant with Sogeti Netherlands, working with their Digital Manufacturing unit helping their customers get on board the testing journey or help get better at testing.

Q. While you were looking for a job; Did you faced the Impostor Syndrome? What advice can you give for anyone facing it currently?

I speak at conferences and meetups. I have faced Impostor Syndrome but not while looking for a job but while preparing for these conferences and meetups. I think the symptoms of Imposter Syndrome are fear of failure and self-doubt and worry about being judged. My simple advice is to focus on your strength, believe in your knowledge, skills, and experience and you should be able to beat the Imposter Syndrome.

Q.You are a role model to a lot of professionals, I know everybody would like to know about your process to get into this position. What do you think helped you most?

First of all, it’s really kind of you to say that because I draw my inspiration from people I interact with. I have spent a lot of time observing people actually testing. I read a lot of testing books, Lessons Learnt in Software Testing by James Bach, Cem Kaner, and Brett Petichord being my first and most loved book until very recently when I read Buddha in Testing by Pradeep Soundararajan. I read blogs from testers all over the world. I like to talk about testing and learn from the experience of fellow testers irrespective of the amount of experience that they have had in the industry. I believe everyone has a story to tell and can teach us something. I engage with testers in meaningful conversations and always look to learn. This has been extremely beneficial.

Q. Manual or automation testing? And Why?

Ah well! Let’s establish one fact very clearly here, there is nothing called manual testing. You will see me using #nothingcalledmanualtesting a lot. Funnily enough automation testing also does not exist. These are just names for the way people execute their tests. I think it is inappropriate to classify testers based on the method of execution of their tests. So to answer your question. It is testing that I focus on. 😊

Q. What Do you think about test cases, importance, etc?

Testing is experimenting. It is therefore a great idea to make note of the experiment you are going to run. Sometimes you know the results you may be looking for and sometimes you do not know the results. So IMHO, it makes great sense in having test case but there is no need for an absolutely detailed test cases. A simple scenario description should be enough.

Q. What kind of documentation your team made while executing testing?

I am a firm believer in the Agile manifesto and the manifesto talks about Working software being more important over comprehensive documentation. So, I always focus on documenting that is just enough and not going for full-blown documentation.

Q.What tools do you use in your position?

I work with a lot of customers so it really depends on what they are looking for so the tool choice really depends on the project and the needs of the customer. I work a lot with JIRA, XRAY and a lot of other proprietary tools

Q. As you know this blog Is focus on Quality assurance; How do you think a Manual Tester can transition to Automation testing, easily? Is it required to know programming to start?

I would like to reiterate that I do not really like to use the terms manual and automation. However, to answer your questions, it helps if the testers can use the knowledge of code and tools for testing. Testers can communicate better with developers and can help debug problems and add more efficiency to the way they test. Knowledge of coding helps but is not mandatory in my opinion. I would suggest to first focus test craftsmanship before looking at coding. That helps them build a solid foundation for testing before they can compliment their knowledge with coding.

Q.From your perspective, How do you describe your ideal tester?

Hmmm. That’s a very good question. An ideal tester for me is one who is good at critical thinking, good at thinking out of the box, a good analyst, and most importantly a strong communicator. He/she should be willing to ask a lot of questions and challenge the status quo, challenge the obvious, and be receptive to feedback and willing to learn.

Q. Finally, give any advice to those people trying to get into automation testing?

First thing, testing with tools and testing without tools are complementary to each other and should be used in tandem for greater benefits. One thing to remember is that what we call as automation is a service to testing and not a replacement because knowledge of code and tells help you become more efficient with your tests.

Sooo!! What do you think about this interview? I hope you enjoyed it as much as I did.

Thank you for reading my posts!

If you’d like to see my daily content follow me on Instagram @testmyjourney .

❤❤❤❤

Pytest is a testing framework that allows us to write code using python. You can use Pytest to test anything; databases, UI, and APIs; but is pretty recommended for API.

Some of the advantages of using pytest are :

• Easy to learn and understand
• Also, there is a lot of documentation available
• Parallel Testing Execution
• Allow executing a particular test case or a test suite
• Open Source.
• It helps to keep testing code maintainable and readable

There are some IDEs you can use to start but I’m using Visual Studio Code and for other projects I use Pycharm. Which IDE do you think is better?

As I said in previous articles, if you’re starting with testing automation; remember that you’re a tester .. I mean you don’t have to know everything about a programming language to start; basic knowledge will help you.

Before starting with Pytest I made a basic course for Python and I challenge myself to make a programming exercise every day (#RealLifeSituation: when my responsibilities allow me to; remember I’m a wife/Mom/QA Engineer).

I’ll be posting in the next days some tutorials/practice that I made to learn Webdriver with Python.

Why are you using or not Pytest?

Sus respuestas me han agregado un gran valor a nivel profesional , personal y ha resultado muy inspiradora y practica para quienes estan iniciando en el mundo de QA!!

I hope this interview will be inspiring for you! ❤

Let’s Start…!

1. Cuéntanos sobre ti. ¿Cómo y cuándo comenzaste con la tecnología?

Mis hermanos y yo tuvimos la gran ventaja de crecer con una computadora con Internet en un momento en que la mayoría de las personas con suerte tenían un televisor con cable.
En 1998 comencé a tomar lecciones de aplicaciones de Microsoft en una escuela local. Me ensenaron Windows, Office, Access … todo lo que había que saber sobre ellos y cómo usarlos profesionalmente. Entonces, en un momento en que la mayoría de las personas no tenían computadoras aquí, ya sabía cómo crear y mantener un servidor de Windows, cómo trabajar con una base de datos de Access y cómo usar las herramientas de Office de manera eficiente. Esta fue una gran ventaja para mi carrera inicial.Una vez que ingresé a la universidad y comencé a estudiar Ingeniería de Sistemas, no estaba seguro de lo que estaría haciendo por el resto de mi vida. En aquel entonces no conocía el mundo de Aseguramiento de Calidad, hasta que un día en 2007 mi hermano me dijo que su jefe estaba buscando a alguien para trabajar en la automatización de pruebas. No tenía idea de qué era esto, así que fui a hablar con él y averiguarlo. Me preguntó acerca de mis habilidades de programación, y estaba satisfecho con lo que escuchó, así que comencé ese mismo día trabajando con Rational Functional Tester y aprendiendo sobre el Aseguramiento de calidad. Nunca miré hacia atrás; desde entonces soy Ingenerio QA.

2. ¿Cuál es tu posición actual?
Soy QA Manager en GBH.

3. Mientras buscabas trabajo; ¿Te enfrentaste al Síndrome del Impostor? ¿Qué consejo puedes dar a cualquiera que lo enfrente actualmente?
Mi primer trabajo como ingeniero de control de calidad llegó con la comprensión de que no sabía qué era el control de calidad, por lo que no enfrenté el problema del Síndrome Impostor en ese momento, pero una vez que comencé a ocupar más puestos de liderazgo, sentí que no era suficiente y que tal vez se equivocaron al ponerme a cargo de tales responsabilidades.
Les recomendaría que miren sus logros y deje que le hablen. No seas el que duda de tus propios méritos. Nadie comienza a saber todo acerca de una posición, hay una curva de aprendizaje para todo lo nuevo. Su primera vez en cualquier posición será una prueba, solo aproveche al máximo y APRENDA. Si por alguna razón falla, al menos la próxima vez tendrá la experiencia y comenzará desde un nuevo lugar.

4. Usted es un modelo a seguir para muchos profesionales; Sé que a todos les gustaría saber acerca de su proceso para entrar en esta posición. ¿Qué crees que te ayudó más?
.. Critical Thinking!
Si deseas iniciar en QA , debes pensar en términos de calidad. Asegúrate de aprender a entender lo que la gente necesita. HACER PREGUNTAS. Un ingeniero de aseguramient de calidad debe ser curioso. Si no hace las preguntas correctas, nunca obtendrá las respuestas necesarias que harán que un cliente obtenga lo que necesita.
En ocasiones, formulará preguntas incorrectas, y eso está bien si aprende de ellas y lo hace mejor la próxima vez.

5. ¿Pruebas manuales o de automatizadas? ¿Y por qué?
Ambos. Las pruebas automatizadas son las mejores para las regresiones. Las pruebas manuales son las mejores para encontrar errores que solo la exploración y el pensamiento crítico detectarán. Las pruebas dependen del contexto y siempre debemos pensar en lo que es mejor en cada escenario.

6. ¿Qué opinas sobre casos de prueba, importancia, etc.?
Los casos de prueba son la mejor manera de documentar y compartir con el equipo cuál es su plan de acción. Dejarán en claro que los pasos a seguir cubrirán lo que el cliente necesita para verificar y validar.

He descubierto que los testers más experimentados tienden a funcionar bien con menos documentación. Pero los testers menos experimentados cometerán errores que pueden ser muy costosos si los casos de prueba no están presentes. Debe tener en cuenta que incluso los experimentados son nuevos en un proyecto en algún momento.

Basado en esto, siempre sugeriría que el equipo mantenga una buena base de datos de casos de prueba y la mantenga constantemente para que cualquier evaluador sepa que no faltan pasos importantes que puedan afectar negativamente la confianza que los clientes tienen en el equipo de Garantía de Calidad.

7. ¿Qué tipo de documentación hizo su equipo al ejecutar las pruebas?
Utilizamos test charters. Esta es una gran herramienta que nos permitirá realizar un seguimiento de lo que estamos probando y nuestros hallazgos. También nos ayuda a asegurarnos de tener todo en cuenta antes de cerrar un esfuerzo de prueba.’

8. ¿Qué herramientas utilizas en tu posición?

Básicamente, cualquier cosa que me facilite la vida.
Tenemos herramientas internas que nos ayudan a realizar un seguimiento de las ejecuciones y resultados de las pruebas y a obtener datos para nuestros informes de prueba. Básicamente es una herramienta de prueba que nos permite documentar y compartir nuestros esfuerzos y detalles de las pruebas.
Uso Jira, Metabase, Clockify, GitHub, Gitlab, Postman, varios chats (depende del cliente) y otras herramientas que ayudan a hacer las cosas.

9. Como saben, este blog se centra en el aseguramiento de la calidad; ¿Cómo crees que un probador manual puede pasar fácilmente a las pruebas de automatización? ¿Es necesario saber programar para comenzar?
Existen herramientas que pueden ayudarlo a automatizar sin tener conocimientos previos de programación, recuerdo haber trabajado con Rational Functional Tester y Katalon Studio, estas herramientas hicieron la mayor parte del trabajo por mí y en ese momento solo contaba con conocimientos basicos de programacion.

Por supuesto, para mejorar la automatización, debes aprender algun lenguaje de programacion para que la computadora haga lo que le dice. Por lo tanto, dominar un lenguaje como Java, JavaScript o Python lo llevará lejos.
Utilizamos herramientas para hacer las cosas, la programación es solo otra herramienta que utilizamos para hacernos la vida más fácil.

10. Desde su perspectiva, ¿cómo describe a su tester ideal?
Cualquiera que se preocupe cuando algo no funciona como se esperaba y esté dispuesto a hacer algo al respecto.
Una persona curiosa que quiere saber por qué las cosas funcionan de la manera que lo hacen y quiere asegurarse de que funcionen como deberían.
Alguien dispuesto a aprender lo que sea necesario para asegurarse de que las cosas se hagan bien.
A puzzle solver who does not rest until he gets the answers they need.

11. Finalmente, ¿tienes algún consejo a aquellas personas que intentan ingresar a las pruebas automatizadas?
Lo primero que debes aprender no es CÓMO automatizar, sino QUÉ automatizar. Por lo tanto, primero aprenda sobre Garantía de calidad y luego entre en las herramientas que lo ayudarán a lograr una calidad más fácil.

Leer, ver videos, hacer preguntas. Aprender constantemente y compartir tus conocimiento.

¡¡WOW!! Esta es una de mis entrevistas favoritas! ❤
¡Gracias por leer mi blog! ❤

English post: https://asmiry.tech/qatalking-jose-rodriguez/

A medida que ha evolucionado la tecnología y el desarrollo de aplicaciones complejas , se requieren de procesos que nos ayuden a mitigar el riesgo de defectos que pueden causar perdidas millonarias o la pérdida de credibilidad por parte de el cliente; por esta razón es sumamente importante que en nuestra posición de Analista de Calidad o desarrolladores creemos las condiciones necesarias para realizar el flujo completo de la aplicación.

Decidi escribir sobre este tema , porque he visto como en muchas ocasiones que no le damos la importancia requerida a la creación de los casos de pruebas.

Que son los casos de pruebas?

En palabras llanas, son condiciones o variables que identificamos y que nos permitirán determinar si la aplicación cumple con lo requerido por el usuario usuario funcional . Los casos de pruebas son creados a partir de la información que tienen los requerimientos funcionales.

Es importante que cada caso de prueba contenga los pasos a ejecutar, data que debe utilizarse y el resultado esperado.

En la internet hay disponibles muchos templates que pueden ser de soporte al momento de crear casos de pruebas.

Para crear casos de pruebas de manera satisfactoria, debes tomar los siguientes puntos en consideración:

1. Entender de manera clara lo que espera el usuario funcional
2. Si es necesario reunirse para entender la necesidad.
3. Realizar las preguntas adecuadas.
4. Luego de entender de manera clara lo que se espera, Identificar las condiciones que estarás evaluando.

5. Escribir los casos de pruebas de manera clara y sencilla; de modo que cualquier persona pueda entenderlos y reutilizarlos.

6. Utilizar identificadores para cada tipo de pruebas.

7. Evaluar las condiciones negativas, es tu oportunidad to break the app! Think out of the box.

8. Realizar una matriz de trazabilidad, que te permita vincular los casos de pruebas con los requerimientos .

9. Documentar los resultados para cada caso de prueba; de modo que puedas utilizar esto como evidencia de ejecución de tus pruebas.

10. También es necesario priorizar cada caso de prueba(Alto- Bajo)

Como puedes ver, la base para crear buenos casos de pruebas esta en la documentación que tengamos a mano; pero si no la tienes no debe ser una limitante para realizar un buen trabajo; Reunete con tu supervisor, con el PM hasta que el requerimiento contenga todo lo que necesitas para definir tus casos de pruebas y procura que todo quede documentado por correo.

Crear casos de prueba es super sencillo, pero también definirá el éxito de nuestras pruebas.

Interactuemos un poco; Cuales casos de pruebas utilizarías para un Login ?

I’m sharing more knowledge in @testmyjourney on Instagram! Hope see you there!

English Post:https://asmiry.tech/index.php/2020/06/10/qabasics-test-cases-definition-and-importance/

This time we are going to be learning about functions in Python.

Let’s start defining what is a function? A function is a unit of code that can be reused throughout a program.

Now that we know the meaning of function, we can build one.

To define a function in Python we have letters def, descriptive function name, parenthesis, and the colon :

Take into consideration that the body of our function is always indented 4 spaces and we remove the spaces when we want to call a function.

In order To call the function we need to let 2 lines of blank space and write and We need to write the unique name of the function follow by parenthesis.

Easy, right? This is how a simple function is created.

This #QATALKING section is created to talk with professionals in Tech, to share some experiences and valuable knowledge about Quality Assurance.

This time I’m talking with Toyer Mamoojee!! I can’t believe I’m doing this interview!! I took his Jest course on Test Automation University(TAU); I connected with him through Linkedin and he became my QA Mentor because in every conversation with him I learn something new!

I know you’re going to enjoy this interview! Let’s start!…

Q.Tell us about yourself. How and when you started into tech?

I am Toyer Mamoojee, originally from South Africa, I have now relocated to the UAE with my family. I started my career in tech the first year after graduating from University. I went straight into Test Automation as a Junior automation tester in 2003. I saw an advert from a company that was looking for graduates who wanted to get into the tech industry. At that stage I only knew that Testing was a phase in the Software development life cycle, so I just wanted to get my career kicked off. Little did I know how much I would love the role and the field itself, 17 years on, and I still love everything software, testing, and test automation.

Q.What’s your actual position?

I am a Head of QA at a leading bank in the UAE

Q. While you were looking for a job; Did you faced the Impostor Syndrome problem? What advice can you give for anyone facing it currently?

Yes, I think some of it was partly because of the tough economic situation in South Africa, where the unemployment rate was quite high. I kept asking myself am I good enough to stand a chance to get accepted for a job if there are so many candidates out there. However I still kept backing myself. My advice to anyone who faces something similar is to keep believing you are unique and have loads to give back to anyone who employs you. It’s natural to feel impostor syndrome but it’s your attitude and determination to keep motivating yourself that defines how you overcome the predicament.

Q.You are a role model to a lot of professionals, I know everybody would like to know about your process to get into this position. What do you think helped you most?

Firstly thank you. Well to get into my current position I have to look back slightly to a few years back. I always believed I wanted to specialize within the Agile Testing and automation space, and also go into a position of leadership. So that was my initial goal and I kept on following the path of knowledge acquiring and pairing with others in the testing community to broaden my skillset, understanding and experience. This approach definitely paid off for me and I am grateful for every experience I have had, that has lead me to my current role.

Q.Manual or automation testing? And Why?

OK, most people would think I would say Automation testing, especially since my career began straight into test automation, however I am a fan of ‘Agile Testing’ which in my view doesn’t differentiate between the 2 forms. I believe a tester should possess the knowledge and skillset to seamlessly acknowledge tasks that are automation focused and those which are manual. There should be nothing holding the Tester back to tackle a task based on what’s best for the given situation. So my answer is, it depends on the task in front of you, along with a whole lot of other factors.

Q. What tools do you use in your position?

I use so many different tools, tools spanning process, technical, automation and even thinking aspects of my role. On process side- MS Azure DevOps and sometimes Jira possibly even Trello. Technical- Postman, Fiddler, DB tools etc Automation — Anything from Jmeter, Cypress, JS test libraries and more Thinking tools — MindMaps

Q.As you know this blog Is focus on Quality assurance; How do you think a Manual Tester can transition to Automation testing, easily? Is it required to know programming to start?

It’s not necessary to know programming from the start however it would definitely help to know some of the basics. Regardless I have personally mentored a few people with zero past programming experience to become fully competent in automation tasks. My key advice here is to take baby steps, always start off small, and keep building knowledge. I would say start with 1 language then learn the basics of programming that goes with it. For example, conditional statements, loops, variables. Those are aspects that are pretty universal across majority of different programming languages.

Q.From your perspective, How do you describe your ideal tester?

I think I touched on it a little above. For me an ideal tester should have the ability to perform both manual and automation testing along with multiple technical testing tasks. This tester should also be versatile and try to incorporate some leadership skills, performance testing plus have a good understanding and overview of the system architecture. Other supporting factors like being a team player, starting and driving initiatives, and having the confidence to address ‘awkward’ team/release issues are great additional qualities.

Q. Finally, give advice to those people trying to get into automation testing?

Once again, I touched on this earlier. You could initially base your first programming language on the automation tool you want to use. The first advice is to pick a popular entry programming/coding language and stick with it until you grasp the programming concept. Then go ahead and try to maintain existing scripts if there are any at your company, alternatively start creating small basic scripts to build up your confidence by solving real-world problems. Always keep an eye out on other automation tools on the market and what the pros and cons of each are, this way you build a solid, well-rounded knowledge base on tools that are available. And finally, my advice is just to believe that test automation is not rocket science if others can do it, then what’s stopping you?

I hope this interview will be helpful for you!! Thanks for reading!!

PD: If you have any suggestions about someone we should interview or questions, just let me know!

In the last few days received a lot of questions about this topic. Take the ISTQB exam or not? How certifications help while looking for a job?

Well, to start it is good to emphasize that this certification valid your basic knowledge, say, management of concepts, types of tests, among others. For this reason, if you have it, your employer will feel safer when inviting you to an interview.

In my particular case and I know that many of you will feel identified, I postponed the certification for a year or more, and not for fear of failing but because I understood that it was not the ideal time to commit to studying (mother’s life, work, etc, etc, etc).

At the end of 2018 I already knew that I would have to move to the USA in mid-2019; Searching and comparing offers to know what I was going to face, I realized that most of the American companies requested this certification. (EYE: I still understood that I did not have the time to study).

I knew that obtaining it could contribute to being considered for the positions because without even having a study plan or distribution of my time, schedule the Certification exam, which cost me if I remember correctly, $ 200.

I confess that the first week did not study anything, for the same hustle of daily life. But when I saw that the days next to the exam were approaching, I thought I could no longer lose my investment, and that put more pressure on me to acquire the commitment to study.

When I started studying the first thing I read was the Syllabus, I mean my strategy was to read a chapter and then read the book in detail, just to get the main idea of ​​what it was about, and then I would study it in more detail.

Something that helped me a lot at the time of studying is teaching what I learn! I still don’t know why but when I want to learn something well and manage it, well I teach it or write it and that’s how it stays engraved forever.

The first chapters are super easy; I found the final chapters a little more complex, so I had to spend more time studying.

Certifications always help and more when you plan to emigrate to another country (the competence is quite high and you must add value to your professional profile); It is a way to validate the knowledge you manage. (At least for the first step of Selection).

If you’re postponing your exam, JUST MAKE THE PAYMENT; and you will find the time to Study….. TRUST ME

I greatly appreciate reading my blog; remember if you have any questions or doubt you can write to me; it will be a pleasure to help you!