Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "testing testcase"
-
when youre working on a API and every testCase is all green plus manual testing thru Postman extension is all good..
then makes a web app use that API, authorization works as intended but the token is immedially invalid...
just..how..2 -
My project is a cloud based automated testing product. My current story is to extend a module to support multiple of a particular testcase type in one test run instead of just one. This has uncovered a rats nest of complexity because everything is designed with the assumption that there will only ever be one of these testcases.
Refactoring about 5 different classes just to get into a state where i can pass a list of testcases into a service instead of just one. Wrecking my head... -
I don't like when the tester asks me(developer) the expected result of a certain test-case.
I have built it with certain thinking and the user end might want something else?!.
The tester should check the use case and then decide or discuss it with me(developer)