Ranter
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
Comments
-
Yeah6916298yI am a student assistant who works as a trester. Writing down the problem report is not the most fun part. Still I rather like it to do myself, because than I can make sure that it is descriptive enough that anybody understands the problem and can test if the fix does the job.
It often happens that a problem report written by a developer is so cryptic that you have to ask the developer anyway. -
arekxv10548y@Yeah69
Yeah us devs can do that. I'm sorry for that. Sometimes there is no good way to explain a fix to a bug or feature. In my case I usually just write a simple explanation and then write for QA to come to me before testing so I can show them. Takes some time, but IMO QA should be an asset which you can use. ☺ -
Yeah6916298yI like it your way. In such cases I would not need to think that the developer assumes that I have to understand it and first try for an hour without success. I can then go to the developer right away. Unfortunately this rarely happens. @arekxv
QA: Hey I found a bug.
Me: Okay, can you log the bug and assign to me?
QA: <audible sigh> sure
undefined
following process is hard