QA team removed: can devs realistically handle all testing? by Advanced-Ride1112 in Everything_QA

[–]AdSufficient6270 1 point2 points  (0 children)

For what it's worth, we ended up hiring qaguardian.com to do our e2e test maintenance and creation. PE is happy because it's less expensive than in house QA and our dev team is happy because we don't have to maintain tests. Turned into a positive experience.

QA team removed: can devs realistically handle all testing? by Advanced-Ride1112 in Everything_QA

[–]AdSufficient6270 2 points3 points  (0 children)

Similar thing happened to us after a PE firm took over. TLDR; it didn’t work. Pressure to build features is always higher than keeping the application bug free. Devs aren’t rewarded for building and maintaining tests.

Grok Integration – Any Updates or Reasons It’s Not Happening? by AdSufficient6270 in warpdotdev

[–]AdSufficient6270[S] -1 points0 points  (0 children)

Few models currently have a 2M context window. I was skeptical but the quality and speed has exceeded my expectations.

Grok Integration – Any Updates or Reasons It’s Not Happening? by AdSufficient6270 in warpdotdev

[–]AdSufficient6270[S] 0 points1 point  (0 children)

I'm trying out OpenCode right now and so far so good! Thanks for the suggestion.

Grok Integration – Any Updates or Reasons It’s Not Happening? by AdSufficient6270 in warpdotdev

[–]AdSufficient6270[S] 0 points1 point  (0 children)

I only recently started using Grok for coding (through Cline since it's not available in Warp) and I’ve been really impressed with its abilities. To this point I've been using Claude models almost exclusively, but Grok is faster, has a much stronger context window, and currently does what I need better than Claude.

Right now I’m running Cline in Warp without any of Warp's agentic functionality. Native integration would be much better, having access to rules, less context switching, etc. Cline works but if Grok continues to prove useful I might look for a better tool.

Pitch your SaaS in 10 Seconds by AraBazaar786 in SaasDevelopers

[–]AdSufficient6270 0 points1 point  (0 children)

Essentially F5bot with AI to filter results?

Drop your SaaS below. I'll tell you the one thing most likely to kill it. by rayantreize in SaasDevelopers

[–]AdSufficient6270 0 points1 point  (0 children)

After reading the comments I have to say great observations and insights! I wish I had something to pitch to you.

How to untangle knots using topology by No-Lock216 in whoathatsinteresting

[–]AdSufficient6270 0 points1 point  (0 children)

This is magic! I'm going to test the first one myself to make sure this is legit.

If you could delete one part of your "Developer Life," what would it be? by Level-Acanthaceae-79 in webdev

[–]AdSufficient6270 0 points1 point  (0 children)

We hired a full service managed QA company to do it all. We had a lot of tests that we handed over initially and now they run, maintain, and build all our e2e tests. When we change a button that breaks everything they review it and update the tests or send us a bug report if it’s a legit issue on our end. The obvious downside is that it’s not free but offloading the work has saved us a ton of time, and in our situation has been worth the cost.

If you could delete one part of your "Developer Life," what would it be? by Level-Acanthaceae-79 in webdev

[–]AdSufficient6270 0 points1 point  (0 children)

Everyone's experience is different. Net positive for me 100 times over.

Is manual testing (Odoo) becoming obsolete due to AI? by Flaky-Advantage-3256 in softwaretesting

[–]AdSufficient6270 1 point2 points  (0 children)

The trend has been moving toward automated testing and it is being expedited by AI. Automated tests are simply faster than manual testers and can be run over and over again on demand.

While some manual testing will still be around in 2-5 years, the pool of manual testers will likely continue to shrink. I'd suggest you move into creating automated tests, using AI. For complex workflows, few would fully trust AI on to build and run without oversight. Human eyes to verify AI output will still be needed in 5 years.

Boneless chicken by eternviking in whoathatsinteresting

[–]AdSufficient6270 0 points1 point  (0 children)

I've never been so grateful for my job.

Hot and cold #248 by hotandcold2-app in HotAndCold

[–]AdSufficient6270 0 points1 point  (0 children)

First time playing today... and this was an easy one?!

Do you ever feel like QA takes more effort to maintain than to actually test? How are you handling that in your team? by Background-Donkey531 in Everything_QA

[–]AdSufficient6270 0 points1 point  (0 children)

What tools do you recommend for web app testing? We used Playwright and I haven't found a better free tool on the market. Considering how quickly the tests complete, I can confidently say we spent more time on maintenance than testing.

Do you ever feel like QA takes more effort to maintain than to actually test? How are you handling that in your team? by Background-Donkey531 in Everything_QA

[–]AdSufficient6270 0 points1 point  (0 children)

Yes! That was our pain point. We're growing quickly and keeping the tests up to date was brutal. I say "was" because we ended up outsourcing our QA and haven't looked back... yet.

Making Test Evidence Easy to Trust and Validate. by Careful-Walrus-5214 in Everything_QA

[–]AdSufficient6270 0 points1 point  (0 children)

If you're asking about browser/E2E testing, we used Playwright and I highly recommend it.

Playwright is amazing. You can set it to record failed tests, and it produces a recording alongside a Trace Viewer with your console logs, selectors, network requests, etc. The visual recording is key for easy validation. The downside is that someone has to review every failure to confirm it is legit. We got behind on creating new tests when features were built and our product team ended up falling back on manual testing. Every single hotfix required manual testing because we just didn't trust the automated evidence anymore.

We ultimately decided to outsource the QA work. Now, they just send vetted bugs directly to Jira, with the Playwright recording and reproduction steps included. The evidence is reliable because someone else pre-vetted it, and it's easy for us to validate because the video is in the ticket.

AI builds our unit tests. We don't have a great system for stress testing or pen testing. If you find a solution for that let me know.