#qa
Posts tagged #qa on Dynamo Geeks: 14 posts from the community, most useful first.
Posts tagged #qa
pujo leave approved. 5 days. laptop staying in the office…
pujo leave approved. 5 days. laptop staying in the office drawer. handover doc: "if prod breaks, ask the dev who said works on my machine. he is on call. he does not know yet" 🐟 শুভ পুজো সবাইকে
5 cosas que hacen tus tests de Playwright flaky (y cómo arreglarlas sin poner sleep)
Qué onda raza. Después del post del martes maldito (el test que solo fallaba los martes, búsquenlo) varios me preguntaron por DM cómo le hacemos para mantener 900 tests e2e sin volvernos locos. Aquí va lo que neta nos funcionó. Nada de magia, pura chamba. 1. Deja de usar waitForTimeout Si tienes await page.waitForTimeout(3000) , ya perdiste. En tu máquina 3 segundos sobran, en CI con 2 CPUs no alcanzan. Usa las…
light mode or dark mode? QA wants to know who to blame
QA when I say "small fix, no need to test"
Flaky test bingo: 12 squares I have seen in real life (with fixes)
Hello everyone) I collect flaky test causes like other people collect stamps. Here is my bingo card from the last 4 years. All real, all happened to me or my team. If you get a full row in one sprint, you deserve a day off. Row 1: Time 1. Test uses real current time. Fails at midnight, at end of month, on DST change. Fix: freeze time. In Playwright page.clock.setFixedTime() , in Jest or Vitest fake timers with a…
I blocked the release on Friday and whole team look at me like I kill their cat
Story time 😅. Friday 4pm, release for our Australian client at 5pm. Everything is green. Dev team already ordered bubble tea to celebrate. I do my last check on real device, the old Android phone that nobody want to use. Checkout button not work. Tap, nothing happen. On iPhone fine, on Chrome desktop fine, on the dev laptop of course fine. "Works on my machine" 3 times in 10 minutes. I write in channel: "Release…
The test that only failed on Tuesdays (yes, only Tuesdays)
ok this one took me 3 weeks and I need to share it because neta I still don't believe it. Context: I do QA automation for a US insurance app, Playwright + TypeScript, around 900 e2e tests that run every night on CI at 2am Central. We had one test, renew policy shows correct premium , that started failing. Not every night. Some nights. Rerun, it pass. Classic flaky, we put it on the quarantine list and move on. Then…
When a test fail only in CI and pass on your laptop, what you do first? (be honest 😅)
Dev: cannot reproduce Me: send video, steps, console log…
Dev: cannot reproduce Me: send video, steps, console log, HAR file, browser version, device model, screen size, battery percentage, moon phase Dev: cannot reproduce on my machine Me: so I send you my machine?? 🐞😅
dev: "en mi máquina sí jala" yo: "perfecto wey, entonces…
dev: "en mi máquina sí jala" yo: "perfecto wey, entonces empaqueta tu máquina y la mandamos a producción" dev: 🤨 yo: "ahorita le levanto el ticket" 🤣
kolkata derby er din office: devs: 0 commits QA: 0 bugs…
kolkata derby er din office: devs: 0 commits QA: 0 bugs raised PM: "team velocity is very stable" manager wearing a red and gold scarf under the formal shirt, we all saw it জয় ইস্টবেঙ্গল 🔴🟡
Bug of the week: date field only broken for Japanese users (and it was not timezone)
Hello everyone, first post here 🐞. I am QA in Hanoi, we test web app for one Japanese client and one Australian client. This week I found a bug that is so funny I want to share. Symptom: Japanese client say "birthday field always say Invalid date". Australian client no problem. Dev team test it, no problem. Of course "cannot reproduce" 😅 First everybody think timezone, because it is always timezone. Not timezone.…
new intern joined today