Skillsjs, java, python, css, html, kubernetes
Joined devRant on 2/3/2020
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
And the award for the best ticket if all time goes to:
No open questions. Of you don't understand, are you really a dev?
In all seriousness, this thing was in the board for like 3 days and nobody raised any questions...11
So... I take over this one ticket to test... the ticket mentions some visual component popping up when a button is clicked. It says there is a success and a failure message. The title of the story also mentions another functionality.
I start testing and some fellow QA asks me why I'm testing in this environment. Turns out, three people are sharing one environment and three different things are deployed...
I ask the dev whats going on because I heard there are multiple people deploying stuff...
He just tells me "oh, my changes are deployed I just checked".
I tell him that it's not about that but about communication and testing one thing at the time. Then I tell him, that I wouldn't test until his stuff is the only stuff there.
Some time later he hits me up again, now with the env to himself.
I test and quickly I see, that there is only the positive message even when I make sure that the backend is not reachable. I tell the dev what I found and he tells me "oh no, it's just the implementation of the popup thing, it's just frontend for now"...
I tell him, that the ticket should say so.
No answer for like 1-2 hours. Then I get an "ok".
End of the day.
Next day I come in and the fellow QA tells me, that the dev asked him to test the ticket.
I ask him if he changed anything about the scope of the ticket, he says no...
I'm like "ok... know what... begin testing and then tell him what I already told him".
So he's testing and then tells him again to update the scope.
Later in the daily the the dev's update is besically "they won't test my ticket..."
It would have taken him like 1 fucking minute to update the ticket...
The whole QA team was always trying to being helpful and even when the tickets where sometimes not 100% clear we always made it work... but now we are more and more going towards "MR does not meet ticketdescription, fix it" and "I don't care if its just a small thing... fix it and then come back to me"...
Seriously frustrating some times...2
I don't get why certain people always complain about the OS they have to use at work... I get, that as a person who really uses aspects of the OS like a sysadmin or something like that, has valid points... but no... as a projectmanager or productmanager, whos tools are all browserbased... "in Windows I know where all the things are..." is not a valid excuse to hate on the OS...
What do you want to do? Change system settings everyday? Use PowerShell to create your Jira tickets?8
My biggest concern is, that I won't be able to get free fruits and drinks while working. Oh yeah also my cat who will definitely want to lay on my laptop and or keyboard...
But I'm so not gonna wear pants to the meetings!5
Mocha or Tape (both with supertest)? For Backend testing. Api, graphql, that shit.
What would you prefer and why?4
Devs from company that develop/modify a service for us say "you can test on <env>".
Description of how to test: scattered across multiple tickets, comments and slack messages in multiple conversations...
Oh and please... Could you not directly merge 20+ branches directly to the dev branch without testing...
So much going wrong with this project... Already a month overdue on the first release...
Today someone took a shit and didn't flush...
Normally you have your typical candidates, who are pissing standing in the stalls although there are free urinals, people who don't wash their hands after pissing or just splash like 3 fingers with water. Even not washing hands after taking a dump, which is pretty disgusting... But today? Some dude in the stall next to me took a shit, wiped his butt... and went away... No flushing no washing hands... Wtf is wrong with people?7
>Get password vom dev.
>Try to connect to MongoDB.
>Had some changes in how to connect because of Kubernetes and stuff.
>Always get authentication error.
>copy password again
>stop and restart portforwarding
>wait almost 1,5h (was lunchtime) for DevOps guy
>sit next to him and ask for help
>he unhides the password and deletes two spaces...
Dev: can you please merge this to master?
QA: wait... Who tested this?
Dev: oh it works, it was tested...
QA: by qa?
Dev: ... <Dev2> tested (sitting right next to him)
Working with external teams on this new project involving pretty sensitive stuff like bank transactions.
Talking about user flow and how to handle authentication, like 2-factor and stuff.
Newish guy on external team (though experienced) says they have a proposal.
... like "What was you first car" security questions...
awkward silence in room...8