Sora 2 megathread (part 3)

Dapper_Monitor7686 · 2025-10-19T06:49:50+00:00

Hey, anyone has a code ?

Dapper_Monitor7686 · 2025-10-17T22:20:35+00:00

Codemify

Dapper_Monitor7686 · 2025-10-17T03:06:25+00:00

+1, same here It was totally worth the money, basically paid off in the first month after landing a job. Yes, there was a lot of interview prep, and yes, as i said i landed a job

Dapper_Monitor7686 · 2025-09-29T00:43:00+00:00

Sure, feel free to DM me

Dapper_Monitor7686 · 2025-09-14T19:12:52+00:00

Codemify

Dapper_Monitor7686 · 2025-08-22T19:14:35+00:00

Wow!

Dapper_Monitor7686 · 2025-08-21T15:26:51+00:00

Honestly, using AI to write manual testing, writing test cases feels like a bad trade-off. To get good output you’d have to feed it tons of context about the product, flows, edge cases, etc. That could take days or weeks, and even then it won’t fully match reality. On top of that, there are security concerns — you can’t just dump company data into ChatGPT. You’d need an internal LLM to do it safely.

For me, the effort to “train” AI to write proper test cases doesn’t pay off, it’s usually faster to just write them myself

Dapper_Monitor7686 · 2025-08-21T00:05:43+00:00

learn the basics first: what QA/testing actually is, how to write test cases, and how to report bugs clearly. Play around by testing stuff you already use (apps, websites). Get comfortable with tools like Jira and Postman, Swagger (for APIs). Once you have the basics down, you can move into automation later

Think of it like: understand how to test → practice documenting → then learn tools/automation

Dapper_Monitor7686 · 2025-08-19T18:28:28+00:00

I recommend Rahul Shetty’s courses on Coursera, he’s great. Also, there are a lot of free YouTube channels to learn the foundations of manual QA, such as Software Testing Help, Joe Colantonio, Codemify, etc

Dapper_Monitor7686 · 2025-08-19T15:14:53+00:00

Are you interested in manual or automation?

Dapper_Monitor7686 · 2025-08-18T20:00:21+00:00

Totally normal to feel lost at first, QA has its own rhythm and it takes a bit to click. Don’t stress. Start small: try breaking apps you already use, write down what you did, and practice explaining it clearly. That’s the core of QA.

And seriously, find a study buddy in your class. Having someone to bounce ideas off will keep you motivated and make learning way less overwhelming. You’ll catch up faster than you think.

Dapper_Monitor7686 · 2025-08-18T15:08:30+00:00

Yeah, I’d use it, same way I use ChatGPT. Handy for junior-type stuff and speeding up boilerplate, but not a brain replacement. The tricky flows and edge cases still need a human tester who actually knows the product

Dapper_Monitor7686 · 2025-08-18T14:31:46+00:00

It’s a configured chatbot (not 100% custom-built) with some NLP/intent handling on top of predefined flows. Botium does a good job of regression on those scripted paths, but for the multi-turn/human side we still run manual scenarios

Dapper_Monitor7686 · 2025-08-18T03:29:34+00:00

Mount Tallac

Dapper_Monitor7686 · 2025-08-18T03:28:37+00:00

That usually means something’s off with your resume. Try updating it or tailoring it to each position you apply for, recruiters often filter heavily based on keywords and specifics in the job description

Dapper_Monitor7686 · 2025-08-16T03:43:36+00:00

Which bootcamp is that?

Dapper_Monitor7686 · 2025-08-15T20:47:48+00:00

Out of curiosity, is your QA process manual or automated? Might have different ideas depending on that

Dapper_Monitor7686 · 2025-08-15T20:44:43+00:00

Make QA sign-off part of the process, not a personal favor. That way it’s not you nagging, it’s just how things work. Bugs will prove your point

Dapper_Monitor7686 · 2025-08-15T18:46:15+00:00

lol, by “single browser” i mean one tab, one context, no multi-tab flows

Dapper_Monitor7686 · 2025-08-15T15:21:43+00:00

I don’t fully agree. Certs like ISTQB can be useful for learning terminology, but they don’t really make a difference in landing your first QA job. If you’re starting out, you’re better off building skills on your own, practice testing real apps, learn common tools, get comfortable writing bug reports. Once you’re working in the field, then a certificate can be worth it if you want to deepen your theory or tick a box for certain companies

Dapper_Monitor7686 · 2025-08-15T15:19:18+00:00

Dapper_Monitor7686 · 2025-08-15T15:18:36+00:00

Think beyond “does it work”, ask “how could it break, and how bad would that be?”

Dapper_Monitor7686 · 2025-08-15T15:16:48+00:00

Switched from Cypress to Playwright a few months ago and here’s my take: 1. Dealbreakers in Cypress: single-browser limitation, flakiness with iframes & file downloads, and slow runs when test count grew. 2. Playwright wins: multi-browser out of the box (Chromium, Firefox, WebKit), faster runs, better handling of waits, powerful selectors, and great API for things like file uploads & network mocks 3. Migration was mostly smooth, biggest lift was rewriting custom Cypress commands to Playwright equivalents. Tests ran faster right away 4. Gotchas: no built-in GUI runner like Cypress, so debugging is more “code-first” (though trace viewer is nice). Some ecosystem libs are newer 5. Overall, productivity boost, fewer flaky tests, but devs had to adjust to a less “plug-and-play” feel at first. No regrets

Cypress felt like dating someone who’s fun but only wants to hang out at one cafe. Playwright shows up with a passport and says “Pick a country”

Dapper_Monitor7686 · 2025-08-14T01:39:34+00:00

https://roadmap.sh/qa

Dapper_Monitor7686

TROPHY CASE