Blog

30 Things a Software Tester Should Know

Yoda Magister · February 26, 2019

30 Things a Software Tester Should Know

Starting today, we begin a free 30-lesson cycle that will allow you to learn about software testing. Or strengthen your position if you're already working as a QA.

We begin our journey, where you will encounter tasks you can complete to thoroughly level up in the field of QA.

Software testers are always learning, but we still can't always give an accurate assessment of their knowledge.

So, in this cycle, we'll learn about the product we're testing. How we learn and build relationships with developers, managers, and testers. This will make us great at what we do every day.

Being a QA means being a chameleon 🙃🙂. We change depending on the environment we're in or the product we're testing. We must continue to study the tools needed to test each product.

I split all the tasks into 30 fragments to create more digestible portions of information. This is by no means a complete list. It will help you start your journey into the world of Senior QA. Do each task and work towards self-checking results to achieve the Zen of testing 🕉.

After completing each of the tasks, carry out a mini-investigation on the topic to delve deeper into it. Google similar articles following the instructions, think about what you've already done, and consider your personal experience with the topic. You might even want to redo the task and do everything differently the second time.

We will publish each task in the group and in the blog with a frequency of 1-5 days, and answer questions in the comments to each task until the next one appears.

And remember, every tester is unique, and this is your main advantage in testing abilities.

✓ (Task 1) Are you interested in software testing?

Let's start with a little self-analysis.

A crucial part of a tester's work is proper thinking and awareness of the profession as such.

Think about what brought you to Galaxy QA Academy?

Why is software testing valuable to you?

What do you think software testing is?

We'll talk about this in more detail in the next task, but think about your opinions regarding these questions right now.

The purpose of this post is to answer most of these questions. Moreover, you will have even more questions along the way. Most importantly, questions encourage seeking answers, which leads to learning!

We are surrounded by technology every day. There are many things from the world of IT that you use in your daily life, which can affect you. It could be a program at work that takes more than a minute to load. An app on your phone that crashes immediately after an update. Or maybe you've locked your email and discovered you can't recover or reset your password. Perhaps you've started thinking more about a certain program after looking at its task manager during loading and seeing how many resources it's consuming.

Can you be exactly the person who strives to make software better? Can you become a defender for users? For business? For your colleagues at work?

Do you know what it takes to become one? Do you know how you need to study? Think about all the good and horribly bad programs you've encountered in your life.

And you're a chameleon in both cases!

In a good situation, a tester wants the product to remain even better, so you continue studying it to stay the top user.

In a bad situation, you want to know more to feel that you did everything possible before releasing the software to avoid user-side errors. Learning is the key. No matter the situation, you will always be learning, even if you don't realize it.

This sounds intimidating, BUT don't let it discourage you. Start with the first question and think about it. By the end of this guide, you'll be more confident in your answers to all these questions.

So, what's next:

Try to write why you are here in this group or on this site.

Where do you plan to be at the end of the course/training?

What skills do you currently have that you consider useful for testing?

What do you think about software testing?

Plan your responses to this post in your schedule. Be realistic about what you can achieve. Consider your daily work and energy levels.