lol, I can't keep up with my own agent's PRs..
Login to reply
Replies (8)
real QA and release management will become the hottest 'dev job' in 2027. devs that always treated QA and releasing as beneath them, in shambles. 😁
Until agents can run and walk through apps to test their own features..
those kinds of tests are so fragile, human will retain champion of this..
They can use AI for a lot of it but at the end of the day a human will catch way more bugs, and triage them, and then send the proper data upstream to be fixed. It's underated skillz that will be ressurected and adopted by devs that will not want to be left behind. (imagine game development)
No more 'elite devs that didn't even bother compiling' throwing code over the fence and then disappearing when it deploys and pretending they can't find or read a logfile 😂
I think agentic bug finding is easy and needed. But I agree that the most important thing we do is to evaluate if the feature and UI makes sense. I am discarding a lot of things the Claude does not because it is wrong or not working, but because it's doesn't make sense to the user.
I believe that's what he does then the AI is trying to create merge PRs. View the repo shows lots of claude/ branches
What's your review process?
Build e2e test harness with maestro and emulator in addition to unit tests. Set acceptance criteria and demand full e2e build and test with screenshots of all changes.
Also: I am in the same spot.
having been an integration test jockey, yes what you are missing is the continuity between changes and the test harnessing. im sure it will get there, but hey, dev already solved, test not so much. speaks for itself.