GalactiQA Quiz — a starship where the atmosphere of professional topics blends with the thrill of play.

Get ready for a quiz — a game of questions and answers. We will tackle puzzles about testing, QA life, IT, and technology in general. You can bring your own team of 3–6 people, or come solo — we’ll form teams on the spot.

The winning team will receive prizes from the SQA Days organisers!

Jump aboard the GalactiQA Quiz, light up the mood and shine like the stars!

Choosing a metric is not a technical task, but a strategic decision. A mistake at this stage can cost a company millions and months of wasted work. In this round table, experts from different fields will propose their evaluation approaches using real cases to clearly demonstrate how context, business objectives, and professional perspective dictate the choice of the key metric. We will not look for a single universal answer — instead, we will learn to ask the right questions, identify the strengths and weaknesses of different approaches, and find the balance that leads to real success.

Be ready to take part in live polls and ask tough questions!

• How to determine if you're asking for much or little?
• How to increase your salary without fearing redundancy?
• How to negotiate instead of feeling like a beggar?
• Should salaries be adjusted for inflation?
• Hit the ceiling on the project. How to further increase your salary?
• You try and try, hear 'well done', but why doesn't the salary change?
  

Have you pondered these questions? Join the presentation. As a leader of a large team, I will explain how the answers to these questions may appear from a manager's perspective.

What if work could be a game? Imagine blasting away a boring task with a cosmic blaster and earning rewards for it.

What if you weren't just a tester, but a hero in a cosmic saga, destined to defend quality against intergalactic crutches?

In this workshop, we'll share our experience of injecting a bit of gaming into our work and guide you through this journey. 

Each participant will become a member of the Hero Academy:

• We'll discuss and select goals for our mission.
• Create a roadmap, which doubles as a task list (achievements) to complete.
• Explore the challenging meteors that await us during execution.
• And choose rewards for successful completion.

In the end, every graduate will have a list of achievements they can apply to their work.

How to build relationships with colleagues so that conflicts do not occur, and how to behave in order to mitigate the problem in case of conflict? This is the most popular question on the subject of conflicts. And, if you answer it head-on, you should:
1. Do not use conflictogens (conflict provocateurs).
2. Do not respond with a conflictogen to a conflictogen.
3. Concede as soon as there is a contradiction in communication.

Question. Will you be happy with the fact that you gloss over your interests in every moment and ignore your needs just to appear "good" and non-conflicted?

More about conflict in the talk.

Translated with DeepL

During the discussion, we will focus on the most pressing issues regarding the testers' education:

• What practices and approaches should be learned from past learning experiences?
• What's wrong with the training of testers today?
• How can we make the training of testers tomorrow not only effective but also exciting?

We will focus on questions from the audience! We are sure that you have a lot of things to say and ask about our first-class experts.

Do we notice the feedback we receive at work? Do we notice positive and negative feedback, or just one? 

How is it expressed? 

Is it possible to motivate yourself when feedback seems to be lacking? 

And when you give feedback, do people really notice it? 

And in general, is feedback to be received or taken?

I've been working in a product company for many years and have conducted hundreds of interviews with outsource and product testers. And now I want to share my observations about what differentiates testers in these two areas. To do so, I will walk through the main stages of product development and reveal the competencies that are required at each of them. 

 The talk is useful for those who intend to immerse themselves in product testing.

Я, как и некоторые из вас, уже будучи опытным тестировщиком, несколько раз переходила с одного места работы на другое, надеясь, что на новом будет лучше, интереснее и т.п. И правда было интересно, ново.. Но! Через какое-то время я понимала, что столкнулась с такими же проблемами, от которых убегала. 

Почему так происходит и что можно с этим сделать на этапе собеседования? Я нашла ответы на вопросы для себя и хочу с вами ими поделиться.

How questions at the interview test the level of knowledge?

Why something is studied, but then it cannot be applied in practice?

In the talk, we will consider these moments from the perspective of Bloom's taxonomy - a system that demonstrates stages of learning some information. And with examples, we will understand how we can ask questions in interviews in order to actually find out the real level of the candidate knowledge, whether this level suits us.

How questions at the interview test the level of knowledge?

Why something is studied, but then it cannot be applied in practice?

In the talk, we will consider these moments from the perspective of Bloom's taxonomy - a system that demonstrates stages of learning some information. And with examples, we will understand how we can ask questions in interviews in order to actually find out the real level of the candidate knowledge, whether this level suits us.

In the talk, we will briefly go over some aspects of iOS applications that can help in testing or which are simply useful to know. This is the life cycle of an application, file structure, working with guidelines, etc.

This talk about my way from the state of "I have a lot of tasks, I do not have time" to a calm measured life. :)

Are you an employee who wants to know more, but you do not have enough time? 

You, as a manager, send employees to the training, but they do not use knowledge? 

Or do you think that some topic is too complicated for self-study? 

I have lived all these questions and found, it seems to me, an effective way to develop the team in just 15 minutes a day. I want to share this knowledge with you.

Quality assurance of mobile applications includes reaction tests for incoming calls, internet connection loses, screen rotations etc.

• But what tests should we hold?
• How to understand if the application behavior is ok?
• How to visualize tests?
• How often to repeat regression testing?

That's what I'm going to talk about in my speech.