QA / QA Automation

How can you build a process so that a junior starts testing, for example, the payment module, by the second day without your help?

A bug has been present in production for 2 weeks, reproduces only in 3% of users and only on Wi-Fi. The developer cannot reproduce it and says he will close the bug in 10 minutes. What actions would you take?

It is necessary to check that the UI does not break on all possible devices. The physical device park is limited. How can additional checks be run?

Let's talk about errors between the backend and clients. You are testing a mobile application, the 'Favorites' section. All test accounts have products added, but on one account, instead of products, an error placeholder 'Something went wrong' is displayed. You connect to the sniffer. All accounts receive 200 OK and JSON. What are your next steps?

Where would you like to develop?

Today is Friday, the client says that they urgently need to release the release in the evening, but regression is not ready yet. What would you do in such a situation?

Have you ever encountered an Android manifest? What is it?

Can you describe in detail how you implemented automation? Did you write the tests yourself or decide what to automate?

Have you worked with Docker?

What from the release checklist could you delegate to a junior, and what would you check yourself?

In the mobile app, QR code payment has been added. What non-functional checks can you name that are better to check first?

Disputes with a developer: he says it's not a bug, but a feature. Are you sure it's a bug? The technical specifications and mockups have no clarifications on this issue. What will you do?

Imagine a situation: you are a lead tester, you have several juniors under your supervision, and you are preparing for a release. What readiness criteria would you set?