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
-
My GF, an iOS QA, went for an interview with a large enterprise and was rejected.
Interviewer: Your current application is hybrid or native?
GF: Native, because it is written in swift using native iOS SDK.
Interviewer: Does it use internet?
GF: Yes.
Interviewer: It is a hybrid application if it uses internet. You know nothing about your projects. You are rejected.
GF: 😯21 -
QA: There is a bug in your program, it doesn't work !
DEV: What? It is working on my machine, let me show you *opens app*
QA: Well, then I will tell our clients to use your machine every time they want the app
DEV: ...7 -
>22 year old college student
>Apply for a QA internship
>Interview goes well,they see I have plenty of experience and doubt it's real
>Hard questions are thrown
>Answer them and they admit the position is for manual testing
I honestly don't care I need the money, plus manual testing doesn't usually strain me.
>A week goes by
>A month goes by
>Call them
>...Sorry we were looking for someone with less technical and dev experience.
My fucking face when I don't have a title, still overqualified, fighting with WordPress devs on freelancer.
14 -
>we increased new releases to once a day
> wow, how'd you do that?
> fired the QA team
Credit - @iamdevloper✓3 -
My gf was a QA. I told her to read my last devrant story about our colleague from the previous company.
Her response was "you misspelled 'taught' twice".
😢6 -
Me, doing QA
PM: "stop submitting bug reports about screen size, we're only supporting one resolution for now"
Me: *What do you mean you're only supporting one resolution it's a website and it breaks on screens <1400 px tall*
*Sigh*
"okay, what resolution?"
PM: "No one knows"
Me: *dies*2 -
Just reduced 900 lines of horrible code into 106 lines of less horrible code..
QA: do those 106loc really do what the 900loc did ?
Me: yes
QA: really?
Me: yes
QA: are you sure?
Me: NO. I was lying. Maybe it does. Maybe it doesn't. Maybe you should run it and find out.
QA: *immediately releases for prod*3 -
Our parent company is pushing a new zero defect policy for code that gets shipped.
The next day they announced they are firing our QA team.
WTF?!14 -
me: Just to be clear, we're only supporting chrome?
boss: Yes.
* few days later *
QA: I have a lot of bugs to report, the bosses asked me to test the app in all browsers10 -
QA: Please Look at this Defect.
Me: Okay not a problem!
QA: Thanks
Me: <Starts to look at Defect>
QA: 2 mins later. Do you have an ETA on when it will be fixed?
Me: Not yet, I'm still looking at it.
QA: Do you know what time it can be fixed? I have a deadline.
Me: I don't know what's wrong yet, I can't tell you when it will be fixed if I don't know what's wrong.
QA: Okay. Update Me.
Me: Opens Dev Rant.5 -
QA: You need to write a test script for your new web app before it can go live
Me: ok, I'll write some tests in PHP unit and automate the tests.
QA: Oh, can you do that? We just normally write a list in excel then go through each line and write pass or fail at the end.
Me: yeah, good one.
QA: Umm, I'm not joking.
Queue awkward silence...4 -
Dev gets hold of me, says my service is down in QA. Works if he hits it locally, works via Postman, but via the QA app server it gives a 401.
I’m like, look, if it works everywhere else, there’s something wrong on your side in QA.
He insists, no, I must help him, and begins CCing all the managers telling them this system has been down for days.
So I eventually climb into his system, check the credentials they’re using in the QA environment, and sure enough, the password is wrong.6 -
QA: When I open the app I get this strange error message that includes "No data connection could be established" near the start of it.
Me: I'll clean up how thats displayed, but the error means your phone doesn't have internet connection.
QA: No that can't be it, I do.
Me: You screenshot shows no WiFi or 3g / 4g symbols.
QA: No those are never there, please investigate.
Me: I have investigated and found that every other one of your screenshots had a WiFi or a 3g symbol. Example: <link>. Please check your connection and try again, i'll clean up the error display.
PM: Oh i've had an issue something like this before. We really need to show users an error screen. We can't just leave them on this screen with no error message at all.
Me: ... we have an error, thats what QA is complaining about, its not loading the text and displaying the error object.
Anyone else want to not pay attention and complain about something else that doesn't make sense? ... no? ... ok good, back to work then7 -
QA: did you test the app first?
Dev: Yes, I test all my code all the time.
*QA crashes the app within first 5 seconds.*4 -
What I would define as a critical bug:
- System doesn't respond
- Functionality is broken
- Client data is all wrong
What QA defines as a critical bug:
- Typo on this page in the QA environment2 -
Manager: Hey Dev I need to do QA on this PR.
Dev: That PR is not finished yet
Manager: Well do QA now anyway, that way when it is finished it can be merged in right away since QA has already been done on it. It’s a project management technique called “fast-tracking” and it improves efficiency.
Dev: …9 -
"IT BROKEN!", the QA tester spoke in unintelligible broken English.
The developer asked for more details.
Then the QA person attempted to explain the problem in a surge of verbal diarrhea and horrible English.
Why do we hire people who don't speak the language of the development team as our QA people? I have nothing against devs and qa guys from India...but it makes my job really difficult when I can't even begin to understand what you are telling me, or even worse...you just tell me "IT BROKEN!" and don't give me a single bit of useful information on how to reproduce the error.
There was this wonderful QA person I used to work with. Her name was Ranjana. She was a beautiful Indian girl with two children, and the best QA person I ever worked with. She took screenshots, grabbed logs, and gave steps to reproduce everything she found. And then one day at stand up we were told she had died. And since then...there has been no one who has ever come close to her level of excellence.7 -
Got really pissed off writing a stored procedure the other day because the reason behind it is absolute bullshit.
Gave sproc to QA for peer review before release.
QA: why are the variables called @FuckThisShit and @ThisIsBollocks?
Whoops, guess I was more angry than I thought 😂3 -
Qa: do you think this looks like the provided designs?
Me: yes I do...?
Qa: well it doesn't, please check
Me: well I hate playing find the difference, how about you fucking tell me what exactly is wrong?5 -
Me at QA, talking about a nasty bug I found in legacy code.
QA: what was the root cause?
Me: pos code.
QA: pos?!
Me: piece o' shit.
QA: ...1 -
Me: *opens up a test script*
> only http response code is checked
Me: hey, coleague from qa, why didn't you also write response body checks?
Col: I had then implemented but removed them later.
Me: ?? Why??
Col: because tests were failing
Crickets: *chirp chirp* .... *awkward pause* [in high pitched crickety voice] what the fuck?!?!3 -
when I already deployed the feature, but QA and product owner just started to talk about acceptance criteria
-
Back in college.
We had this course in which we gathered in teams and worked the whole semester for another teacher building a product. We had roles, like QA, devs, PM...all the works.
I was PM and during our first presentation of the product to our teacher and the client we showed the work of our first month of work. At the end, our teacher asked our QA, who have been silent the whole project and hadn't answered my mails asking for tests, if he had found any problems. "Oh, yes. The whole site is broken. I can easily break throught it"
The faces of the rest of the group showed a level of surprise that made the teacher ask if he had informed us: "No..."
Our client, another SE teacher, started to laugh and that was that.
It was awful3 -
One of my QA friends told me today,
" If I wanna screw you up, I will just have to delete a semicolon in your code, hahahhaahhaha ". <for real>
There are two problems here
1. He's not familiar with the concept of an IDE
2. I use Python
Stop making fucking " ; " jokes in early 2019 >_<
:P
#No hard feeling to the QAs out there9 -
How was your day at work?
Dev: - I managed to break the whole thing, so s**t! 😭
QA: - I managed to break the whole thing, so productive! 😎
3 -
Im going to fucking murder the QA team if they don't stop sender bullshit issues!
QA: hey dev, there is an error with attached files.
Me: okay what's the issue?
QA: it's just a random file that gets attached. Can you fix it by the end of the sprint(tomorrow)?
Me: I need to investigate it a bit before I can tell you how long it will take, how can I reproduce it?
QA: idk, it was just there.
*several hours of testing later*
Me: I've tried to cause the 'issue' on my local server, the test server and the live server. But I haven't seen it and I have no clue what could cause it.
*30min. before I go home*
QA: dev you have to fix it before you go home! Because we have some other important issues you have to fix tomorrow!
FUCK YOU AND YOUR IMAGINARY ISSUES I'M GOING HOME1 -
QA : There is a bug, come at my desk now !
Me : I'm busy on some feature, can you make an issue on Jira I will fix it later.
QA : NO! It's a major issue
Me : Ok... I come.
* 3 hours later *
QA : I just created you the Jira you asked
Me : I told you, the bug is already fixed since 2 hours
QA : yeah but I will not test it until you mark the issue as done on Jira
.... Are you kidding me ??? So you interrupted me in my work two times for one stupid issue...4 -
During QA for a huge project when our dev team was confident of the stability of the project, We started introducing small bugs, QA team use to raise bugs in Jira, we marked them as not reproducible.
Frustrated QA started coming to our cubes - at this point dev team worked in a perfect coordination like a man to man marking in hockey. While one dev asked QA guy to reproduce the bug in front of him while the other dev has already fixed it.
Continued for a couple of days till our team lead was satisfied with the revenge. -
Our parent company nixed our entire QA team last year and now they wondering why our product releases are so unstable lately.
Who needs QA anyways. Their solution is to just stop writing code with bugs in it.5 -
Normally I'm both the dev and QA... Today I was the dev, QA and the user... Of course, I'm paid only as a dev... But I'm blamed as all three... Ffs I can't do this anymore 😞2
-
You don’t appreciate how large a project really is until you have to write tests cases for QA, to cover most work flows.
God this is mind numbing, only half way there... I think 😰3 -
Two of them, both are not very extrem.
Positive one first:
Meetings were usually not dead serious (unless there was a problem), everyone just joked around a little, made their actual points and got back to work.
Now the other one:
A client's QA staff commented "this bug is still occuring" on 5 tickets, without checking if they ever deployed the new release candidate.
They didn't deploy the new RC, so of course, the bugs couldn't have been fixed on their side.2 -
QA: When I start the onboarding process, kill the app and reopen it, I return to where I left off with no way to go back to the previous screen.
Me: Please click the back button in the top left corner5 -
Finally got around to updating the vanillia sleep screen to something more QA work flow base.
http:///www.monkeyuser.com/2018/... for source of image
-
Just closed a TOP PRIORITY ticket with "as designed"..
After a 1 minute talk with the developer who wrote this code, I found it is actually deliberate..
So I just closed the ticket..
but what really bothers me is:
That developer, is sitting right next to the QA.
HE IS SITTING RIGHT THERE..
We are a small startup company, everyone are sitting around the same table..
communicate much?1 -
We have this lovely little old lady who works in QA and whenever she finds a bug she goes across the office to the developers desk and taps them on the shoulder and spends like 15 minutes explaining and showing the bug...
This is infuriating as you lose all concentration on what you are working on and wastes so much time... But I can't bring myself to tell her to stop just can't find kind enough words. She's a lovely person and means well but it seems her world runs a lot slower than everyone else's.1 -
I solved a big problem today. It made me feel fuckng amazing. I like my job.
P.S. I'm a QA Engineer3 -
I am pretty decent developer but ended up in Quality assurance :/ it hurts me when people are having awesome discussions about coding amd I am performing dumb tests.7
-
Major project to be released. Dev environment still has defects, still moving forward to QA.
#PrayForQA1 -
Me: Im testing a new feature that is not on production yet for 30m and can not make it work. (I asked the developer for any idea why is not working)
Dev: i just tested, works fine.
Me: i just tested again with no luck. I’m i missing anything?
Dev: (Developer comes to my desk). Lets see what you doing wrong here. (After 5seconds). You have been redirected to the production site and you've been testing there all this time.
Me: 😩1 -
It's Friday morning, I haven't had my coffee yet and already stumbled upon 2 bugs in staging. How did QA miss this on development?
Oh wait, we don't have QA!2 -
Always love seeing massive companies fail in simple trivial things like these. Just tells me they don't have proper QA.
5 -
Team: * hands over release to QA
QA: Release broken. It doesn't load any entries from the test system.
Me: Not possible. It works perfectly fine in our environment and we haven't touched that logic in weeks.
A couple of days later...
QA: It seems that we accidentally deleted all the entries from our environment. We'll apply a backup.
Team, clients, air wasted to keep these people alive:
5 -
DEI QA: “For step 2 should the checkbox be checked? Or uncheck ?”
… Step 2 of my testing steps reads: “Check it [the checkbox], save it, reload it. The box should still be checked. Repeat to uncheck it, just to be pedantic, then leave it off so we can test the existing behavior.”
🤦🏻♀️
DEI QA: “The payment_method_identifier will be in api callback logs if `Return payment method identifier in auth/confirmation callbacks` is checked?”
🤦🏻♀️
Me: it does what it says on the tin.
DEI QA: “BTW its a `tin`.”
DEI QA: “In Canada its `Taxpayer Identification Number`”
🤦🏻♀️ -
A while back we had some time sensitive work I was doing in overtime, the work was purely functional and the front end had not yet been done. It went to QA to test the functionality and the only feedback I got was UX oriented.
I tried to explain on 3 occasions that the looks was not important in the slightest at this stage, and just try to break it. I then got a lecture that it wasn't an optimised layout and was shown the AA route finder as an example of how the tester thought it should look.1 -
Me and the team I manage after fixing bugs,
Me: hey devXY, please send a build to the QA to test it. I am going to a meeting.
*2 hours later
QA guy: hey, we did not receive any build yet.. we are already out of time..
Me to devXY: hello, why didn't you send a build to QA?
devXY: ok, sending it now.
ME LIKE: WTF!!!1 -
Me to QA: I need an urgent signature.
QA: That costs a cake.
Me: If we baked cake at our company, that would have too much sugar, and we would use more salt as workaround.4 -
I hate those morons who do QA by simply clicking around. You are a disgrace to people like me who like to code and still enjoy doing testing.
Get a life you fuckers. You are the sole reason why many people in industry thinks that QA is something anybody can do.
Yes, I agree you can test the application, but in no way you could ensure the quality of the product.4 -
I just realize I made QA wait for 5 minutes while testing session handling on the app when I missed just a single zero and made the session expire after 30 seconds instead (instead of 300000 milli calculation produced 30000)
He tried 3 times and then opened a ticket not knowing why session is always expired
wonder if I should tell him >_> -
Probably a must read for QA!
I would love to see someone referencing this book in their application 😂
-
What the fuck this fucking shit of an app supposedly went through five rounds of QA and I broke it in 5 minutes? Holy fucking shit How this is the main point of your job. You shitty shits take forever getting this PR to me and now it’s buggier than a haunted house on Halloween?
After this is after wanting to cuss Apple for making me update the os then then xcode then iTunes just to recognize the goddamn development phone. It’s an app built off Cordova it works for like 14 versions of iOS just run the bugger you over priced aluminum chassis dildo riding fruit Fuckers.
Now back to the goddamn cluster fuck I just got delivered. What the goddamn fuck. This level of bullshittery I have not seen before. And apparently Cordova is only partly de-sandboxed? I don’t know for sure because I don’t have time to test it because I’m running the entire technological stack of this company on a junior dev salary!
When you tell me it goes though all this QA and you spend 2 weeks on just QA tickets for fucks sake the first operation I do, the most common fucking operation on the app, the shit we have been building around all this fucking time, should not fucking error out. For fucks sake at least try to get the main fucking thing working. I recognize you did a lot of work and implemented a number of features but what the fuck good are they if I can’t even run them for one fucking time. -
That feeling when you hace your first talk with new lead QA, all the way from Microsoft:
QA (sitting at her new desk & PC): "How do I get the log in screen?"
Me (trying to be helpful): "Have you checked the machine is on?"
<QA checks>
QA: "How do I turn it on?"5 -
The feeling when your scrum master or lead ask you run the automated tests against the application though they know the application is down or not working.
-
Hate when one of the devs get personally offended cause I log some bugs about his part of the app.. I know it is your child, nothing about you, it's a bit retarded, and doesn't do well with other kids.. :/
-
The boss wants to improve the QA by introducing GUI tests (partially non-automatic) instead of refactoring the legacy blob of application with unit and integration tests.
THIS WONT MAKE IT ANY BETTER1 -
When QA isn't smart and you spend way to much time talking and in meetings.... "Listen, we are only testing for new bugs related to this fix, if there is a pre-existing bug, document it and move on".
QA finds a pre-existing bug and stays fixated on it for 3 days....1 -
QA vs Devs
QA PERSON 1: "They are sending the same thing again!? Did they actually make some change or do they think we're stupid and won't notice that it's the same as the last one?"
QA PERSON 2: "Is this a game of chicken? - Who caves in to the pressure first, loses."
QA PERSON 3: "Nah, it's not a big deal, just let it pass... it's going to be easier for everyone. It's not a critical thing."
On the dev side:
"They accepted it this time, with no changes. LOL They're stupid and useless." -
I just heard someone quote this
"To complain about a problem without proposing a solution is called nagging."
I know the perfect name for QA team now. 😁😁😂2 -
Nothing destroys an ego quite like the cold, ruthless testing of your software by the QA team. I humble once more.
-
QA: There is a problem
Me: Ok how do I reproduce it?
QA: You do x
Me: I have done x and there isn’t a problem
QA: Oh it only happens sometimes
Me: Fair enough, I’ll try a few times
...
Me: Are you sure x is how you do it?
QA: Oh no actually it’s y
FML2 -
That moment you're trying to access your web portal in the QA environment and you realize your colleague is loading huge amounts of data into the QA database...
-
Scenario after sending a build to QA:
(Monday)
Me: How's the build? did that app worked?
.
.
.
.
.
(here come's friday)
QA: The app didnt work on this part and there some bugs there, and please add this another module.
Me: okay ill fix that..when do you need it?
QA: today
Me: (just kill me)3 -
Doing GUI agile testing with the QA before passing my code to test server. I do this 'cause the QA marked in the past a lot of bugs that aren't bugs because he didn't liked the wording (in spanish there's A LOT of ways to say the same thing), the color of a button or an icon, and this delayed the release of the code a lot of times. So, this way I can change things to avoid unnecessary bugs... if the QA is not so busy XD
-
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 -
Me: Open Jira. See 8 point story skip QA column and move into Done.
Ask dev why it didn’t go through QA.
Teammate: Oh, did they want to test this?
Commence argument that **all** stories need to go through QA. -
Full round of QA, full round of internal testing, and the client still finds a bug nobody can reproduce.
🤷🏻♀️🤷🏻♀️🤷🏻♀️1 -
Dev: can you please merge this to master?
DevOps: ok
Dev: thx
QA: wait... Who tested this?
Dev: oh it works, it was tested...
QA: by qa?
Dev: ... <Dev2> tested (sitting right next to him)
QA: ...amIAJokeToYou.jpg6 -
Be happy or offended. You decide.
When Project Owner congratulate your team that the app is not crashing on QA. -
Main branch running locally - fine
Main branch locally connected to QA dB - fine
Main branch on QA server with QA dB - NOPE
OK - build main locally, push to QA server - fine
WTF.jpg
Main build by build server, push to QA - nope
Rebuild QA vm and dB - build main, push to QA - nope
Turn on full server logging - PASS.
MAXIMUM WHAT -
Project for a client, release date: tomorrow.
We handed over the project two weeks ago, for their QA to test everything.
Guess when they complained about having no access.
Hint: it's today1 -
Was offered a Mid QA position in my home country and just for shit and giggles applied to a QA Lead for another one (remote) and they offered me the QA Lead one as well. And now I don’t really know how the fuck you are supposed to measure seniority for this kind of jobs.2
-
I don't know if our QA is good enough. We were developing an app for both ios and android. I, an ios developer, told the QA guy that it will take long before uploading the app in the testflight (convert swift2 to swift3). After a week the app is now uploaded in the test flight and at the same time my partner, an android developer, uploaded the android version of the app in the play store beta. The QA guy started to raise bug issues about the android version. He wanted to fix the bugs immediately since our boss needed to upload it in the play store and appstore. The QA guy kept on complaining to my partner why the android version is buggy. Then he said something we, me and my partner, facepalm.
The QA guy said " You shouldn't convert the app to swift 3. The ios version is fine when converted why the android version is buggy. You need to revert it back to swift 2"
We sit there in silence, thinking if we pity the QA guy or laugh at him. -
dev vs QA rant (n + 1)
So our QA is done by China team so naturally time difference is quite irritating,
I cannot change code
I cannot debug for issue
So today I fix a critical issue and before pushing it my seniors send the to the QA
> QA unavailable
> I wait for QA because nobody notifies if the code is tested and I can work ahead
> I get review that my issue fix generated another issue (page gets redirected)
> I'm angry and astonished, I check on same link, same circumstances and no such issue is found
> My seniors say read the issue properly and I do it, no positive response when I contradict the QA
> QA leaves for home on Friday and critical issue still remains in live
I cannot believe the laziness of QA, I mean it's their loss at the end of the day.
> top of that I waited 2 hours for QA to check the issue2 -
QA: * reopens the bug I fixed *
Me: hi, whats up I thought I fixed that?
QA: *proceeds to explain totally different issue from totally different module* ... andd April fool.1 -
Today I got bug report on code that I thought was fairly well unit and manually tested by me while I was writing it.
What happened:
Our QA was testing other feature and asked someone to deploy into his env other branch, without these changes, and reported that this feature is just straight up not working at all.
That report was kindda big deal1 -
Seriously though, since so many devs I know rant about their QA / test engineers, what would your ideal Test engineer look like?!
I mean sometimes I feel like devs expect test engineers to write them their unit tests too...4 -
Is there any free software or website one can use where it takes a screenshot or page and you can mark areas on it, then add comments to those areas? (kind of like powerpoint comments, but without the awkward canvas limitation)
Then later the viewer sees instead of huge message bubbles, only those marked areas on top of the screenshot and when he hovers them - sees the comment pop up somewhere.
I remember QA having something like that, but don't remember anything about it. (I think it had a palmtree logo?..)
It would be amazingly useful for clients to just go through screenshots and marking on it "that looks nasty, put ajit pai on it".8 -
Upper mgmt paying an enterprise software vendor 40k US annually. Told vendor No more me QA'ing for them and 'discovering' obvious bugs. Told them to hire QA person and spring for some automated testing software. Yeah I know I am a nice guy but Enough is enough!1
-
Just heard a QA member say whilst training a starter:
'We are going to do some hacking now'
He just changes a URL argument.5 -
I work as part of a small international team in a big corp , we work product quality of sorts but work closer to dev than qa , last week we found several giant issues and reported them in . Dev and Qa teams of said project are Indians . Meeting starts , two of my colleagues are indian as well , so dev , qa and all the other involved parties from india decided they should join in from the same conference room . My manager(he's a brit) presents the issues . Dev manager starts talking , qa manager talks over him , they start to formally yell at one another . One of them (couldn't figure out which one) started asking my two colleagues which one of them found these issues . At this point I had already passed a headphone to my ex-colleague who still sits next to me , he looks at me when he hears the question . I panic . Colleagues say they don't know (*phu* I didn't CC them in emails and my manager didn't tell them ) . My manager tells them to calm down , take responsibility and find solutions else he'll veto the product back into fullblown development . Other managers start growling and fighting again (more than 10 people were in the same room arguing) me and my ex-colleague decide to go take a coffee since I didn't have a saying in the meeting . We get back 10 minutes later , indians are still arguing over my manager trying to explain the issues a 4th time . I IM my manager and ask to drop the meeting , he gave me the ok and I dropped out, my head was hurting after an hour long meeting of angry indians arguing in a conference room and it kept hurting the whole day...yeah...meetings...fun time...
-
This week the QA is on vacation, so we, the developers, are testing our own code (I test my partner's code and he tests mine).
For those who are QA, I have a question: If our boss omitted something on the description of how the code has to be made, for example, filtering data from database, and one of those filters are needed but the boss forgot to tell us and, at the time of making the tests, the QA and de dev team notice this... the change that has to be made should be marked as a bug? or how would you mark it?1 -
Spend about half the day fixing a bug. Whilst reporting it complete on our ticket system, QA change the ticket's expected outcome. Ffs.
-
Couple of advices from the QA guy
1) Don’t do the bare minimum bc the PM asks that. The people that write up the tasks/requirements don’t know their shit sometimes. Or even worse, they just copy paste what the client asked.
2) Confront the PM and ask more time to build something robust and scalable. When shit don’t work, people will blame the devs which is not fair. Is not easy but put your foot down when you’ve being asked to build shitty stuff bc the client want it ready now. -
No QA Steve I will not insert a massive feature into the project no matter how high of an importance you deem it or how awesome you think it is.2
-
QA guy: Your app crashed on this Samsung.
Me: Checks Firebse logs and finds out that phone was rooted and tells QA guy.
QA guy: You must consider all use cases.
Fuck you dude!2 -
Boss calls a team leads meeting which is just me and the other guy. Rest are product or project managers.
Turns out they concerns over how our last few sprints are always left unfinished as the work in it doesn't get passed QA.
Tried to tell him how can devs work on something that failed QA on the last day of the sprint.
We have one QA person who tests 20 something devs work. We are massively under resourced and yet they want us to do everything and always end up making promises to clients that we can't keep coz our sprint doesn't have capacity.
Yet they are hiring more product managers instead of getting some more QA help.
Sick & tired of this shit. -
The other day was reading someone else's shitty code which had taken an object into a set without implementing the hashcode and the equals, cursed the developer and fixed that and informed the QA about their lackadaisical attitude. Later on that fix broke some other functionality on live and now the QA team gives me the stares. Feeling like birdman...
-
So my company has 2 different apps that work using the same API located on 2 different servers.
I mistakenly uploaded both apps to the store with the same server reference.
QA tester alerts me on this issue.
Boss: hey, I the tester said both apps works with server1, ask her more info
Me: (what extra info should I need? I've already been told what's the issue in details, so what's the point?) ok, will do.
Me to QA: hey, do really both apps work on the same server?
QA: yeah
Me to QA: ok, will fix
What the fuck have I accomplished by asking the QA team about it?1 -
Just had a major breakthrough on a project for work today! The project has been going slowly the last couple months and the client actually sent a slightly concerned status request this morning, so being able to invite them to preview a fully working demo and let them know we’re starting to conduct QA testing tomorrow is quite a relief.1
-
Thread about Quality Analysts/Testers!
I've seen that Managers and HR get a lot of shit thrown their way but I'm surprised to see no love for our QA friends
What was your worst experience with a QA/Software Tester? When was the last time you felt like punching your monitor over an argument with them?
If you're a QA, what has been your worst experience with developers?6 -
What a bunch of Maroons! They come out at 4PM on Friday with a QA migration scheduled for Saturday; can we please pick up our tasks. Really? It's not even production, it's QA. Can't you wait until Monday like everyone else? Morons.
-
!rant
If you would have to stick with one language for your entire life which language would it be?13 -
So, just had an interview for a junior position at a company but as a QA engineer.
I would've preferred to apply to a more dev kinda job but I gotta eat. Apparently they liked my CV and the job doesn't sound so bad, any QA engineer with some advice or tips of what to expect if I get the job?3 -
How do you fit QA inside the weekly sprint?
At the end of a sprint, the team should be able to give something deliverable such as a new release.
How could the developers team integrate their work with the QA team along this week?
I mean, should we test individual features with QA as soon as they’re merged or make a pre-release test with all new features together before releasing? Develop 80% of the time and reserve last 20% for tests?
Could you share something or recommend any links?3 -
Given a set of projects, twice the amount of work half the amount of time to do them in. We told management we need more time and more developers. Products are being given to the clients with lots of bugs. Management's response: double the QA team size... We almost have more QA members than Dev members. FFS.
-
Everyday Build releases for closed Alpha.
My PM wants our QA to do "Little bit Smoke testing" and "little bit regression" . -
It is so frustrating working in a pure waterfall environment. My current work is constantly interrupted by QA and UAT defects. Many of which have nothing to do with my code. But they still require me to stop what I'm doing and research what happened. It's 2:43 and after meetings and research I haven't written a line of code on my current project. Ugh!
-
To ensure everything goes well on prod, the chief QA set an env called 'stable' after prod deployment to stimulate true prod situation. Then we found that some apis on 'stable' crashed more often then those on prod.
-
Work day 3 of 2023… gawrram I’m bored. Another day of IaC. Unfortunately the issues I’ve dealt with today are sequential from the QA point of view. And our QA is slow us fuck today. So a lot of waiting around for me today. I’m one fucking issue away from the Great Infrastructure Update. So close, yet so far, knowing how slow our QA process is…
So here I’m sitting around in my office away from office pondering what the hell I should do with all this time…2 -
Do you believe in QA who only tests the application as a user i.e just blackbox testing of clicking here and there.?
The QAs in my company doesn't have a clue on how the shit works and most of them don't even understand a line of code.
I feel that it's really important to test the application from the web api level as well to test out all the complex business logics which may not be feasible from the UI.15 -
Unfortunately I am working in a firm where they consider QAs as some second class citizens. Also the QAs we have right now are purely blackbox testers who doesn't know shit about the system.
In my opinion a QA should know about the system and integration. They should also have decent programming skills.
What are your thoughts?2 -
How many developers does it take to install a white board...
3, and 1 QA, 1 designer, 1 project manager and 3 attempts...9 -
QA Tester: titles in table items look like links and are clickable, they should be plain text.
Senior Dev: style={{ color: '#000' }}6 -
(I am not a native english speaker so please excuse any mistakes I make while writing this)
I know, during an internship, its good to see all different sides of the job and of course QA is one of them. Its definately good to know as a dev later how QA works, I can see that. But why the F U C K do I have to test the same 3 pages (not websites, PAGES) since 5 days for 8 hours a day even though NOTHING CHANGES?! The page doesn't get updated, I am just sitting there clicking around and wasting my time I could use to learn more PHP or jQuery or WTFEver. But no! I have to sit there for hours and hours, doing nothing but staring at a page where I already tested literally anything that can be tested 4 days ago. If you don't have a good task for me over there in QA, then STOP WASTING MY FUCKING TIME instead of forcing me to continue testing this stupid website even though testing already completed a few days ago!!! I don't even have Test Cases to follow, its just “yea look at this page and click around is something is broken“ for 5 days. There is nothing broken, your fucking website works fine. And now STOP WASTING MY TIME!!!!6 -
What is the best way to learn QA automation? Any ideas? If you have links to tutorial and also the download content for me to practice that would be great!!! Thanks2
-
Is QA bad at all companies or just mine? We ask QA to test changes from a list of changes. They come back with existing bugs outside the scope of what they were testing. Waste our time talking about irrelevant and out of scope bugs, then when corrected they respond "what would you like me to test?" Then I try to refrain from snapping and say "test the original items on the list like we originally asked you too... Agh. I really don't like working with our QA. They slow everything down, they cause delays because they don't grasp things. And it wastes our dev time, we talk about the same things over and over. Ugh.2
-
You ever have someone who you'd set to QA for a group project, and then find out that - rather than setting up automated testing and writing code that can be run at different times in the development cycle - they just did it by hand, running through the program and deciding that the result they got was good enough?
Imma smack a bitch, then write this shit in their stead.2 -
One QA guy ... I solved one ticket out of two. He doesn't want to pass it because the other one is still unfixed.
-
The only thing worse than client QA is client vendor QA.
I do QA for a company that does custom implementations of a major e-commerce platform. On one of my current projects, the customer has elected to outsource their UAT, and isn't willing to wait for the site (or even individual features) to be complete before starting testing, so I've been triaging a lot of silly tickets. But today took the cake.
This system allows users to save their credit card info. The vendor QA guy filed a ticket "reporting" that if he saved a cc with a given number, then created a new cc record with the same number but a different expiration date, the original record was overwritten, rather than a new record being created.
I just stared at the thing for like five minutes, gathering the mental strength to reply with something other than "you're an idiot."3 -
I've been a freelance for almost 20 years, so I had the ability to choose my tech and architecture. Now that I'm leading a team, I'm finally needing to fight with other developers to convince them to actually use what was the scientific state of the art 20 years ago, because our field is so disconnected from science and good practices…
The upside is that I get to teach that state of the art to my team members.
I'll see in a year if it's more thrilling or tiring. -
Does your company use QA team? Or do you do your own QA.
We do our own QA and then write detailed damned test cases in excel o.o for other people to run the scenarios you've already run through o.o4 -
Hey guys!
I'm a senior computer science student at a big ten university graduating in December. I'm thrilled to have been offered a full time software engineer 1 position on a QA team. I just wanted to ask, I ultimately want to be a software dev, would taking this QA position make that more difficult in any way? Or is it a great place to start? Because it is a software engineer position, but not directly doing software development.
Thanks for your input!3 -
Anyone here made a change from a QA background to a Mobile Dev or just regular dev? Any tips for a QA looking to ditch the field soon.
I’m an automation QA bit still feeling like the coding challenges are not enough.2 -
I was a pure automation QA guy. And told every recruiter that I will do pure automation.
All told truth about profile except current one.
Here I am supposed to be a QA guy with 90%manual and just 10%automation :((
-
If I had a dollar for every time a mother fucker in QA distracted me and threw me out of focus..
Nothing against QA but an unnecessary interaction costs me about an hour of downtime trying to back up to speed. -
Made a working full stack native app..
QA-"what happens if I change my time and try to fool the time based component."
Why didn't you tell about that earlier you piece of shit!!!! -
Starting to wonder why I tend to like our QA people so much: they often seem so much saner. Yes, sometimes they quibble as with the complaints about a page that is hidden from the user anyway, but they would usually not creep to deep into the hole creating most unintuitive workflows and abysmal logic.
Disclaimer: We're more like backend devs, but we had to do a UI which was beautifully slaughtered by the CEO messing with it - guess what's happening with the new one - and because of that... thing I already nearly smashed my Mac because stupid entered credentials for updating software would only be applied if you defocused once out of the password entry box. Fucked up stuff like this, which devs meddle with, give up, just shrug it off and dump it on the (l)user.
Or a more recent example: So PM wanted a stupid "Apply to all" buttons on a list that can be filtered. Guess to which items the actions should be applied if you filtered it and you currently only see a small selection in your window! Yes, of course it still applies to all items in the universe. QA guy who's just trying the buttons comes to me: "Hey, you sure this "apply all"-stuff supposed to work like that?"
Third example to end this long QA-praise: So there is this virtual appliance we build and we should support another stupid hypervisor.. and he found the kernel modules I have to activate additionally so we can just convert the existing image without having to create a new build system.3 -
When you click on a link in google and get taken to "wwwqa.companyname.com". I think they're really really confident in their QA environments ;)
-
I've talked with my friend about what does that mean to work as QA. It seems all they do is watching yet vids with kittens and slacking off, and basically they are useless.
But then, it clicked. They are people to blame first if shipped product have bugs.
I wonder if one day, one dev just thought(after getting reprimanded by his boss for bugs in the final product): "hey, I don't need to listen to this, we can hire a guy for that!1 -
Why humankind why? People changing my code, commit without testing and QA is complaining cause the shit isn't working.2
-
Hey guys.
Does anyone have an idea of the proper way to answer this question.
It is testing your ability to communicate complex things.
"Describe the color green to a blind person"13 -
I’m having to justify why our QA team doesn’t actually point stories… anyone have a good reference?5
-
Why is it acceptable for dev think it's ok to skip testing? WHY?
Today i was told that a co-worker had good enough judgment when it comes to CSS if it will break in other browsers other than chrome. I'd accept that if they knew the browsers inside out and read all the release docs but no, not them. Even more so when it's not their field of expertise.
After working for 2+ years at the some company, with a QA team, it's become evident no one does any proper testing, even the friking QA team!
I'm close to define the supported browsers as "What ever the developer used at the time of build".
Am I really the only Dev to test in at least 2 other browsers? -
Everytime my qa says "it's a bug"
Me: You saint, it's not a bug, it's a feature...
*Awkward silence* -
So turns out my manager wants me to do QA automation (not in Espresso btw) of my own items "because we're all in the same team". The weirdest thing is that she's obsessed with "best practices" about daily iteration work such as not starting to work on something until test planning is done (she gets CRAYZEEE about that). Violating one of the core development principles is out the window so I guess the question is am I in a good place to ask for a raise since I'm going to have dual roles?2
-
Repeating story, here, isnt it? A dev dislikes a PM, a QA, a Boss. They don't understand, or have unrealistic expectations or say something "stupid"...
But it requires guts to work with other people, cause often the facts we devs have to tell isn't popular. But to lower unrealistic expectations with the bosses, isn't that part of being pro?
Wish *I* had guts... -
Guys, need your help. What are some interview question for junior QA? Aaand, what do I need to review? Thanks a looooot!3
-
When you're working with a QA/test engineer that insists on manually testing code that have automated tests. Can any test engineera chime in here?
-
QA: Finds and reports Critical Bug
Dev: Hotfix 2 days before next scheduled deploy, NP!
After Scheduled Deploy...
QA: Critical Bug is back
Dev: Oops, overwrote hotfix during Scheduled Deploy -
QA to Android Dev : "the app just force closed"
Android Dev : giving a Darth Vader look pretending to use the force.
QA : "won't work on me, i have the FORCE CLOSE" -
Dev and QA environments are housed on AWS servers, both sharing the same API code. Dev API is unable to connect, while QA is able to connect just fine. How does this happen 😱
-
Calling QA/ Test managers for help !
Im a junior dev at a company where im slowly transitioning into also being our test lead. I just got my ISTQB foundation and im starting to write out the test strategy for our company.
Currently we’r doing alot of reactice testing, and to implement more proactive testing i wanted to implement a risk strategy as well.
Problem is that i feel this strategy takes too much time for our organization (doing risk analysis for each story we’r implementing just isnt possivle) , and we don’t have time for me actinh as a full time Test manager while also doing software dev tasks.
Question is: what good proactive strategies can we implement that doesnt require too much time investment - or could we use risk strategy only for specific stories implemented / custom orders / etc and stick with a reactive strategy solely ?
Later this yesr ill be sent on ISTQB test manager course to better qualify my position but until then id really want to get a test strategy somewhat implemented
Any help is MUCH appriciated!10 -
So I'm the only tester at my company, and I've had to adapt a lot of my skills to fit in with our in house expectations. So everything was fine when I focused on trying one component (manual and automation).
Slowly over time I've had more components to test with exact same resource of me.
Eventually my automatic breaks as I could no longer maintain that and all the other manual tests and all the other jobs I do ( light level internal it support, jira ticket rangerling, rollbar (error messages) basic investigation).
My boss keeps saying why is x,y,z not tested / missed while I can point to time periods where was focused on v instead so didn't get to others.
I keep wanting to just hit them with a keyboard until they realise 10± devs to one qa in our environment just isn't going to work.
I keep getting promised some dev time to help with qa so I can play catch up but never seems to arrive.
Don't get me wrong I'm not the best I used to be at testing(before joining I was proud of my abilities, maybe all stick and not enough carrot wears you down)
We keep taking on new work flows that make no sense (create a bug ticket, then a task ticket if bug take more than hour to do, then I'm stuck chasing developers to update their task ticket so I cam update the bug ticket (if its a bug then log sodding log time against it).
I've gotten to point now where I'm stopping my suggestions, explaining why something didn't get dome and will see if they can answer their own stupid questions
At what point do you stop ignoring the voices in your head (metaphorically).
Do other people go through this cycle where feel like pushing a boulder up the hill, for them to either push your boulder down the hill, replace it with a bigger boulder, move to a bigger hill, get you to move more rocks at once or all the above.
I know QA has its quite and busy phases but for me it seems to be constantly busy with no respite4
Top Tags
Weekly Rant
View