Boss: "I looked at a testing suite. It is $2,500 a license and I'm buying 60 licenses. You should probably get familiar with it."
LeadDev: "Um, we already use NUnit, and it's free."
Boss: "Hmm...I'd better add Pluralsight training in the budget so you can learn about the new program."
LeadDev: "Oh, no...we need new laptops more than we need software."
Boss:"New laptops? Not my budget. When we buy this new software, everyone is going to use it"
LeadDev: "Everyone? How will you monitor it's usage?"
Boss: "I'll have networking send me captures of all the running tasks on the dev machines. The test suite better be running. Writing good tests will be our #1 priority."
LeadDev: "Um, we already write tests using NUnit."
Boss: "I don't understand what you are saying. I need something I can visualize. This UI testing suite is exactly what I need."
LeadDev: "Maybe the testing suite would be better suited for you and QA?"
<click..click>
Boss: "Submitted the budget. There will be a test server available for you to configure. This whole project costs over $100,000, so don't screw it up. Any questions?"
LeadDev: "Oh...well...what server ..."
Boss: "Dang...sorry, I'm taking off the rest of the afternoon. We'll talk about this more on Monday. Get started on those Pluralsight videos. I'll expect a full training and deployments by next week. Have a great weekend!"

Unit testing be like "all tests passed"

"Don't deploy on Friday" is a public admittance that your company either has no CI/CD pipeline, or that all your devs are retarded rhesus monkeys who only wipe their ass if the product manager wrote it as a spec.

If the saying was: "Don't port your whole API to GraphQL on a Friday", or "Don't switch from MySQL to Postgres on a Friday", I would agree.

But you should be able to do simple deploys all the time.

I deployed on Christmas & New Year's eve. I've deployed code while high on LSD, drunk-peeing 2 liters of beer against a tree after a party. I've deployed code from the hospital while my foot was being stitched up. On average, we deploy our main codebase about 194 times a week.

If you can't trust your deploys, maybe instead of posting stupid memes about not deploying on Fridays, you should fix your testing & QA procedures.

>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.

Things have been a little too quiet on my side here, so its time for an exciting new series:

practiseSafeHex's new life as a manager.

Episode 1: Dealing with the new backend team

It's great to be back folks. Since our last series where we delved into the mind numbing idiocy of former colleagues, a lot has changed. I've moved to a new company and taken a step up as a Dev manager / Tech lead. Now I know what you are all thinking, sounds more dull and boring right? Well it wouldn't be a practiseSafeHex series if we weren't ...

<audience-shouting>
DEALING! ... WITH! ... IDIOTS!
</audience-shouting>

Bingo! so lets jump right in and kick us off with a good one.

So for the past few months i've been on an on-boarding / fact finding / figuring out this shit-storm, mission to understand more about what it is i'm suppose to do and how to do it. Last week, as part of this, I had the esteemed pleasure of meeting face to face with the remote backend team i've been working with. Lets rattle off a few facts to catch us all up:

- 8 hour time difference to me
- No documentation other than a non-maintained swagger doc
- Swagger is reporting errors and several of the input models are just `Type: String`
- The one model that seems accurate, has every property listed as optional, including what must be the primary key
- Properties go missing and get removed at the drop of a hat and we are never told.
- First email I sent them took 27 days to reply, my response to that hasn't been answered so far 31 days later (new record! way to go team, I knew we could do it!!!)
- I deal directly with 2 of them, the manager and the tech lead. Based on how things have gone so far, i've nick named them:
1) Ass
2) Hole

So lets look at some example of their work:

- I was trying to test the new backend, I saw no data in QA. They said it wouldn't show up until mid day their time, which is middle of the night for us. I said we need data in our timezone and I was told: a) "You don't understand how big this system is" (which is their new catch phrase) b) "Your timezone is not my concern"

- The whole org started testing 2 days later. The next day a member from each team was on a call and I was asked to give an update of how the testing was going on the mobile side. I said I was completely blocked because I can't get test data. Backend were asked to respond. They acknowledged they were aware, but that mobile don't understand how big the system is, and that the mobile team need to come up with ideas for the backend team, as to how mobile can test it. I said we can't do anything without test data, they said ... can you guess what? ... correct "you don't understand how big the system is"

- We eventually got something going and I noticed that only 1 of the 5 API changes due on their side was done. Opened tickets. 2 days later asked them for progress and was told that "new findings" always go to the bottom of the backlog, and they are busy with other things. I said these were suppose to be done days ago. They said you can't give us 2 days notice and expect everything done. I said the original ticket was opened a month a go *sends link* ......... *long silence* ...... "ok, but you don't understand how big the system is, this is a lot of work"

- We were on a call. Product was asking the backend manager (aka "Ass") a question about a slight upgrade to the new feature. While trying to talk, the tech lead (aka "Hole") kept cutting everyone off by saying loudly "but thats not in scope". The question was "is this possible in the future" and "how long would it take", coming from management and product development. Hole just kept saying "its not in scope", until he was told to be quiet by several people.

- An API was sending down JSON with a string containing a message for the user with 2 bits of data inside it. We asked for one of those pieces to also come down as a property as the string can change and we needed it client side. We got that. A few days later we found an edge case and asked for the second piece of data to be a property too. Now keep in mind, they clearly already have access to them in order to make the string. We were told "If you keep requesting changes like this, you are going to delay the release of the backend by up to 2 weeks"

Yes folks, there you have it, the most minuscule JSON modifications, can delay your release by up to 2 weeks ........ maybe I should just tell product, that they don't understand how big the app is, and claim we can't build it on our side? Seems to work for them

Thats all the time we have for today,

Tune in for more, where we'll be looking into such topics as:

- If god himself was an iOS developer ... not
- Why automate when you can spend all day doing it by hand
- Its more time-efficient to just give everything a story point of 5
- Why waste time replying to emails ... when you can do nothing instead

See you all next week,
practiseSafeHex

Doot doot.

My day: Eight lines of refactoring around a 10-character fix for a minor production issue. Some tests. Lots of bloody phone calls and conference calls filled with me laughing and getting talked over. Why? Read on.

My boss's day: Trying very very hard to pin random shit on me (and failing because I'm awesome and fuck him). Six hours of drama and freaking out and chewing and yelling that the whole system is broken because of that minor issue. No reading, lots of misunderstanding, lots of panic. Three-way called me specifically to bitch out another coworker in front of me. (Coworker wasn't really in the wrong.) Called a contractor to his house for testing. Finally learned that everything works perfectly in QA (duh, I fixed it hours ago). Desperately waited for me to push to prod. Didn't care enough to do production tests afterwards.

My day afterwards: hey, this Cloudinary transform feature sounds fun! Oh look, I'm done already. Boo. Ask boss for update. Tests still aren't finished. Okay, whatever. Time for bed.

what a joke.

Oh, I talked to the accountant after all of this bullshit happened. Apparently everyone that has quit in the last six years has done so specifically because of the boss. Every. single. person.

I told him it was going to happen again.

I also told him the boss is a druggie with a taste for psychedelics. (It came up in conversation. Absolutely true, too.) It's hilarious because the company lawyer is the accountant's brother.

So stupid.

Not so much screaming as staring in disbelief, mumbling profanity in his direction...

When my department lead said "I don't think this unit testing hype or code reviews make much sense, it's more efficient to just make a checklist and test the application yourself"

This was the QA department of an aerospace company, we wrote NDT software to do image recognition on xrays of alloy welds and micrometer laser measurements on fuel tank surfaces. Software which is quite mission critical, a single misrecognized welding fault could literally cost up to half a billion dollars — not to mention that it's a very sabotage & espionage sensitive industry.

After raising some hell he was replaced though.

!rant
!!git

Who here uses `master` for development?

My boss (api guy) tried to convince me that was normal practice. I gently told him that it sounded crazy and very very bad.

Here's the dev path I'm enforcing on my repos:

(feature branches) -> dev -> qa* -> master -> production*

*: the build server auto-pulls from these branches, and pushes any passing builds to staging/production.

Everyone works on their own feature branches, and when they're happy with their work, they merge it into `dev`. `dev`, therefore, is for feature integration testing. After everything is working well on `dev`, it gets merged into `qa` for the testers to fawn over and beat with sticks. Anything that passes QA gets merged into `master`, where it sits until we're ready to release it. When that time comes (it's usually right away, but not always), `master` gets merged into `production`.

This way, `master` is always stable and contains the newest code, so it's perfect for forking/etc. Is this standard practice, or should I be doing something different?

Also, api guy encourages something he calls "running a racetrack" -- each dev has their own branch (their initials) and they push to that throughout the day. everyone else pulls from it regularly and pushes to their own branch. When anyone's happy with their code, they push from their (updated) branch to `qa` (I insisted on `dev` instead.)

Supposedly this drastically reduces the number of merge conflicts when pushing to an upstream branch due to having a more recent ancestor node?

I don't quite follow that, but it seems to me that merging/pushing throughout the day would just make them happen sooner? idk.

What are your thoughts?

Why are job postings so bad?
Like, really. Why?

Here's four I found today, plus an interview with a trainwreck from last week.
(And these aren't even the worst I've found lately!)

------

Ridiculous job posting #1:
* 5 years React and React Native experience -- the initial release of React Native was in May 2013, apparently. ~5.7 years ago.
* Masters degree in computer science.
* Write clean, maintainable code with tests.
* Be social and outgoing.

So: you must have either worked at Facebook or adopted and committed to both React and React Native basically immediately after release. You must also be in academia (with a masters!), and write clean and maintainable code, which... basically doesn't happen in academia. And on top of (and really: despite) all of this, you must also be a social butterfly! Good luck ~

------

Ridiculous job posting #2:
* "We use Ruby on Rails"
* A few sentences later... "we love functional programming and write only functional code!"

Cue Inigo Montoya.

------

Ridiculous job posting #3:
* 100% remote! Work from anywhere, any time zone!
* and following that: You must have at least 4 work hours overlap with your coworkers per day.
* two company-wide meetups per quarter! In fancy places like Peru and Tibet! ... TWO PER QUARTER!?

Let me paraphrase: "We like the entire team being remote, together."

------

Ridiculous job posting #4:
* Actual title: "Developer (noun): Superhero poised to change the world (apply within)"
* Actual excerpt: "We know that headhunters are already beating down your door. All we want is the opportunity to earn our right to keep you every single day."
* Actual excerpt: "But alas. A dark and evil power is upon us. And this… ...is where you enter the story. You will be the Superman who is called upon to hammer the villains back into the abyss from whence they came."

I already applied to this company some time before (...surprisingly...) and found that the founder/boss is both an ex cowboy dev and... more than a bit of a loon. If that last part isn't obvious already? Sheesh. He should go write bad fantasy metal lyrics instead.

------

Ridiculous interview:
* Service offered for free to customers
* PHP fanboy angrily asking only PHP questions despite the stack (Node+Vue) not even freaking including PHP! To be fair, he didn't know anything but PHP... so why (and how) is he working there?
* Actual admission: No testing suite, CI, or QA in place
* Actual admission: Testing sometimes happens in production due to tight deadlines
* Actual admission: Company serves ads and sells personally-identifiable customer information (with affiliate royalties!) to cover expenses
* Actual admission: Not looking for other monetization strategies; simply trying to scale their current break-even approach.

------

I find more of these every time I look. It's insane.
Why can't people be sane and at least semi-intelligent?

Welcome back to practiseSafeHex's new life as a manager.

Episode 2: Why automate when you can spend all day doing it by hand

This is a particularly special episode for me, as these problems are taking up so much of my time with non-sensical bullshit, that i'm delayed with everything else. Some badly require tooling or new products. Some are just unnecessary processes or annoyances that should not need to be handled by another human. So lets jump right in, in no particular order:

- Jira ... nuff said? not quite because somehow some blue moon, planets aligning, act of god style set of circumstances lined up to allow this team to somehow make Jira worse. On one hand we have a gigantic Jira project containing 7 separate sub teams, a million different labels / epics and 4.2 million possible assignees, all making sure the loading page takes as long as possible to open. But the new country we've added support for in the app gets a separate project. So we have product, backend, mobile, design, management etc on one, and mobile-country2 on another. This delightfully means a lot of duplication and copy pasting from one to the other, for literally no reason what so ever.

- Everything on Jira is found through a label. Every time something happens, a new one is created. So I need to check for "iOS", "Android", "iOS-country2", "Android-country2", "mobile-<feature>", "mobile-<feature>-issues", "mobile-<feature>-prod-issues", "mobile-<feature>-existing-issues" and "<project>-July31" ... why July31? Because some fucking moron decided to do a round of testing, and tag all the issues with the current date (despite the fact Jira does that anyway), which somehow still gets used from time to time because nobody pays attention to what they are doing. This means creating and modifying filters on a daily basis ... after spending time trying to figure out what its not in the first one.

- One of my favourite morning rituals I like to call "Jira dumpster diving". This involves me removing all the filters and reading all the tickets. Why would I do such a thing? oh remember the 9000 labels I mentioned earlier? right well its very likely that they actually won't use any of them ... or the wrong ones ... or assign to the wrong person, so I have to go find them and fix them. If I don't, i'll get yelled at, because clearly it's my fault.

- Moving on from Jira. As some of you might have seen in your companies, if you use things like TestFlight, HockeyApp, AppCenter, BuddyBuild etc. that when you release a new app version for testing, each version comes with an automated change-log, listing ticket numbers addressed ...... yeah we don't do that. No we use this shitty service, which is effectively an FTP server and a webpage, that only allows you to host the new versions. Sending out those emails is all manual ... distribution groups?? ... whats that?

- Moving back to Jira. Can't even automate the changelog with a script, because I can't even make sense of the tickets, in order to translate that to a script.

- Moving on from Jira. Me and one of the remote testers play this great game I like to call "tag team ticketing". It's so much fun. Right heres how to play, you'll need a QA and a PM.

*QA creates a ticket, and puts nothing of any use inside it, and assigns to the PM.
*PM fires it back asking for clarification.
*QA adds in what he feels is clarification (hes wrong) and assigns it back to the PM.
*PM sends detailed instructions, with examples as to what is needed and assigns it back.
*QA adds 1 of the 3 things required and assigns it back.
*PM assigns it back saying the one thing added is from the wrong day, and reminds him about the other 2 items.
*QA adds some random piece of unrelated info to the ticket instead, forgetting about the 3 things and assigns it back.

and you just continue doing this for the whole dev / release cycle hahaha. Oh you guys have no idea how much fun it is, seriously give it a go, you'll thank me later ... or kill yourselves, each to their own.

- Moving back to Jira. I decided to take an action of creating a new project for my team (the mobile team) and set it up the way we want and just ignore everything going on around us. Use proper automation, and a kanban board. Maybe only give product a slack bot interface that won't allow them to create a ticket without what we need etc. Spent 25 minutes looking for the "create new project" button before finding the link which says I need to open a ticket with support and wait ... 5 ... fucking ... long ... painful ... unnecessary ... business days.

... Heres hoping my head continues to not have a bullet hole in it by then.

Id love to talk more, but those filters ain't gonna fix themselves. So we'll have to leave it here for today. Tune in again for another episode soon.

And remember to always practiseSafeHex

Imagine if a structural engineer whose bridge has collapsed and killed several people calls it a feature.

Imagine if that structural engineer made a mistake in the tensile strength of this or that type of bolt and shoved it under the rug as "won't fix".

Imagine that it's you who's relying on that bridge to commute every day. Would you use it, knowing that its QA might not have been very rigorous and could fail at any point in time?

Seriously, you developers have all kinds of fancy stuff like Continuous Integration, Agile development, pipelines, unit testing and some more buzzwords. So why is it that the bridges don't collapse, yet new critical security vulnerabilities caused by bad design, unfixed bugs etc appear every day?

Your actions have consequences. Maybe not for yourself but likely it will have on someone else who's relying on your software. And good QA instead of that whole stupid "move fast and break things" is imperative.

Software developers call themselves the same engineers as the structural engineer and the electrical engineer whose mistakes can kill people. I can't help but be utterly disappointed with the status quo in software development. Don't you carry the title of the engineer with pride? The pride that comes from the responsibility that your application creates?

I wish I'd taken the blue pill. I didn't want to know that software "engineering" was this bad, this insanity-inducing.

But more than anything, it surprises me that the world that relies so much on software hasn't collapsed in some incredible way yet, despite the quality of what's driving it.

Whoever designed UEFI, FUCK YOU!! Giving the OS control over every fucking thing in the hardware instead of letting the BIOS do that separately, WHO IN THEIR RIGHT FUCKING MIND THOUGHT THAT THAT WAS A GOOD IDEA?!!

And same goes to fucking you Microsoft! How difficult is it to do a fucking ACPI shutdown and do it properly?! How fucking difficult is it to not make the fans spin like jet engines because why the fuck not?! And yes the fucking PC is dust-free and bloat-free so I don't want to see any fucking Wintard comment that.

You know where else I saw the inability to power down? In Linux 4.20-rc2. A kernel that is within active development, and rc2 at that!! A kernel branch that's designed to be unstable, for testing purposes. Meanwhile the stable branch of MS Windows does the same. Also designed to be unstable because fuck QA?! Filthy fucking motherfuckers!!

Me: Hi Guys, theres no docs on our custom push notification / deeplinking implementation. I've tried to work backwards from a QA testing doc to add new links. Can someone tell me if this is all ok? It seems to behave a little weird.

Dev: Looks ok, but we've moved to the braze platform for sending notifications. You'll need to trigger braze notifications now. Test that it works ok with that <confluence-link>

*hour later*

Me: I've tried the debugging tool, both with my payload and one of the samples from the link. It displays on the phone, but tapping it doesn't trigger the deeplinking.

Dev: No it works, try one of these <screenshot of samples I used>

*hour later*

Me: Tried it again on the real device to make sure, as well as on develop and master. Not working with those samples or mine.

Dev: No it does. It comes in here in this library <github link to line of code>

Me: ... Nope, debugged it, it doesn't get passed the next 'if' check on the next line as its missing a key/value. The whole function does nothing.

Dev: Oh do you want to send a braze notification?

Me: ..... you told me I had too .... yes I guess.

Dev: ok for a braze notification it works different, send this <entirely different sample no where on the link>

Me: ...... but ..... this is only for braze notifications ..... why .... all the samples have deeplink url's .... but they don't ....... are you ..... FFS!!!!! !@#?!

(╯°□°）╯︵ ┻━┻

┻━┻ ︵ヽ(`Д´)ﾉ︵ ┻━┻

(ノಠ益ಠ)ノ彡┻━┻

┌П┐(ಠ_ಠ)

QA: Why have you sent this for testing? it's not working!

Me: Have you cleared your cache?

QA: Oh

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...

Long story short, I'm unofficially the hacker at our office... Story time!

So I was hired three months ago to work for my current company, and after the three weeks of training I got assigned a project with an architect (who only works on the project very occasionally). I was tasked with revamping and implementing new features for an existing API, some of the code dated back to 2013. (important, keep this in mind)

So at one point I was testing the existing endpoints, because part of the project was automating tests using postman, and I saw something sketchy. So very sketchy. The method I was looking at took a POJO as an argument, extracted the ID of the user from it, looked the user up, and then updated the info of the looked up user with the POJO. So I tried sending a JSON with the info of my user, but the ID of another user. And voila, I overwrote his data.

Once I reported this (which took a while to be taken seriously because I was so new) I found out that this might be useful for sysadmins to have, so it wasn't completely horrible. However, the endpoint required no Auth to use. An anonymous curl request could overwrite any users data.

As this mess unfolded and we notified the higher ups, another architect jumped in to fix the mess and we found that you could also fetch the data of any user by knowing his ID, and overwrite his credit/debit cards. And well, the ID of the users were alphanumerical strings, which I thought would make it harder to abuse, but then realized all the IDs were sequentially generated... Again, these endpoints required no authentication.

So anyways. Panic ensued, systems people at HQ had to work that weekend, two hot fixes had to be delivered, and now they think I'm a hacker... I did go on to discover some other vulnerabilities, but nothing major.

It still amsues me they think I'm a hacker 😂😂 when I know about as much about hacking as the next guy at the office, but anyways, makes for a good story and I laugh every time I hear them call me a hacker. The whole thing was pretty amusing, they supposedly have security audits and QA, but for five years, these massive security holes went undetected... And our client is a massive company in my country... So, let's hope no one found it before I did.

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.*

How QA people buy beds..

//I have done all kinds of testing that possible exist, but I'm still not convinced

User: “I’ve tried hundreds of different names. How come all the usernames are registered?!😤”
Developer: ”I’m quite confident about my code. Can’t find any issue in this login form.🤔”
QA: “It passed all unit tests. We did a comprehensive testing on live server by registering all the possible names. What can go wrong?🙀”

I had to explain what version control was to the dinosaur last week. (Our cto, for more context check last post)

So we've been having issues getting our infrastructure dude to do deployment because he is sick of the treatment he gets here and has basically checked out.

Deployments then fell onto the dinosaur. After struggling for an eternity to figure out app settings (any junior dev could figure this out) he finally deployed, however it was from qa branch.

I gently reminded him that we were deploying from master and that all changes in qa should be merged to master when testing phase is over.

He informed me that 'he doesn't think that's a good idea because if we merge to master and there's problems then it's fucked forever and there is nothing we can do'

I stood there with my mouth hanging ajar until I finally managed to squeeze out 'that's literally what git is for....' 🤡

how the qa tests my code

I just told my biggest client that they have to start changing things or they will need to find a different company to work with.

I'm hired to program what they want. They are suppossed to do all the concepting, functional designs, QA, testing.

So they tell me to program feature x, not realising that this interact with feature y. And then complain about the change in feature y. Make me do a lot of extra work and then complain that my estimates are way off.

So I told them they also need to hire my company for the software design and QA and prefferable testing because I'm done getting blamed.

Me done fixing a bug.
Me commit the fix.
Me resolve issue in JIRA.
Few minutes later, Me receive a notification. QA reopened issue: "Bug is still there".
Me go have look to Jenkins.
Pissed off, Me respond to QA: "Can you just wait for Maven to finish building the goddamn thing before testing it please?"

Every. Fucking. Time

One of the best GIFs in the history of GIFs.

Once I purposely made a very obvious mistake to see if QA was actually testing due to how many bugs were getting through to production.

The code is a freaking mess. Shared behavior, terrible variable/method naming, misleading module naming, dynamic polymorphic spaghetti, whitespace errors, no consistency, confusing even if you understand what the code is doing, ... . It should never have passed code review. It probably wasn't code reviewed.

The comments are sparse and useless. Quality level: // This is bridge.

The documentation does not exist.

Testing steps for QA are missing several steps, including setup, so actually using the feature is bloody challenging. If one thing is wrong, the feature just doesn't show up (and ofc won't tell you why).

The specs for the feature are outdated and cover only 4 of 19+ cases. And are neigh useless for those 4.

The specs for the report I'm fixing don't even check the data on the report; it just checks for one bit of data on each row it creates -- a name -- which is also the same on each row. gg.

The object factories (for specs) are a mess, and often create objects indirectly, or in backwards order with odd post-create overwriting to make things work. Following the factories is a major chore, let alone fixing or extending them.

The new type has practically zero test coverage.

The factory for the new type also only creates one variant -- and does so incorrectly.

And to top it all off: the guy who wrote the feature barely ever responds. If he does, he uses fewer words than my bird knows, then stops responding. I've yet to get a useful answer out of him. (and he apparently communicates just fine, according to my micromanager.)

But "it's just fixing a report; it'll be easy!"
Oh, fuck off.

Just finished my internship.

I entered knowing nothing and spent the entire year on solo projects.

My company does not use any frameworks because "they don't want to run code on a server that they didn't write", they use waterfall, only use version control on half the projects, use notepad++, never once even glanced at my code to check I know what I'm doing - even when i asked.

Also have never heard of a code review, have absolutely no QA in place other than the devs making it and quickly testing it visually, no requirements gathering - just pictures and have never heard of tdd.

Recently was given a project with no designs, no specs other than a verbal half thought out explanation and was dumped with random deadlines like "this needs to be demoed tomorrow night" with no idea about the project progression or what it looks like. Apparently it's all my fault that it failed.

I am very grateful to them for teaching me so much and giving me opportunities to teach myself on nice projects but come on.

What boggles my mind is that the company is 6 years old and has big, big clients. I don't understand how. I once tested a project about to go out the next day that had been "tested" and found pages of bugs. They would have lost the contract for sure...

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 HOME

Why is there so much hate against QA in general??

I read tons of rants about how bad testers are... and as a dev who does a lot of QA work, IT SUCKS!

We (devs) have to accept that are work needs to be tested! Otherwise we want be successful with our products.

BUT the testers need to know the development business! They should be trained at the same level as the devs are.

BECAUSE if the mug on my desk is smarter than the tester it is not going to work!
If the tester has full access to all the technologies, environments and tools (and are capable of using it) he has the ability to HELP!

I THINK that testing should be more than just follow predefined steps and let a random tool generate a bugreport.

I am sure that some of you are lucky enough to work with highly skilled testers so please let them help

Got this in the email.

Frequently used answers :)

UI developer - I think API is not working
Backend developer - Front end is not sending the request correctly
Tester - Testing! Testing!
UI/UX - As per android/ios standards...
QA - Let me check one more time
PM - Let us have another meeting and get on the same page
Dev-Ops - It's very complicated you know
CTO - We're working on a next-gen solution
Founder - Let us build something that no one has built, something similar to what google...facebook...

Cridits: My EX-CPO

Write so many tests that QA goes out of job 😃😃

- Be me (Dev)
- Develop website for client that has an online payment integration.
- Notice there is no one for QA and testing.
- Try to raise voice about it but get shot down by management.
- Get order to push the project to production (because the deadline has arrived, therefore the project must be ready)
- Production performance has an error margin of 15% (customers getting their card over/under charged)
- Get blamed and flamed for everything cuz well, its all the dev's fault.

FML

Just got this notification. I see virgin active UK likes to test in production. I too like to live dangerously.

I'm coming off a lengthy staff augmentation assignment awful enough that I feel like I need to be rehabilitated to convince myself that I even want to be a software developer.

They needed someone who does .NET. It turns out what they meant was someone to copy and paste massive amounts of code that their EA calls a "framework." Just copy and paste this entire repo, make a whole ton of tweaks that for whatever reason never make their way back into the "template," and then make a few edits for some specific functionality. And then repeat. And repeat. Over a dozen times.

The code is unbelievable. Everything is stacked into giant classes that inherit from each other. There's no dependency inversion. The classes have default constructors with a comment "for unit testing" and then the "real" code uses a different one.

It's full of projects, classes, and methods with weird names that don't do anything. The class and method names sound like they mean something but don't. So after a dozen times I tried to refactor, and the EA threw a hissy fit. Deleting dead code, reducing three levels of inheritance to a simple class, and renaming stuff to indicate what it does are all violations of "standards." I had to go back to the template and start over.

This guy actually recorded a video of himself giving developers instructions on how to copy and paste his awful code.

Then he randomly invents new "standards." A class that reads messages from a queue and processes them shouldn't process them anymore. It should read them and put them in another queue, and then we add more complication by reading from that queue. The reason? We might want to use the original queue for something else one day. I'm pretty sure rewriting working code to meet requirements no one has is as close as you can get to the opposite of Agile.

I fixed some major bugs during my refactor, and missed one the second time after I started over. So stuff actually broke in production because I took points off the board and "fixed" what worked to add back in dead code, variables that aren't used, etc.

In the process, I asked the EA how he wanted me to do this stuff, because I know that he makes up "standards" on the fly and whatever I do may or may not be what he was imagining. We had a tight deadline and I didn't really have time to guess, read his mind, get it wrong, and start over. So we scheduled an hour for him to show me what he wanted.

He said it would take fifteen minutes. He used the first fifteen insisting that he would not explain what he wanted, and besides he didn't remember how all of the code he wrote worked anyway so I would just have to spend more time studying his masterpiece and stepping through it in the debugger.

Being accountable to my team, I insisted that we needed to spend the scheduled hour on him actually explaining what he wanted. He started yelling and hung up. I had to explain to management that I could figure out how to make his "framework" work, but it would take longer and there was no guarantee that when it was done it would magically converge on whatever he was imagining. We totally blew that deadline.

When the .NET work was done, I got sucked into another part of the same project where they were writing massive 500 line SQL stored procedures that no one could understand. They would write a dozen before sending any to QA, then find out that there was a scenario or two not accounted for, and rewrite them all. And repeat. And repeat. Eventually it consisted of, one again, copying and pasting existing procedures into new ones.

At one point one dev asked me to help him test his procedure. I said sure, tell me the scenarios for which I needed to test. He didn't know. My question was the equivalent of asking, "Tell me what you think your code does," and he couldn't answer it. If the guy who wrote it doesn't know what it does right after he wrote it and you certainly can't tell by reading it, and there's dozens of these procedures, all the same but slightly different, how is anyone ever going to read them in a month or a year? What happens when someone needs to change them? What happens when someone finds another defect, and there are going to be a ton of them?

It's a nightmare. Why interview me with all sorts of questions about my dev skills if the plan is to have me copy and paste stuff and carefully avoid applying anything that I know?

The people are all nice except for their evil XEB (Xenophobe Expert Beginner) EA who has no business writing a line of code, ever, and certainly shouldn't be reviewing it.

I've tried to keep my sanity by answering stackoverflow questions once in a while and sometimes turning evil things I was forced to do into constructive blog posts to which I cannot link to preserve my anonymity. I feel like I've taken a six-month detour from software development to shovel crap. Never again. Lesson learned. Next time they're not interviewing me. I'm interviewing them. I'm a professional.

Holy fuck I did it. I convinced my non tech manager not to do code QA after he brought the whole system down approving things without testing them and getting devs to make changes that caused bugs. Don’t get me wrong he threatened to fire me twice during the conversation but I dunno…I think I’m just about ready for my second dev job anyway ¯\_(ツ)_/¯.

I'm going to kill management.
After a serious migration fiasco at one of our biggest costumers the platform was finally usable again (after two days instead of 10 hours) and, of course, users started to report bugs. So good old po came in ranting that we as qa did a horrible job and basically tried to fault us for a fucked up update (because we produced user pain, which of course not being able to log in didn't do). Among the issues: If the user has more than a hundred web pages the menu starts looking ugly, the translation to dutch in one string on the third submenu of a widget doesn't work and a certain functionality isn't available even if it's activated.
Short, they were either not a use case or very much minor except for that missing function. So today we've looked through the entire test code, testing lists, change logs and so on only to discover that the function was removed actively during the last major update one and a half years ago.

Now it's just waiting for the review meeting with the wonderful talking point "How could effective QA prevent something like this in the future" and throwing that shit into his face.

I mean seriously, if you fuck shit up stand by it. We all make mistakes but trying to pin it on other people is just really, really low.

Have any of you already felt that you really like what you do (coding, of course, among other things), but you hate "the place(s)" where you work, specifically some of the people from there...?!?!?

It's 9AM, you already got your coffee, is comfortably sat, with your precious headphones, all ready for some gorgeous lines of code to gain life... but...

... your coworkers are arguing cos one prefer braces when using an single-line if statement, the other not...

... another one is discussing about how bad he's paid after discovering that a dev (at the same "level") receives more...

... the coordinator comes to convince you that the manager is not good, has not all the needed "certifications", and vice versa ...

... the designer didn't like the UX's work, and this is just an enough reason for a BIG gossip with the rest of the team (or even with people from other teams) ...

... the QA complains all the time about everything: the testing environments are a shit, the other QAs are a shit, the system is a shit, his life is a shit (even though he has not yet realized it) ...

Sometimes I miss that time when I got into the coding universe at home, giving my first steps and was creating things all the time... against the toxicity we find in a lot of enterprise "habitats"...

A discussion about writing tests for frontend applications.

Context: my frontend coworkers don't write tests, at all. Yeah, really. Our testing process is very manual. We test manually when developing. We test manually when reviewing code. After merging, the application is deployed to a staging server and the design team does a QA Sprint. Lots of manual testing and some bugs still crawl by.

So I decided to start pushing my coworkers to start writing tests. One of the reasons I constantly hear them say to not write tests in the frontend is: "It's not worth the time, because design keeps changing, which means we have to take time to fix the tests. Time that we usually don't have."

I've been thinking about this a lot and it seems to me that this is more related to bad tests than to tests in general.

Tests should not break with design changes (small changes at least). They should test funcionality, not how things look. A form should not break if the submit button's style changes, so why should its tests fail? I also think that tests help save time, as they prevent some back and forth because of bugs.

Writing good tests is the hard part. Tests that cover what's really important and aren't frail and break with things that shouldn't break them. What (and how) should we test? And what shouldn't be tested?

Writing them fast is another hard thing. Are you doing it right if they take more time to write than the actual code?

What do you think about this? Do you write tests for your frontend applications? What do you test? How much time do you spend writing tests? What are your testing tools/frameworks?

When your week has been so busy and exhausting you remember at 1PM Friday you have a deadline for Monday morning and force yourself to do a weeks worth of work in 4 hours and deploy it on a Friday without QA testing!

To future me - I apologise for Monday’s headaches.

nice landing bro!

Started work: 9:30am
Finished work: 9:30pm

Finally finished my "basically done" ticket from two days ago, though I'm still not sure if it's behaving correctly. It deals with the Apple wallet and iPhone notifications, and all I have is an emulator, so. 😕 Things work as expected maybe half the time? and idfk why. I'm going to leave the actual testing to QA since they have actual iPhones and it'll run on staging on actual servers with actual connectivity and actual pushes, so maybe then things will actually make sense. Until then? So done.

Started drinking: 9:30pm
Finished drinking: TBD

<media lyrics="I don't know what the fuck just happened but I don't really care, imma get the fuck up outta here. Fuck this shit i'm out" />

Just joined a new team at the organisation as senior dev.

Team lead keeps singing about how we need unit testing and good standards.

I implement domain pattern on the backend supported by unit tests.

It passes QA and then get an earful about the code not being 'restful'. What does that even mean?

Well, it matters not since team lead changes the whole feature in the release branch and all unit tests obviously fails. Builds start to fail.

The solution? Comment out all unit tests. In the sprint retro, we hear the same old adage 'we need 80% code coverage'

Do as i say, not as I do. FML.

Today, I left the world of QA testing. I start a new job in designing a DevOps system on Monday! Yay!!!

I just love how liferay keeps finding ways to surprise me...

Customer: need to fix this security issue
me: ok
me: fixed. Testing locally. Works 100%.
Me: testing on dev server. Works 100%
qa: testing on dev server. Works 100%
me: all good. Deploying to preprod
customer: it doesn't work
me: testing preprod - it doesn't work.
Me: scp whole app to local machine. App works 100%.
Me: preview loaded liferay properties in preprod via liferay adm panel. All props loaded ok.
Me: attach jdb to preprod's liferay to see what props are loaded. Only defaults are used [custom props not loaded according to jdb]

me: is there some quantum mechanics involved..? Liferay managed to both load and not to load props at the same time and the state only changes as it's observed...

Management Double standards...
At a previous employer, the manager had me doing some QA testing for a updated version of some customer facing UIs. I spent 3 days constantly testing, except for my lunch break.
Every bug that I found I sent to a Sr dev.
Now this Sr dev was a coding savant. I mean awesome coder, but he had the personality of a rat and snake combined. If he wasn't coding he was brown-nosing the manager, talking about how he was doing all the work, or trying to rat on us other devs.
Anyway this dev has spent the 3 days of bug fixing alternating between watching videos and fixing bugs. Don't know what the videos were, don't realy care. I do know that he did not like to be disturbed while watching them...
On the third day, on my lunch break, I decided to watch two fifiteen minute videos on VSTS feeds and linking node packages.
As soon as I started Sr dev came over and asked me if I was focused on the teams priorities. I told him that it was my lunch break and since this was related to an upcoming sprint I thought it was worth it.
This S.O.B. goes full out hissy fit. He was flat out throwing a tantrum like my small daughter would. He made such a noise that my manager walked over and asked what was going on.
This shitbag Sr dev smirked at me and asked to speak to the manager in his office. When the manager called me over I knew what was up. I was lectured on not focusing on the teams priorities. I tried to explain that the videos were relevant to an upcoming sprint but was shot down. When I brought up the fact that the Sr dev was watching videos, the manager told me flat out that he didn't care. I was mad and told the manager that this was bullshit. All the manager cared about was keeping the Sr dev happy. I was told to "treat <shithead sr dev> with respect or else".
It was at that time I decided to look for another job. Less than a month later I left, for a much better paying job with awesome benefits. Sr dev acted like he was hurt I was leaving. Manager couldn't have cared less.
When some others on the team heard what he did, they started looking for work elsewhere too.
A month after I left another Sr dev on the same project left. At the same time a BA and QA tester demanded to be put on another team or else they would leave.
Manager started out with a team of 6 was left with only two people.
When the last one left, manager had the nerve to ask me why I didn't let him know anyone was unhappy. I told him if he cared so little for me, why would I think he care about them.
Ultimately, leaving was one of the best things I could have done.

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 corner

😔😔😔😔😔

I spent two days in a row fixing chairs at work because our whole dev team was waiting for issues (which means helping QA team and playtesters testing the whole game).

Just when everyone left and Im standing up to go as well a playtester comes up with a release breaking bug in the handwriting recognition code...
Since this game is build for a charity which will release it in a country at war we cant push the release date.

Guess who is making overtime trying to fix this bug?

Murphy's law is completely true.

Deployed my own software the very first time on a customer system on monday.

Today I'm at a job college class when my boss calls me: "...Hey yeah (unrelated) (yadda yadda) the software does not function for anyone").

I fucking knew it.
We don't have a proper project planning nor a real project manager/lead, we don't do QA, and now it's gone to shit.

I did my own testing extensively on monday & Tuesday, everything looked alright and worked like a charm.

I'm looking forward to the weekend already...

tl;dr - My company makes me pass around code over email. Is this normal?

How we fix bugs at my company.
1. Simulate bug in dev env (ok, cool)
2. Get the required code from svn and make changes locally (so far, so good)
3. Deploy changes in dev env and test (yeah!)
4. Take screenshots of fix in action along with the files you've changed and mail it to the respective leads (really? send code via mail?)
5. Keep changing your fix based on feedback and keep repeating above steps (what!)
6. Once approval mail comes, check-in your code in the svn branch for deployment and testing in the test env (QA team)

My question to you fine folks is, is this normal? Is this how most companies work? Passing around code over e-mail? Where the different versions of your fix are just attachments in emails. Or have I committed a sin by being a part of this heinous act?

I was asked to fix a critical issue which had high visibility among the higher ups and were blocking QA from testing.

My dev lead (who was more like a dev manager) was having one of his insecure moments of “I need to get credit for helping fix this”, probably because he steals the oxygen from those who actually deserve to be alive and he knows he should be fired, slowly...over a BBQ.

For the next few days, I was bombarded with requests for status updates. Idea after idea of what I could do to fix the issue was hurled at me when all I needed was time to make the fix.

Dev Lead: “Dev X says he knows what the problem is and it’s a simple code fix and should be quick.” (Dev X is in the room as well)

Me: “Tell me, have you actually looked into the issue? Then you know that there are several race conditions causing this issue and the error only manifests itself during a Jenkins build and not locally. In order to know if you’ve fixed it, you have to run the Jenkins job each time which is a lengthy process.”

Dev X: “I don’t know how to access Jenkins.”

And so it continued. Just so you know, I’ve worked at controlling my anger over the years, usually triggered by asinine comments and decisions. I trained for many years with Buddhist monks atop remote mountain ranges, meditated for days under waterfalls, contemplated life in solitude as I crossed the desert, and spent many phone calls talking to Microsoft enterprise support while smiling.

But the next day, I lost my shit.

I had been working out quite a bit too so I could have probably flipped around ten large tables before I got tired. And I’m talking long tables you’d need two people to move.

For context, unresolved comments in our pull request process block the ability to merge. My code was ready and I had two other devs review and approve my code already, but my dev lead, who has never seen the code base, gave up trying to learn how to build the app, and hasn’t coded in years, decided to comment on my pull request that upper management has been waiting on and that he himself has been hounding me about.

Two stood out to me. I read them slowly.

“I think you should name this unit test better” (That unit test existed before my PR)

“This function was deleted and moved to this other file, just so people know”

A devil greeted me when I entered hell. He was quite understanding. It turns out he was also a dev.

I just auto charged myself because I forgot I tested my 7 day trial in production last week

🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡🤦‍♂️🤡

How illustrators from undraw.co sees QA :D

How to delete 16 days of commits 101 🤯:

First of all, me and my class (computer science in college) were working on a project for around 12 weeks, our “client” is one of our teacher and we literally just finished today to work on the project since our degree terminal projects are starting next week.

So now there's this guy in our class who kinda has the reputation to be stuborn and clumsy; he’s going to do his assigned task, commit, push it and put his task into QA (which is just peer evaluation and testing nothing really complex) and then when we try his functionality and finds out it isn’t working, we tell him and the only thing he always answers is : “but it works on my machine” and then we will need to explicitly ask him to be sure he has all the latest changes (database and codebase) and to see if it still works on his side since it doesn’t work for anyone else.

This actually happened quite a lot in these 12 weeks and you can definitely imagine that of course it would definitely not happen again today when we thought we were finally done with this project…

So another teacher gave us an assignment to create a development environment for our big project so we could try out Docker instead of virtual machines, he made GitHub Classroom repos with a minified version of our project and up to this point everything is fine and clear. That is until 3 hours ago, that our little clumsy friend somehow pushed his Docker related files on the main project, maybe he was trying his Docker setup on the real project no big deal you know EXCEPT IF HE HADN’T NOT PULLED SINCE 16 DAYS 😤.

He was doing maintenance on another project so I can maybe understand but gosh how did he not see the big warning of Git that he wasn’t up to date with master ? And yes we only have a master branch bear with us but hopefully we were able to create a new branch with the up to date project and then merge master.

A couple of us had a gut feeling that this guy would do something that would break the whole project right before we ended, turns out we were right 😅

Our project at work goes live in 3 weeks.

The code base has no automated tests, breaks very often, has never had any level of manual testing

will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.

We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.

Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.

We have no testing team, or qa team of any sort.

Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.

We don't use any file streams so everything is just shoved in the buffer on the server.

Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.

No one looks at the pull requests, they just click approve so they may as well push directly to master.

Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.

I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.

Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.

No one there understands css properly. Or javascript.

Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.

Our customer facing fe app is not dry because no tests so it was decided it was better this way.

Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.

Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.

Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.

I just love PMs that wait until an hour before I'm supposed to leave and come and say, "Hey, we need you to do this thing right now. We're doing performance testing in QA this evening." And then take 45 minutes to get the information to me, without telling me which database or schema. Like, did you just find this out, or have you known this for the past week, and are just now telling me?

Me: Let's implement this integration test suite in Python since it has got plenty of rich libraries for accomplishing our goals.
Client: Let's use Node.js instead.
Me: With Node.js, we'll need to handle a lot of it's inherent stuff like asynchronous code flows, promises, etc. That's not what we primarily want to achieve.
Client: Let's use Node.js.
Me: Okay. What potential advantages do you see with Node.js?
Client: Umm.. let's just use Node.js?
Me: FML

This isn't a funny rant or story. It's one of becoming increasingly unsure of the career choices I've made the path they've led me down. And it's written with terrible punctuation and grammar, because it's a cathartic post. I swear I'm a better writer than this.

The highlights:
- I left a low-paying incredibly stable job with room to grow (think specialized office worker at a uni) to become a QA tester at a AAA game studio, after growing bored with the job and letting my productivity and sometimes even attendance slip
- I left AAA studio after having been promoted through the ranks to leading an embedded test tools development team where we automated testing the game (we got to create bots, basically!) and the database, and building some of the most requested tools internally to the company; but we were paid as if we were QA testers, not engineers, and were told that wouldn't change; rather than move over or up, I moved out to a better paying, less fabulous web and tools development job for a no-name company
- No-name company offered one or two days remote, was salaried, and close to home. CTO was a fan of long lunches and Quake 3 Arena 1-2 hours at the end of every day. CTO position was removed, I got a lot of his responsibilities, none of his pay, and started freelancing to learn new skills rather than deal with the CFO being my boss.
- Went to work as a freelancer for an email marketing SaaS provider my previous job had used. Made loads of money, dealt with an old, crappy code base, an old, cranky senior dev, and an owner who ran around like the world was on fire 24/7; but I worked without pants, bought a car, a house, had a kid, etc;

Now during ALL of this, I was teaching game dev as an adjunct at my former uni. This past fall, I went full time as a professor in game dev. I took a huge pay cut, but got a steady schedule (semester to semester anyway) and great benefits. I for once chose what I thought was the job I wanted over more money and something that was just "different". And honestly, I've regretted it so much. My peer / diagonally above me coworker feels untrustworthy half the time and teaches the majority of the programming courses when he's a designer and I've been the game programming professor for 8 years (I also teach non-game programming courses, but those just got folded into the games program...); I hate full-time uni politics; I'm struggling with money for my family; and I am in the car all the time it feels like. I could probably go back to my last job, which had some benefits, but nowhere near as good; my wife doesn't want me back to working in the house all the time because that was a struggle unto itself once we had a kid (for all of us, in different ways); and I have now less than 24 hours to tell my university I want to not pursue longer term contracts for full-time and go back to adjunct next Fall (or walk away entirely), or risk burning a bridge (we are reviewing applicants for next year tomorrow, including my own) by bailing out mid-application process.

I'm not sure I'm asking for advice. I'm really just ranting, I guess. Some people I know would kill to have the opportunities I have. I just feel like each job choice led me further away from a job I liked, towards more money, which was a tradeoff that worked out mostly, but now I feel like I don't have either, and I'm trapped due to healthcare and 401k and such. Sure, I like working more with my students and have been able to really support them in their endeavors this semester, but... that's their lives. Not mine. The wife thinks I should stay at the university and we'll figure out money eventually (we are literally sinking into debt, it's not going well at all), while most people think I should leave, make money, and figure out the happiness factor once my finances are back on track and the kid is old enough to be in school.

And I have less than 24 hours it feels like to make a momentous decision.

Yay. Thanks for reading :)

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`”

🤦🏻‍♀️

Our employee management system, for some reason, stored Testlists (I work in QA) linked to the user accounts that created them. Now after an colleague who worked there for five years left pretty much all our data was suddenly down the drain and nobody backed the fricking server up because, hey, whats the fun in that. Now all the tests need to be rewritten and other than the whole gui test automation of our product, maintenance of the same for another product, manually testing dev issues and training my new code monkeys to frickin not commit non working code to the trunk I have now also "Make a better Employee management system" (roughly translated those are the specs I've got) on my plate... I can remember back to the care free days of just before my boss asked me if I wanted to try to automate some of the test cases... How did I ever survive this paralyzing tranquility. Ha, surprise.
!rant, I fucking love the stress and juggling a shit ton of problems at the same time keeps ine on edge.

We use a third party paid company to produce a service and give ongoing support for it, which all our revenue streams depend upon. They are shit and their service is shit. Here's how my conversation about testing went today.

Me: 'hey X wrote an integration test project for the service. It shows the service is broken 50% of the time. We should give their team access to it and have them run it as part of CI'

Colleague: 'They are too shit to setup CI'

PM: 'we are stuck with them so there is no point. It is what it is'

Boss: just ignores me. Not even a reply.

Some days later

Head of QA: 'Hey Dev and QA are broken'

Me: 'because their service is broken. I made so and so suggestion before but it was rejected. We will just have to accept Dev and QA are broken 50% of the time'

Head of QA: 'no we cant'

Me: 'ok so we should setup the tests to run by giving them access'

Head of QA: 'No we shouldn't. The tests can only be used by us and if they break it tells us so we can act on it, or choose not to'

Me: 'We would not want to act immediately on all our revenue streams breaking? Yes we can reverse engineer their client and fix errors as they occur, or we could just have them run the tests and a team our company pays for can stop adding breaking changes to their own API every other day. Right now it has been broken for 2 weeks.'

Head of QA: 'in an ideal world we would have an internal team so you're wrong'

Me: :)

I really don't understand how they can come to such a conclusion. Am I missing something or am I surrounded by total fucking idiots?

Last sprint is a mess.

Working on three products that are related one with another a little bit.

1. Bug reports are coming in;
2. We fix it and give for QA to test;
3. QA starts testing and it doesn’t work;
4. Because another team updated something in product A and product B depends on it.

Repeat for straight 14 days

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 >_>

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.

We had 1 Android app to be developed for charity org for data collection for ground water level increase competition among villages.

Initial scope was very small & feasible. Around 10 forms with 3-4 fields in each to be developed in 2 months (1 for dev, 1 for testing). There was a prod version which had similar forms with no validations etc.

We had received prod source, which was total junk. No KT was given.

In existing source, spelling mistakes were there in the era of spell/grammar checking tools.

There were rural names of classes, variables in regional language in English letters & that regional language is somewhat known to some developers but even they don't know those rural names' meanings. This costed us at great length in visualizing data flow between entities. Even Google translate wasn't reliable for this language due to low Internet penetration in that language region.

OOP wasn't followed, so at 10 places exact same code exists. If error or bug needed to be fixed it had to be fixed at all those 10 places.

No foreign key relationships was there in database while actually there were logical relations among different entites.

No created, updated timestamps in records at app side to have audit trail.

Small part of that existing source was quite good with Fragments, MVP etc. while other part was ancient Activities with business logic.

We have to support Android 4.0 to 9.0 of many screen sizes & resolutions without any target devices issued to us by the client.

Then Corona lockdown happened & during that suddenly client side professionals became over efficient.

Client started adding requirements like very complex validation which has inter-entity dependencies. Then they started filing bugs from prod version on us.

Let's come to the developers' expertise,
2 developers with 8+ years of experience & they're not knowing how to resolve conflicts in git merge which were created by them only due to not following git best practice for coding like only appending new implementation in existing classes for easy auto merge etc.

They are thinking like handling click events is called development.

They don't want to think about OOP, well structured code. They don't want to re-use code mostly & when they copy paste, they think it's called re-use.

They wanted to follow old school Java development in memory scarce Android app life cycle in end user phone. They don't understand memory leaks, even though it's pin pointed by memory leak detection tools (Leak canary etc.).

Now 3.5 months are over, that competition was called off for this year due to Corona & development is still ongoing.

We are nowhere close to completion even for initial internal QA round.

On top of this, nothing is billable so it's like financial suicide.

Remember whatever said here is only 10% of what is faced.

- An Engineering lead in a half billion dollar company.

Probably a must read for QA!

I would love to see someone referencing this book in their application 😂

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 BETTER

How the hell some devs are releasing to production before passing to QA, Alpha testing, staging at least handle all type of errors and hide your API Keys.

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.

TLDR: Walmart bug 😠

As a dev, I know that bugs happen. But as a dev from a small shop that has many clients and very few devs, I absolutely despise when a large company with many devs has a bug in a product that millions of people use.

WalmartContacts.com. How many devs do they have? And how many dedicated to this 1 product? How many people in QA? (how many on DevRant... lol)
And yet I can't even place an order using their reorder functionality. Seems like they should have this shit down. Seems like they should have all their regression testing ducks in a row. Seems like they should at least show some kind of error message so the user knows what's going on. Instead, no message at all, just the final checkout payment page reloading when I submit leaving me to wonder if my card has been charged or not.

that moment when you implement a new feature for product
while testing, QA comes and says everything is working fine except its not working properly in IE8🤔🤔

You know what's the worst in doing software?
being assigned that dreadful project, that's doomed and cursed just from the start. Nobody dared to try or touch it for 7 years, because it's destined to fail. You will never get the resources to do it properly, all the constrains are just against you. Even as the requirements bars are lowered and lowered you barely make it. You keep testing that shit with QA for like 8 months past schedule. Then before release some core changes need to be done. It passes QA, but you somehow now it's just a ticking time bomb. It will just crumble and fall somewhere out there, if somebody dares to use that shit for real.

And so it goes.

Bug reports coming in.

So we called out our project manager and tech leader, who sent out an email last Friday to our bosses and stakeholders a project schedule - which we never knew about until we saw it in our inboxes - that showed we had already completed development and would go on to UAT testing by next week.

Except if you look at our agile board we have 3 weeks of dev tasks left and a couple more for testing and QA. Then our dev environment is shit because the deployment steps in TeamCity were not properly done by Dev Ops. And we still don't have a UAT environment created, much less tested out. And the project manager is about to go on a one-month vacation. Great!

So we replied back with all the aforementioned information (less the swearing and name-calling) and sent it out to the same recipients, including our bosses and stakeholders.

That was such a fun Friday afternoon.

Bug detected!

Wish me luck. Looks like the feature I am developing is going to be late because QA doesn't feel like following the estimates we agreed on. We already identified that development was going to be the longest part of this whole effort and that QA was going to be relatively easy, but but no. Because this is the day we have to be "code complete", they don't want to test a relatively simple feature. In fact we had to talk them into even starting testing on it today. Even though regression day is Monday and they are basically going to be done testing their last ticket this morning. Like what the fuck were they going to do for the next 7-8 hours? They don't write any documentation. There are no reports to do. There are no meetings. Did they just want a virtual day off?

Edit: they are literally playing with people's careers here. This is not the first time I have had something delayed by QA even though they agreed that it was simple to test and it was delivered with enough time to fucking test. Then I get in trouble because of late delivery.

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....

Get a ticket for a low priority bug, reported internally. Fix the issue mentioned in the bug.

Moves to QA environment, the original bug reporter tests and *passes* the ticket.

Moves to Staging environment, same exact individual then *fails* the testing. Cites totally new/unrelated changes that need to be made.

Apparently our the workflow is -

Code->QA->Staging->Requirements

Makes sense! :)

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. 😁😁😂

The feature was to parse a set of fairly complex xml files following a legacy schema. Problem was, the way this was done previously did not conform to the schema so it was a guideline at best, which over the course of many years snowballed into an anarchy where clients would send in whatever and it was continuously updated per case as needed. They wanted to start enforcing their new schema while phasing out the old method.

The good news is that parsing and serialization is very testable, so I rounded up what I could find of example files and got to work. Around the same time I asked our client if they had any more examples of typical cases we need to deal with, and sure enough a couple of days later I receive a zip with hundreds of files. They also point out that I should just disregard the entire old set since they decided to outright cut support for it after all if it makes things simpler. Nice.

I finish the feature in a decent amount of time. All my local tests pass, and the CD tests pass when I push my branches. Once we push to our QA env though and the integration tests run, we get a pass rate of less than 10%.

I spend a couple of days trying to figure out what's going on, and eventually narrow it down to some wires being crossed with the new vs. old xml formats. I'm at a loss. I keep trying to chip away at it until I'm left with a minimal example, and I have one of those lean-back moments where you're just "I don't get it". My tests pass locally, but in the QA environment they fail on the same files.

We're now 3 people around my workstation including the system architect, and I'm demonstrating to the others how baffling and black magic this is. I postulate that maybe something is cached in my local environment and it's not actually testing the new files. I even deleted the old ones.

"Are you sure you deleted the right files?"

"Duh of course -- but let me check..."

Tester says that selection to is dark when they selected a dark color.. 😑

Nothing destroys an ego quite like the cold, ruthless testing of your software by the QA team. I humble once more.

Did anyone ever felt that everyday is a loop? Mine is as follows

Bug Reported -> Try to reproduce -> Check on web -> Check iOS -> Check iOS 13.x -> Update or get hold of other simulator/devices -> Check iOS 13.x2 -> Fix it -> Now it breaks on Android -> Fix it -> Get it QAd -> QA feels their should be some more design changes -> Make him/her understand that what is priority for now -> Now everyone has started testing app and everyone have their opinion (designers are asleep at this point) -> Get all of the team in sync -> Start release -> 99% -> Some yells "wait" -> One more thing -> Sleep with nightmares -> Repeat

PS: We have a responsive web application that is also wrapped in Cordova for iOS and Android.

You cant be a recognzied as a good developer, untill you are a good tester or say produce least bug free code. You should do thorough testing of your code before handing over to QA. I lacked the skill of good unit testing, so have suffered alot in past years.

me: reviewing an old ticket relevant to testing a similar area of a ticket im working on as a developer

"QA Note

Please don't ask me where to find one of these, because I don’t know"

the retired QA who worked on this ticket also didn't write where to find the thing

well fuck me alright

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...

Thanks, plugin, that help text was incredibly...helpful?

Nazgul devs: tested it thoroughly, sir. It's mankind-proof. Safe for unleashing in warfare

QA testers: I'm about to end this wraith's whole career

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...

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 deal

Full round of QA, full round of internal testing, and the client still finds a bug nobody can reproduce.
🤷🏻‍♀️🤷🏻‍♀️🤷🏻‍♀️

I really miss having a team. Don't get me wrong, right now I do what I love and I got into a position where I can actually do Quality Assurance instead of just testing and I enjoy being able to actually change things instead of just repeating what problems there are and acting surprised when the same processes produce the same bugs over and over again but I really hope that we'll interview anything else than mouthbreathers soon.

I'm aware of the fact that QA isn't sexy and that few people who could become "Software ninja Rockstars" choose to go into it but can it be that hard to find at least two or three people who can write and read code at least on a junior level and understand how web protocols work? I get the feeling my entire branch is nothing but shit talkers clicking around blindly on pages.

I just want to exchange ideas again, come up with innovative tools, tweaking processes, learning from and teaching each other while we watch the entire operation get more and more efficient.

One responsibility of our team is general code QA for the entire dev department, DevMgr walks in our area yesterday…
DevMgr: “Has anyone reviewed the new WPF threaded model execution code?”
- everyone on the team responds “no”
DevMgr: “Can we get a review on that code ASAP? If it works as well as the developer said, it’s going to solve the lock up problems users are experiencing and automatic logging of errors.”
DevA: “Well, no amount of code is going to stop users from performing bad searches locking up the user-interface. That code is just a band-aid around the real problem. If the developers would write unit tests first …”
- rant about 5 minutes on unit testing that had nothing to do with why the DevMgr was here
DevB: “Yea, the code probably isn’t written to handle threads correctly. All the threading they’ve done so far is –bleep-”
DevMgr: “Oh, I wasn’t aware of that. Get me the results of the code review and if they don’t have unit tests, delete it from source control and let the developer know it’s not up to our standards.”
OMFG!! You have not even seen the code!
OK, DevA ..what the –bleep- does unit testing have anything to do with the user interface! You know the DevMgr is too dim to understand the separation of concerns. Shut your pompous ‘know-it-all’ mouth.
DevB…what the –bleep- have ever done in WPF? You manage the source control and haven’t written any C# in two years and never, ever written code for any significant project. Take that “handle threads correctly” and shove it up your –bleep-. Pompous –bleep-hole. Go back and watch youtube and read your twitter while the grown-ups get the work done.

I got assigned to work on a new project a couple of weeks ago. We got the POC code handed off from senior management, since he came up with the idea over the weekend. The project concept is hella exciting, but the dev manager and PO I have to deal with make life unbearable to say the least.

We have only 2 devs (including me) and 1 QA on this supposedly very important project. Of course, management announced the project to the clients already, so now we have to deliver ASAP cause it adds “sizzle”.

The MVP deadline is... no one knows when, either July 30th or September 1st. The MVP requirements are... unknown. I swear if someone saw the list of tasks and issues attached to “MVP” Epic, they would call us nuts trying to fit it all in.

To make things better, each PR requires 2 reviewers, so we end up adding manager as a reviewer just cause we need him to hit that “approve” button. So in attempt to make life easier, we requested to have a third developer. We are getting another developer, but that guy doesn’t know how to unit test a pure function...

Current priorities are... unit testing with coverage of 95% and if we want to refactor code, we have to add area to the list in a Google Doc. As a result, we are not tackling big things like risk of SQL injections not to mention big features like i18n (5-6 languages to support by the way and yes, it’s part of MVP as well as SSR no one knows why). Currently, I spend 2-3 hours a week in calls with the team just to figure out what the hell MVP is, what we have to do and why we have to do it. Last time we spent an hour refining 1 spike and breaking down one story into 3.

Oh, we also don’t have a deployment plan, not even to test environments since DevOps team was not aware of this project at all. Thus, QA cannot create any test suites and have to test everything manually which eats a lot of their time.

This whole project is a big hot mess and I’m considering leaving it all together especially since I’m working on two squads at the same time. I love the project, I love the idea, but management makes it unbearable, so I’m not even motivated to work on that.

*Repost of my own accidentally deleted post*
A Short story that i made on an Android component
===============================

Once upon a time there used to be a ViewPager who was not able to load a Fragment UI.
All the ViewPagers in town can properly load the Fragrant UI but this one was little different.

He wanted to be more then just a ViewPager. He used to see an Activity that can load anything. He was inspired from the Activity and wanted to be like the Activity but his destiny made him just a ViewPager.

So he refused to cooperate. He started to protest silently, No log, nothing.

Everyone assumed this ViewPager have a bug in it. but he was planning something really big that will left everyone in shock and awe moment.

He was planning to rise against the evil 😈 developers who continuously making him to load Fragrant UI

He assembled the biggest army of the bugs that humanity ever seen to counter the developers.

He distributed these bugs in all over the developer's code to make them fire from their work.

Even he taught bugs to not caught in QA testing but appear in production randomly.
So they silently started going into production

And then chaos is erupted all around the world, bugs started to surface and interrupted the daily life of humanity.

In this chaos the ViewPager RAISED!
And took over all the base classes.

ViewPager was unaware of few facts. this unnecessary rise in his power made whole system unstable

Without the base classes the system finally collapsed and then ViewPager as well with the system.

This was the end of everything for the ViewPager but he was satisfied as he lived the life he always wanted

THE END

I had a tight deadline so what I did to finish the feature was to cut corners by not writing optimized code and not doing enough dev testing to ensure the feature works.

End of today, I've moved the ticket to QA.

My iOS app is going under QA and Security testing this week. This'll be interesting.

A customer asks for a change request or a bug fix and it results in creating a ticket for that.
It's the process and how it works in most places but after you finish with the task and fix the same customer who provided you with the requirements will request that you share the steps on how to test the fix or the feature.
I'm not speaking about the data preparation or required configuration. I mean a step-by-step instruction on how the tester/QA will test it.
It's driving me mad!! So a way to counterplay this stupid requests, I provide the happy path and what to expect. And in case, they stumbled on a bug later in production, I can easily say "It was approved by your testing team and that's a new requirement ;)"

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?

Companies that do not do uat or internal testing in QA. Test in prod. Really bad. Really bad.

y'know, preparing for a colleague's vacation is a lot like QA testing. you prepare for all likely scenarios, but the moment they're out the door that exception with 0.0001% likeliness of occurring comes to bite you in the ass

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!

They need to make a drug that makes quality tests interesting.

But such a drug would have the side effect of making paint drying look like monkeys blowing up racecars.

Our QA is acting like a customer, or even more... Pushy, demanding, some times rude... you name it

On the flip side, we have a real (cruel) world scenario in testing. Not too bad I think?

Got designs on Wednesday afternoon. Final changes on Thursday and they expected me to work all weekend because they were lats for designs I asked 1 month ago for QA and testing. Not my fucking problem.
And not working on a weekend.

And today got told that components were missing and they needed animations. No fucking duh

So, I encountered a classic case of the infamous "it works on my machine" excuse today. 🤦‍♂️ Seriously, folks, can we please put an end to this lazy and unprofessional behavior?

Picture this: I had just completed a feature in my code and passed it on to the QA team for testing. Confident that everything was running smoothly on my local environment, I expected a smooth sailing experience. But boy, was I wrong!

The QA team began testing the feature on different environments, and that's when the chaos ensued. What worked seamlessly on my machine seemed to transform into a monstrous bug fest on theirs. Panic set in, and I couldn't help but feel a mix of embarrassment and frustration.

Lesson learned: testing code thoroughly across various environments is crucial. No, seriously, it's an absolute must! That "it works on my machine" excuse is just a ticking time bomb waiting to explode in your face.

From now on, I pledge to dedicate more time to thorough testing and consider the diverse environments our code will encounter. Let's save ourselves and our colleagues the headache and embarrassment caused by such oversights. Together, we can put an end to the reign of the "it works on my machine" excuse once and for all!

Okay, this time it's BINGO game for software testers/QA....
C'mon, tell us your bingo score 😄

After three months of development, my first contribution to the client is going live on their servers in less than 12 hours. And let me say, I shall never again be doing that much programming in one go, because the last week and a half has been a nightmare... Where to begin...

So last Monday, my code passed to our testing servers, for QA to review and give its seal of approval. But the server was acting up and wouldn't let us do much, giving us tons of timeouts and other errors, so we reported it to the sysadmin and had to put off the testing.

Now that's all fine and dandy, but last Wednesday we had to prepare the release for 4 days of regression testing on our staging servers, which meant that by Wednesday night the code had to be greenlight by QA. Tuesday the sysadmin was unable to check the problem on our testing servers, so we had to wait to Wednesday.

Wednesday comes along, I'm patching a couple things I saw, and around lunch time we deploy to the testing servers. I launch our fancy new Postman tests which pass in local, and I get a bunch of errors. Partially my codes fault, partially the testing env manipulating server responses and systems failing.

Fifteen minutes before I leave work on the day we have to leave everything ready to pass to staging, I find another bug, which is not really something I can ignore. My typing skills go to work as I'm hammering line after line of code out, trying to get it finished so we can deploy and test when I get home. Done just in time to catch the bus home...

So I get home. Run the tests. Still a couple failures due to the bug I tried to resolve. We ask for an extension till the following morning, thus delaying our deployment to staging. Eight hours later, at 1AM, after working a full 8 hours before, I push my code and leave it ready for deployment the following morning. Finally, everything works and we can get our code up to staging. Tests had to be modified to accommodate the shitty testing environment, but I'm happy that we're finally done there.

Staging server shits itself for half a day, so we end up doing regression tests a full day late, without a change in date for our upload to production (yay...).

We get to staging, I run my tests, all green, all working, so happy. I keep on working on other stuff, and the day that we were slated to upload to production, my coworkers find that throughout the development (which included a huge migration), code was removed which should not have. Team panics. Everyone is reviewing my commits (over a hundred commits) trying to see what we're missing that is required (especially legal requirements). Upload to production is delayed one day because of this. Ended up being one class missing, and a couple lines of code, which is my bad (but seriously, not bad considering I'm a Junior who was handed this project as his first task at his first job).

I swear to God, from here on out, one feature per branch and merge request. Never again shall I let this happen. I don't even know why it was allowed to happen, it breaks our branch policies. But ohel... I will now personally oppose crap like this too...

Now if you'll excuse me... I'm going to be highly unproductive and rest, because I might start balding otherwise after these weeks...

Started new internship last week, hired as dev but working qa till their next release goes up. See last 3 posts for some horror lmao. They... don't know how to use git but insist they do. 275MB single repo for entire angular frontend (no dependencies are pushed, few images) and "angular backend" (according to PM). Commits to master, bad commit messages, no testing except me on qa..... death

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?

The biggest things I’ve probably learned working on side projects are patience and planning. Side projects are a great place to hone your skills of negotiation with other people, but I’ve personally learned a great deal about the process of architecture, simply by doing side projects where I’ve experienced scoping and tooling problems later on. Being patient lends itself to getting better at planning. Working with others on side projects has given me insight into “when to hold em and when to fold em”...and again, this patience education has often helped me be a better planner for a multitude of tasks.

Spent most of this week busting my ass working on a hotfix that came out of nowhere with mega high priority. This annoys me greatly because the hotfix wasn't even fixing a bug, it was adding new functionality because certain customers were being blocked from testing without this specific feature. In my humble opinion, given that we release every weekend, hotfixes should be reserved for actual critical bugs. But anyway, as I probably could have predicted, the code got to QA and exploded. Literally nothing works.
This is what happens when you try to rush out features to satisfy customers. If you try to rush something that is late, you WILL make it later.
Meanwhile there's an issue I'm supposed to be fixing for our next release which goes out this weekend and I've had no time to even look because of this hotfix. And now it's the end of the day and I just feel worn out from stress, tomorrow will no doubt be similar.

Everyday Build releases for closed Alpha.

My PM wants our QA to do "Little bit Smoke testing" and "little bit regression" .

So I'm working on some communications app which bridges the main server/database with some equipment on the field. Now this equipment works in a redundancy pair: two cpus, A and B, both connected via ethernet, one active, the other standby/replicating and no comms on it. One obvious requirement is that when this equipment swaps the active cpus the comms app should switch as well. Fair enough, going with this into testing phase.

This guy, from qa, got some instructions from someone else:
1. Trigger the soft switch from equipment so that cpus got swapped.
2. Remove the ethernet cable from the standby unit.
3. Observe the communications.

And the test goes like: cpu A is active, B is standby. Switch is triggered, B becomes active, A goes into standby. The cable is pulled out from cpu B.

Test result: failed, no comms ever

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.

New customer request comes in early December. I bend over backwards to get the requested job completed in a week before everyone leaves for vacation, only to be told that we re delaying testing because appropriate QA isn't 'around'

The next six months is a set of meetings to plan the meetings where we test, which kept being rescheduled, resources being switched around on the customer end, and "refresher" meetings since its been weeks since we talked last.

Today I was told that due to a completely separate effort, this development piece would no longer be needed and the project is being canceled.

Just joined a new company and can only describe the merge process as madness.....is it or am I the one that is mad?!

They have the following branches:

UAT#_Development branch
UAT#_Branch (this kicks of a build to a machine named UAT#)

Each developer has a branch with the # being a number 1 to 6 except 5 which has been reserved for UAT_Testing branch.

They are working on a massive monolith (73 projects), it has direct references to projects with no nuget packages. To build the solution requires building other solutions in a particular order, in short a total fucking mess.

Developer workflow:

Branch from master with a feature or hotfix branch

Make commits to said branch and test manually as there are no automated tests

Push the commits to their UAT#_Development branch, this branch isn't recreated each time and may have differences to all the other UAT#_Development branches.

Once happy create a pull request to merge from UAT#_Development to UAT#_Branch you can approve your own pull request, this kicks off a build and pushes it to a server that is named UAT#.

Developer reviews changes on the UAT# server.

QA team create a UAT/year/month/day branch. Then tell developers to merge their UAT#_branch branches in to the previously created branch, this has to be done in order and that is done through a flurry of emails.

Once all merges are in it then gets pushed to a UAT_Testing branch which kicks off a build, again not a single automated test, and is manually tested by the QA team. If happy they create a release branch named Release/year/month/day and push the changes into it.

A pull request from the release branch is then made to pre-live environment where upon merge a build is kicked off. If that passes testing then a pull request to live is created and the code goes out into production.

Ahhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh it's a total mess. I knew when I took on this job it would be a challenge but nothing has prepped me for the scale of the challenge!! My last place it was trunk based development, commit straight to master, build kicks off with automated testing and that just gets pushed through each of the environments, so easy, so simple!

They tell me this all came about because they previously used EntityFramework EDMX models for the database and it caused merge hell.

I've been trying to push good practices at work, which includes migrating testing environment to vagrant.
Been trying to push it forward for months, and this week, a "genius"co-worker just started complaining we shouldn't overcomplicate and just provision a vm for testing for everyone to use, and boss agrees immediately!
Guess who'll have to maintain it whenever someone remembers to destroy it...

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!!! Thanks

so the new QA guy just raised 8 new tickets all of which are UI related

full stop is missing
buttons are slightly misaligned
need to add a space in between
etc

all these things can be fixed over a 5 minute call, but noooo he took screenshots, created report, created 8 separate jira tickets with the steps to reproduce and attached screenshots and sent the testing report to all the managers

is this normal in big companies? i feel like it's grossly inefficient and unnecessary

I work in a 20 person startup, the previous qa guy used to call me up directly and explains the issues, he only creates tickets for the things which couldn't be fixed in an hour, I usually fix most those things in under an hour and he provides sign off

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.

(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!!!!

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."

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.

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.

Well I consider motivation something that although is influenced by your "environment", you must seek for it. Even with the most boring/stressful/etc. situation, there must be something that makes a little change... For example, my first job was in QA testing, and I don't have anything against it, but it's simply not what I was interested... Initially my life was a little bit miserable haha, because most of my friends were already working as developers. At that time motivation was pretty low to be honest... My solution, I started learning about automation testing, that was more motivating and to be honest, a most interesting branch of testing. There I've found motivation to keep going, getting better and eventually gaining more experience to get a developer job.

Currently having very funny project lead, who gives on the spot estimates for 9 years old very pathetic quality code having Android app in security domain. Memory leaks, bad practices, typos, CVEs etc. you name it we have it in our source of the app.

Since 5-6 sprints of our project, almost 50% of user stories were incomplete due to under estimations.

Basically everyone in management were almost sleeping since last 7-8 years about code quality & now suddenly when new Dev & QA team is here they wanted us to fix everything ASAP.

Most humourous thing is product owner is aware about importance of unit test cases, but don't want to allocate user stories for that at the time of sprint planning as code is almost freezed according to him for current release.

Actually, since last release he had done the same thing for each sprint, around 18 months were passed still he hadn't spared single day for unit testing.

Recently app crash issue was found in version upgrade scenario as QAs were much tired by testing hundreds of basic trivial test cases manually & server side testing too, so they can't do actual needful testing & which is tougher to automate for Dev.

Recently when team's old Macbook Pros got expired higher management has allocated Intel Mac minis by saying that few people of organization are misusing Macbooks. So for just few people everyone has to suffer now as there is no flexibility in frequent changing between WFH & WFO. 1 out of those Mac minis faced overheating & in repair since 6 months.

Out of 4 Devs & 3 QAs, all 3 QAs & 2 Devs had left gradually.

I think it's time to say goodbye 😔

Skipping jasmine tests- especially ones on partials (not the controller). Seriously, QA has automated test suites to test UI functionality. If it takes 30 mins to write the code and 3 hours to write the tests... it may just not be worth the effort when there already is automated testing.

Ugh I hate skipping them but you know how to test the UI? Use the UI.

ingenuity

needed testing with 3 acccounts.

as a dev, I managed to do this with two screens, juggling here and there.

The QA guy, just installed 3 monitors.

I am like

(⊙＿⊙')(⊙＿⊙')

On a website, which is evolving, QA guy wants specification for website testing. Da, click anything you find, see if some thing changes. There is no specification which can compensate for incompetence. Aaaaaaaaaaaargh........

Started freelancing via agency as android dev for this client. The product is a kyc mobile sdk with a flow of around 20 steps for identification. My job is to maintain the sdk/fix bugs/add features and so on.

Communication seems to be so fucking terrible.

For example the product owner is not technical and sucks at defining issues.
QA sucks at testing and providing feedback. Backend sucks at documentation and seems to live in a parallel universe, swagger docs are outdated. Previous android dev whom I replaced gave me 2 hours of his time during his last month in the company, answered some questions and then left today (which was release day) with around 6 bugs hanging. Now because we are behind schedule the PO is grilling my ass so I would provide hourly estimates, while I dont even know the codebase yet since I spent maybe 30 hours on it in the last month.

What a clusterfuck. I feel like Im in a kindergaden where people are either lazy or incompetent. It seems that sweet gig of 40 hours a month will become much more hours or my output will be low :)

I just joined my company as a fresher in graduate developer, we will be going around in different teams over the course of next 6-7 months. My question is even though i joined as a " software developer" as of yet i am in a performance testing team, is it a good start or should i move to other team like development, QA testing etc ?

Someone from QA just randomly started asking me about API requests and responses today. For our backend which is not actually an API and changes all the time without notice. They just like, casually wanna know the contract of every endpoint on that.

So after having a heart attack thinking my coworker got spear phished I find out QA has decided to start testing our backend without telling us let alone asking us if it's a good idea.

I have a great chemistry with this coworker.

He lacks some depth of android knowledge but is always very interested in adding new google libs to the project, so we often discuss and come up with the safest, scalable solutions.

He is SE2 and I am SE1.

But one thing that is interesting about him is the way he gives estimations for the tasks. He takes usually that much amount of time that i would take, for a task, but he would quote half the time estimates.

the bosses usually come on the last days to check the feature demo, but QAs gets the first build when a task is completed. I have seen his first builds that goes to QA and most of the time, boy it has some amazingly stupid bugs.

dude would just put a util function, then run the build, if everything compiled, he would just give the build to QA directly. he wouldn't even check that the util function gave an expected output or not.

He is simply wasting QA time n efforts, and risking product quality by not testing enough, but he almost always gets a clean chit for this behavior just because he did the work super fast.

Dude is super cool and i don't envy him for his good luck, but rather think of him as an inferior dev. However bosses think of him as a better dev and my TL even once told me to "be like him"

So i guess this is how corporate works. I will try to apply this in my next role in current/next organisation.

Ohh......man. These manual tester wants everything from developer. They will simply clicking here and there in the application.

...tfw management shifts your priorities suddenly, for the next 2 days, and it requires that you completely alter your environment from what you have been building up for the last two weeks...

Not even funny when QA is testing a module -> they find a bug -> report the bug and forget rest of the functionalities that are actually working!

So my company is forcing me to take this ISTQB exams for testing and QA... after 10 months of employment.... "Thinks to self" I can wing this cant I?

I dislike qa's but I hate automated tests more

Why humankind why? People changing my code, commit without testing and QA is complaining cause the shit isn't working.

Some Back Story

Hey, so i was hired as a graduate developer in a company recently, its a rotation kinda thing so we get to work in different roles. At the moment i am in performance testing (which i like), here i am learning a lot of new things and like the working environment as well. After sometime i will have the freedom to choose a different role to move to but it is restricted to back-end mostly (that's what i went for during the interview) so i will have a choice between software engineering and QA automation, i can try both for sometime and then i will have to decide which part suits me more. Of course they will take my word but also take into account where i suit more according to my performance and factors like some others preferring the same thing.

Problem

Problem is that i have very limited knowledge of performance testing as a career simply because i think most people would prefer Development over testing, but this is a different kind of testing which i actually like. I just want to know if i have this choice then which career path makes more sense as i applied as a developer only but being a newbie i didn't know there were these many categories. A senior developer i know advised me to get all the knowledge i can take from performance but still go with software engineering and didn't explain his rational.

just want some advice for a newbie, i love the workplace.

I just want to say that although LLMs are great and are truly moving tech forward, testing anything related to them has become a hassle. And that makes me fear the amount of ‘you are testing llms wrong’ articles in Medium that will come up in the upcoming months.

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?

I've been working on an issue on and off for the past few weeks. The QA tests failed, so the ball is back in my court again. The data our analysts are testing from comes from a mysterious spreadsheet that no one knows where it came from, while my data is coming from some obscure database table. After asking around it turns out that the table hasn't been maintained for who knows how long, and nobody really knows what the data is used for... I feel like a freaking archaeologist.

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?

whenever I take extended brakes from reading whats on devrant the initial reopen of the app leads to a immediate crash. Android nougat.

Hola community!! Everyone going over this, please read this once and honestly answer my query.
I am on a probation at a startup. When i will be full-time, then the startup has promised me to provide CTC of 7,50,000(inr) i.e 10,000$ (usd).
Now I want to switch this startup company. Here are my reasons -
1. Less people, more work. - Well, that's what we call a startup. The tech team consists of 3-4 members only and we ourselves have to do the whole thing from end to end. This consists of designing the architecture, PR reviews, qa testing and coding ofcourse.
2. I see myself that I am capable enough to earn 1.5 times more than the above CTC. Also, all my friends are earning 2x the above ctc.
3. Also, there is no senior in the team except founder himself. This really seems awful as can't learn from anybody.
4. Also, i have plans of higher studying due to which i have to entrance exams. So i need to prepare them too. Switching to an established company can mean more money and less work.
Now, can anyone suggest me whether my reasons to switch are legit or vague??

How do you deal when you are overpromising and underdelivering due to really shitty unpredictable codebase? Im having 2-3 bad sprints in a row now.

For context: Im working on this point of sale app for the past 4 months and for the last 3 sprints I am strugglig with surprises and edgecases. I swear to god each time I want to implement something more complex, I have to create another 4-5 tickets just to fix the constraints or old bugs that prevent my feature implementation just so I could squeeze my feature in. That offsets my original given deadlines and its so fucking draining to explain myself to my teamlead about why feature has to be reverted why it was delayed again and so on.

So last time basically it went like this: Got assigned a feature, estimated 2 weeks to do it. I did the feature in time, got reviewed and approved by devs, got approved by QA and feature got merged to develop.

Then, during regression testing 3 blockers came up so I had to revert the feature from develop. Because QA took a very long time to test the feature and discover the blockers, now its like 3 days left until the end of the sprint. My teamlead instantly started shitting bricks, asked me to fix the blockers asap.

Now to deal with 3 blockers I had to reimplement the whole feature and create like 3 extra tickets to fix existing bugs. Feature refactor got moved to yet another sprint and 3 tickets turned into like 8 tickets. Most of them are done, I created them just to for papertrail purposes so that they would be aware of how complex this is.

It taking me already extra 2 weeks or so and I am almost done with it but Im going into really deep rabbithole here. I would ask for help but out of other 7 devs in the team only one is actually competent and helpful so I tried to avoid going to him and instead chose to do 16 hour days for 2 weeks in a row.

Guess what I cant sustain it anymore. I get it that its my fault maybe I should have asked for help sooner.

But its so fucking frustrating trying to do mental gymnastics over here while majority of my team is picking low hanging fruit tasks and sitting for 2 weeks on them but they manage to look good infront of everyone.

Meanwhile Im tryharding here and its no enough, I guess I still look incompetent infront of everyone because my 2 weeks task turned into 6 weeks and I was too stubborn to ask for help. Whats even worse now is that teamlead wants me to lead a new initiative what stresses me even more because I havent finished the current one yet. So basically Im tryharding so much and I will get even extra work on top. Fucking perfect.

My frustration comes from the point that I kinda overpromised and underdelivered. But the thing is, at this point its nearly impossible to predict how much a complex feature implementation might take. I can estimate that for example 2 weeks should be enough to implement a popup, but I cant forsee the weird edgecases that can be discovered only during development.

My frustration comes from devs just reviewing the code and not launching the app on their emulator to test it. Also what frustrates me is that we dont have enough QA resources so sometimes feature stands for extra 1-2 weeks just to be tested. So we run into a situation where long delays for testing causes late bug discovery that causes late refactors which causes late deliveries and for some reason I am the one who takes all the pressure and I have to puloff 16 hour workdays to get something done on time.

I am so fucking tired from last 2 sprints. Basically each day fucking explaining that I am still refactoring/fixing the blocker. I am so tired of feeling behind.

Now I know what you will say: always underpromise and overdeliver. But how? Explain to me how? Ok example. A feature thats add a new popup? Shouldnt take usually more than 2 weeks to do my part. What I cant promise is that devs will do a proper review, that QA wont take 2 extra weeks just to test the feature and I wont need another extra 2 weeks just to fix the blockers.

I see other scrum team devs picking low hanging fruit tasks and sitting for 2 weeks on them. Meanwhile Im doing mental gymnastics here and trying to implement something complex (which initially seemed like an easy task). For the last 2 weeks Im working until 4am.

Im fucking done. I need a break and I will start asking other devs for help. I dont care about saving my face anymore. I will start just spamming people if anything takes longer than a day to implement. Fuck it.

I am setting boundaries. 8 hours a day and In out. New blockers and 2 days left till end of the sprint? Sorry teamlead we will move fixes to another sprint.

It doesnt help that my teamlead is pressuring me and asking the same shit over and over. I dont want them to think that I am incompetent. I dont know how to deal with this shit. Im tired of explaining myself again and again. Should I just fucking pick low hanging fruit tasks but deliver them in a steady pace? Fucking hell.

"TDD is a waste of time" well so is making QA do way way more manual testing than needed.

I was finally able to set up a server with my coworker's help in our work office. After struggling trying to get CoreOS to work, I quit and just went with Ubuntu Server 16.04. It's a SFF PC that we had lying around. The purpose is to run applications in Docker containers for QA, demo, and performance testing. I can say it was truly a productive day...

I want to ask for your opinion guys, because I don't know if I am right or wrong.

So, some days ago, my brother sent me some code to check out for an automation that he does for testing purposes, since he's a QA (I am a programmer). He should be able to send XML data to a server and depending on the process that he tests, the data is different every time. I saw a strange thing, he hardcodes the XML tags and concatenates them with data which I find stupid. So I proposed him to use a template to generate XML data, because I think it's more flexible and easier, making data and presentation separate. That way if in the future he wants to start using JSON he could do it in no time. I made the code in a separate file which he imports and uses it's functions (they are two so no need for classes) and uses them to load the template and render it as he passes the data as a hash table. He insists that concatenating data and XML tags is easier and simpler and I can't wrap my mind how could that be true. I gave him an example in which the data structure for a process is changed and he have to open the file and change the XML tags or the structure and he still says that's simpler.

What is the right decision in this situation. Keep in mind that I simplified the process a lot and it actually involves sending the data and reporting the results, but they are not important here since I am talking only about generating data.

Just got hired for an internship duing QA testing for an insurance companies software team. I've been told their systems run mostly Java, SQL, php, JavaScript, and a little bit of Cobol. Any advice, tips, or things to look out for?

So we are 8 devs in our scrum team but 2 major refactors felll on my shoulders (initially they were supposed to be fairly simple tasks, but like that malcolm in the middle video 2 tasks became 10 tasks in the past month) and I have been working from 11 am till 4 am for the past 1 or 2 weeks. Just yesterday I worked until 7am. Slept only 4 hours... Trying to play it cool, since I asked for a raise 5 weeks ago and still waiting for answer.

I havent told anyone because partially its my own stubborness of wanting to learn things and not wanting to bother others with questions, but Im starting to loose it.

And all because my pushed initial features resulted in unexpected blockers so scrum team leaders had an all hands meeting and my newly appointed teamlead started shitting bricks.

Meanwhile all other devs pick a low hanging fruit tasks and sit around for 2-3 weeks while I have to do heavy lifting alone with some guidance from other devs.

We dont even have QA resources. We have 2 new hires who will be useful maybe after 3-4 months and we have 1 QA guy who judging by his output is working part time. Also same guy managed to take 2 weeks of vacation in the past 4 weeks.

So due to lack of QA and due to code reviews taking long time it takes over a week for code to be reviewed and tested and each time if a blocker happens I have like 2 or 3 days to rush until end of the sprint in order to fix the feature for upcoming release or I have to move tasks to another sprint and feel bad about spillover.

Imagine implementing something in 2 weeks, just to wait for another 1-2 weeks for changes to be reviewed/tested and now having to fix blockers. And then teamlead comes up to you with being surprises how come shipping of this is taking longer than 4-5 weeks? Dude, I did my fucking part in 1-2 weeks, its not my fault that other devs perform code reviews late and they dont even launch the app to test. Its not my fault that we have very limited QA resources and our only QA guy is not even testing out everything properly.

Seriously Im starting to fucking loose it. We are basically 8 devs in a team where 2 people are doing all the heavylifting.

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 respite

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!