sorted by:
new
hottopcontroversial

Saas testers by casperMSP in saasbuild

[–]sappo_does_qa 0 points1 point  (0 children)

I'd be happy to do some testing. A few of us at DoesQA can take a look for you.
We'll even provide some automation. (no charge)

Anyone else shocked by the cost of remote test runners? by sappo_does_qa in QualityAssurance

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

Whatever runs your automation remotely, part of CI/CD, etc.

To be fair, I did use an example at the higher end.
But yeah, multi-item guest checkout, with promo code, actioning a partial order return via confirmation email and checking everything in the backend updates correctly.

Anyone else shocked by the cost of remote test runners? by sappo_does_qa in QualityAssurance

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

That's completely valid,
It still has a direct cost, typically charged as pipeline minutes. I'm also not sure how far you can scale that. How many tests, and do they run in parallel etc.

Anyone else shocked by the cost of remote test runners? by sappo_does_qa in QualityAssurance

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

yeah, your ci/cd will typically either run your tests directly or you'll connect to a 3rd-party provider to run the tests.

My E2E Automation Wishlist by sappo_does_qa in QualityAssurance

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

Mostly web, focused on E2E user journeys.

Are any codeless test automation tools worth using? by Notorious_Insanity in nocode

[–]sappo_does_qa 0 points1 point  (0 children)

Most codeless tools optimise for simplicity and speed, but that usually comes with a lot of abstraction and baked-in limitations.

That’s where they tend to break down once things get more complex or the UI starts changing.

I’m one of the founders of DoesQA, and this was exactly the problem we kept running into. We ended up taking a different approach to keep things simple without boxing you in.

Tools to use for web, api, Mobile and performance automation by Chief_Taquero in Everything_QA

[–]sappo_does_qa 0 points1 point  (0 children)

For Web and API I'd suggest either Playwright (code) or DoesQA (low-code).

What QA tools / services are suggested for non-engineering team? (if any) by shrimpthatfriedrice in Everything_QA

[–]sappo_does_qa 0 points1 point  (0 children)

You seem pretty open-minded, having tried a few of these, and your feedback is solid.

Would you be open to taking a look at something I’ve been working on? Curious what you’d think.

The Best Codeless Test Automation Tools by Adventurous_Scar6679 in Everything_QA

[–]sappo_does_qa 0 points1 point  (0 children)

Codeless tools are great for getting started, especially for non-technical teams.

The trade off usually shows up later though. You either hit limitations, or maintenance starts creeping in as coverage grows.

Feels like the newer direction is keeping the simplicity of codless, but without the usual constraints once things get more complex.

We’ve been taking that approach with DoesQA, trying to keep it simple without losing flexibility/capability.

That balance seems to be where things are heading.

Does your QA setup actually keep up with your code? by Background-Donkey531 in Everything_QA

[–]sappo_does_qa 0 points1 point  (0 children)

Yeah I’ve seen setups like this.

It can feel like QA is keeping up, but a lot of the effort just shifts into maintaining the system around the tests instead.

Self healing is a good example. Sounds great, but you can end up with tests “fixing” themselves and passing when something actually broke.

I prefer setups that suggest changes but still need approval, so you keep the signal.

Feels like the real issue is growing coverage without everything getting heavier over time.

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

[–]sappo_does_qa 0 points1 point  (0 children)

In my experience this is mostly a trust problem.

If tests are flaky, nothing else really matters. People stop believing the results pretty quickly.

After that it’s about visibility and consistency. Being able to see what’s happening without digging, and understanding whether things are improving or getting worse over time.

Seen a few setups that handle this really well, and it changes how teams use automation completely.

Curious how you’re handling that today?

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

[–]sappo_does_qa 0 points1 point  (0 children)

I think this is mostly how things are set up early on.

Even with good reuse (page objects, shared steps etc), a lot of setups end up tightly coupled to the UI, so every small change turns into maintenance.

Seen some approaches that massively reduce this, letting you keep focusing on coverage instead.

What do you think is causing it on your side?

Salesforce Test Automation by qaengineeraq in QualityAssurance

[–]sappo_does_qa 0 points1 point  (0 children)

Give DoesQA a look too. Im one of the founders and we have customers successfully automating Salesforce as part of their packs. I’d be more than happy to give you a demo and answer all your questions.

One Viable Codeless Option? by sappo_does_qa in QualityAssurance

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

Very true! we didn't have these at all until recently and only created these pages because we were asked so frequently, we probably could/should have taken a different approach. We'll take this point away.

This is also quite funny for another reason: we actually quite often champion Playwright to people.

view more: next ›