Tester here, I only have to do this if the ticket is unclear / its not clear where impact can be felt by the change. I once had a project with 4 great analysts and basically never had to ask this question there.

[–] Th3D3k0y@lemmy.world 9 points 2 days ago (1 children)

We added an API endpoint so users with permission sets that allow them to access this can see the response.

Ok... What is the end point, what's the permission, is it bundled into a set by default or do I need to make one, what's the expected response, do we give an error if the permission is false or just a 500?

They always make it so vague

[–] Kualdir@feddit.nl 6 points 2 days ago (1 children)

And if one dev responds with "Just look at the swagger" to those questions I'm gonna cry

[–] Th3D3k0y@lemmy.world 3 points 2 days ago (1 children)

ID: String (required)

BUT WHAT FORMAT?!?

[–] Kualdir@feddit.nl 2 points 2 days ago

I feel this in my core bro

[–] nogooduser@lemmy.world 3 points 2 days ago (1 children)

I have worked with some excellent testers but I have also worked with a team that literally required us to write down the tests for them.

To be fair, that wasn’t their fault because they weren’t testers. They were finance people that had been seconded to testing because we didn’t have a real test team.

The current team is somewhere in between.

[–] Kualdir@feddit.nl 5 points 2 days ago

Look I don't think its bad to have people like that testing, but you'd need a test team to write the test for them or have those people specifically interested in testing the software.

I've had a project where we as testers got out most bugs during test phase, after that it went to staging and there were a few business people who always jumped on testing it there and found bugs we couldn't think of cause they just knew the business flows so well and we had to go off what our product owners said.

Leaving all testing to a non-testing team isn't gonna work