Телеграм канал «QA Community»

🚀 Tactical Forking in Practice: An Approach to Microservices Migration

Thinking about moving from a monolith to microservices but worried about cost, time, and risks? Join our meetup on August 26 to learn how tactical forking can help evolve your system gradually without a complete rebuild.

🔹 Why migration is difficult when modularity is lacking
🔹 When tactical forking makes sense
🔹 How to implement it without disrupting development
🔹 Its impact on architecture, processes, and teams

🎙 Speaker: Mohamed Taman — Solutions Architect at Andersen, Java Champion, JCP member, TOGAF-certified architect, and Azure-certified professional with 22+ years of experience.

💡 For Architects, Tech Leads, Java & Backend Developers, and anyone involved in software modernization.

📅 August 26
⏰ 17:30 CEST
🗣 English
💻 Online

🔗 Register here

🐹 Go developers, this one's for you!

gRPC in Production: What They Don't Tell You in the Getting Started Guide

Production gRPC comes with challenges that tutorials rarely cover. Join Dmitry Kudryashov (Software Engineer at Andersen) to learn how gRPC really works in production, the most common pitfalls, and practical tips to avoid them.

✨ gRPC for microservices
⚡️ What happens during an RPC call
🛠 Production pitfalls & best practices
📋 Practical production checklist

🎟 Register here
⏰ 19:00 (Tbilisi, GMT+4) / 17:00 (CEST)
🗣 Russian
📍 Offline (Andersen Tbilisi) + Online

🚀 Selenium vs Playwright in Python: what to choose?
Which tool fits your project better?

At this meetup, we’ll compare both frameworks in practice and discuss:
• why tests become flaky
• Selenium vs Playwright: key differences
• how auto-waiting improves stability
• speed, convenience, and real project experience
• how to choose the right tool

🎤 Speaker: Anton Semenchenko — CTO at Alfa Algorithm, Senior Lecturer at BSU, founder of COMAQA, 20+ years in software development and test automation.

🧠 Who should attend: QA engineers, automation beginners, QA Leads, and Engineering Managers.

📅 19:00 (Minsk, GMT+3) / 18:00 (CEST)
🗣 Language: Russian
📍 Offline: Andersen office (Minsk)
💻 Online: Streaming link will be sent after registration.

🎟 Register here

📱 QA Community Linkedin

Schrödinger's cat is the reason your CI is flaky

#QAMemes #SoftwareTesting #BugOfTheDay #TestingTips

“No second date” is temporary, understanding NULL is forever


#BugHunter #TesterLife #QAHumor #ITCareer #QArelatable

A green CI/CD pipeline doesn't mean your system is production-ready

All tests can pass while users are stuck on a loading screen.

Most production incidents aren't caused by bugs in your code - they happen when the environment fails:
• slow databases
• flaky networks
• third-party API outages

That's why Chaos Engineering matters.

Instead of asking "Does it work?", it asks:
"What happens if a critical service fails right now?"

Companies like Netflix even created Chaos Monkey to randomly terminate production instances and continuously verify system resilience.

Because users don't care if your pipeline is green - they care that the app still works when everything around it doesn't.

How does your team test resilience?

Have you ever been there?