Oh you're a frontend guy? Good, we need one of those.

Oh you're a backend guy too? Good, we need one of those.

Oh you're a security guy too? Good, we need one of those.

Oh you're a devops guy too? Good, we need one of those.

Oh you're a QA guy too? Good, we need one of those.

Oh you're an SEO guy too? Good, we need one of those.

"Well, sorry to say fullStackCraft, but we found your cloud architecture skills just a little too lacking for this position. We really need someone who can do frontend, backend, security audits, QA assessments, SEO, AND build scaling cloud architecture. Oh and while you're at it, can you turn fucking water into gold? We need that at our company too. You didn't get the position, but it'd be great if you could refer us to someone who is very advanced in fucking alchemy. Thanks!"

Absolutely toxic the way software people are treated I swear. The money may be the only good thing that is left.

I would absolutely love it if people would write their own stupid code instead of blindly mixing everyone else's mental diarrhea together and pouring the resulting mess into their bloody stupid IDE. At least then I could insult them properly. As it is, they're outsourcing their fucking stupidity to the lowest fucking bidder and then bragging about how quickly they get everything done. And management eats it up! No wonder everything is a slow, tangled, unmaintanable mess.

I can't fix much of anything because almost none of it is in my control. It's all autogenerated bullshit glued together with laziness and poor taste. "But Root, why is fixing this taking so long?" Gee, I wonder why. Maybe if someone had built it somewhere in realm of correctly the first time, it wouldn't have all fallen apart when someone looked at it the wrong way!

Seriously, there's no way this pile of stale fertilizer could have passed QA.

QA: Rapidly toggling between light and dark mode causes screen to flash unpleasantly

Dev: …

Manager: Hey Dev I need to do QA on this PR.

Dev: That PR is not finished yet

Manager: Well do QA now anyway, that way when it is finished it can be merged in right away since QA has already been done on it. It’s a project management technique called “fast-tracking” and it improves efficiency.

Dev: …

Send help..

The project we're currently working on:

- an angular codebase that's broken beyond recognition - nothing's working as it should

- user stories are estimated in hours, but estimations are treated as hard facts. Since the app is so broken, everything takes longer than usual and it's almost impossible to consider every potential hardship during refinements, therefore, we constantly need more time than we have estimated

- retrospectives (intentional plural here, since one time isn't enough) are used to discuss why we cannot manage to finish tickets within the estimations

- the design was made beforehand and is extremely inconsistent and inaccessible

- if you open a new ticket, you need to add a reason for why this ticket is needed - in addition to the ticket description..

- The moment you move a ticket to QA, the "Scrum Master" breathes down your neck, shoving new tickets in your face. Despite having to finish up the other two you're still working on

- multiple teams are working on the application, but - of course - communication is overrated.

I could go on, but I'm too tired..
We were supposed to help the client for a couple of months - we're close to a year now and still nowhere near done.

Joined this new team which said to have a rockstar teamlead with his right hand rockstar drummer senior dev. Turns out its just 2 socially awkward dudes who come into office once a week and all they care about is doing their own tasks and calling it a day.

The rockstar senior teamlead actually turns out to be an ex QA guy whos doing development only for the past 2 years and is unable yo explain what his code is doing and just starts rambling. I didnt expected spoon-feeding type of mentoring but man calling them and trying to get some advices makes me wanna die everytime. Fuck. My. Life.

I took matters into my own hands, Im doing pretty well actually and already am delivering, but man, if they dont give me a raise after probation ends then fuck this Im outta here. This is not what I signed up for.

These fuckers are pretentious egomaniacs who look good in their linkedin page but in reality are selfish narcissists.

Im getting tired of this fucking scrum team.

First of all let me introduce our backend team which takes 3 weeks to add one fucking column to database and in the end turns out they fucked up RabbitMQ RPC implementation so the column is not syncing with our app at all so now we have to wait 2 extra weeks until that will be working. Best part is that backend fucker who fucked up doesnt even feel like hes blocking a feature and would rather sit for extra few days and do nothing until he gets reassigned his pile of shit back to him than clean up his own shit.

Then we have business analytic who doesnt know how to define tasks properly so I have to record each grooming meeting so I would know what to fucking implement because he doesnt even bother to take proper notes. Which results in not fully defined tasks, which results in unexpected behaviours and MR's stuck in limbo for weeks.

Also lets not forget QA guy who doesnt even bother writing scenarios, I as an app dev have to write them myself just to be sure that fucker will test everything thoroughly.

Then we have fucking devs from consultancy agency who apparently have 6 years of experience (I have barely 2) and these fuckers are spamming me daily with the most basic questions. After each grooming they rush to assign themselves tasks which are not even defined properly yet and not even in this sprint, but fuckers are lazy so thy want to reserve easier tasks for themselves. Pathetic.

At least I have a decent senior on my team, but sometimes he patronizes me so much that I start asking me what I am doing in this team.

Fuck this shit, I asked for a 43% raise and if Im not getting it in 2-3 weeks im outta here. Fuckers.

I just don't get my coworkers. They tweak designs, they tweak functionality, but no task is made.

They just simply update designs in Figma, without notifying anyone or just msg me on Slack what to change...

How the fuck do you guarantee that all those tweaks will get reflected to the app? How do you guarantee I won't forget? How do you guarantee QA will test your stupid tweaks?

Ask me about that one time a motherfucking LOG STATEMENT caused the code to not work properly, breaking both the Test and QA environments, but failed in a way that made it maddening to figure out (in conjunction with the cloud-based hosting environment and the abomination that is centralized logging, which just makes EVERYTHING more difficult).

Actually, DON'T ask me about it, because it was today, it wasted most of my day, and I'm still salty as fuck about it.

when u break some functionality on prod as you and QA both missed a test case

This new job has more work than I can possibly complete in a day, week, or month. Deadlines pile up and I’m thoroughly exhausted all weekend. My mind feels lethargic and dull. People around me seem to be getting stuff done and I feel like I’m making too many mistakes and holding everyone back. Not sure I can stick with this job for the long haul to retirement. But freelancing absolutely sucks because nobody wants to pay you enough to feed yourself and it doesn’t scale to a full time salary for me. I simply don’t have the mental capacity to do the equivalent of four peoples’ jobs to design, code, QA, launch, and do all the digital marketing, advertising, writing, and maintenance for enough sites to make up my salary.

FML or how I made myself unhireable

TL;DR: Working as a QA.
Changed jobs.
New job sucked.
Left after three months.
Got laid off from the next one after 4 months (not my fault).
Got depressed.
Got a Dev job back in the first company.
Job sucks, cannot leave… (5 months in)

Full rant:
I was doing pretty well as a QA Enginner. Started with internship, then junior in company A, then big pay rise moving to company B, where I quickly got promoted to Senior. As I was nearing 3yrs of exp, I decided it’s time for a change, as things were getting worse project-wise and felt like I was regressing. Also I was constantly bombarded with offers of +50% of my salary I could easily land, while company offered 10%.

Moved on to company C. This is where it started getting rocky. I was told I would be working on this one project, strictly test automation, nothing exciting but an easy gig. However week in, I was told to work on this other project 50/50. This was a startup kind of thing. It was a nightmare. Only manual testing. Most tickets had only a vague title, no description, no requirements, nothing. How do one test something without any knowledge how it should work? Besides that, the project lead on the client side was aggressive sometimes.
The workload was immense - 4 devs, 2 of them doing heavy overtime, so the output was like 6 devs and half of a tester….
Despite raising the problems, nothing was going to change, nor I could switch projects. The job began to heavily affect my mental health. Decided not to prolong my contract and left after 3 month probation period.

Quickly landed a job in company D. As my burnout as a tester kept bothering me more and more I decided that this was going to be my last job as a QA and next one will be a Dev. You see, I never enjoyed the tester part, I always enjoyed the automation part more. The plan was to learn in free time and after 18-24 months start applying for a dev role to see if I can land one (switching inside D was not an option). All plans went to hell, as I was handed a one month notice by the end of my third month. A month before my wedding… I was told the company was having financial issues and was laid off with about 30% of people in the company (mostly new hires).

I got depressed. I wouldn’t get out of bed for a few days. I never thought something like this would ever happen to me. Standing by my decision I was applying for development jobs, but most recruiters seeing either only QA experience or my recent 3 and 4 month employment periods weren’t responsive. Applying for testing jobs was a bit better but still nothing like before C and D.

Since company B I stayed in touch with my former manager, and he kept telling me that a new team has taken over most of the shitty work, and they are now working on cooler stuff and have more coming. He encouraged me to come back, as he has always thought highly of me professionally.
Looking at my options, I could probably get another testing job with lower pay, maybe I could land a junior Dev with like 1/3 of my salary or I could go back. So in my dark time I have reached out to my manager and just like that he got me a Senior Dev position, same pay as in company D.

Finally what I wanted right? Yeah… As soon I as joined all the new initiatives were being dropped one by one, and backlog got flooded with bugs and sh*t again. Five months in I hate my job again. Cannot leave cause no one will hire me…

Where I made the mistake?
Shouldn’t leave B despite facing regression and being underpaid?
Shouldn’t leave C no matter what?
Shouldn’t come back to B?

I think the sleep deprived me is finally cracking under the weight of incompetent assholes.

We just launched a major project in some weird cocktail of Agile slapped with MVP and release to the wild in a waterfall, but it was premature, premature in the sense QA hasn't even finished their side of things, but because some fuck with with "manager" in their title decided they have burnt through the budget with incompetence and scrapped an entire element of the project and outsourced just so they could make a shittier version that doesn't even fucking work.

How hard do you want to fail before you will start listening to the people that now have to work around the fucking clock to clean up this horse shit of a mess.

I'm literally arguing over field mapping with multiple 3rd parties, when the fucking requirements state WTF this is suppose to look like. All because they didn't validate or test their own shit.

Why is EVERY FUCKING cock head in this industry a waste of space and cash! Is it really to much to ask for 1 fucking project to fucking go live that actually fucking works where I don't need to work 2 weeks straight (including weekends) after going live just to be sure that what shit does hit the fan isn't going to create a SEV 1 issue...

Sorry, I'm pissed at the incompetence of others I need to deal with on a daily basis. It's not like this field is insanely hard. A little attention to detail and self validation, verification goes a long way. But clearly that's a rarity.

Once this shit is stable and actually works, I'll be pulling out the mop to clean up half this shit just so it actually works.

Oof, I'm getting to old for this bullshit.

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

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

I fucking hate managers who go out spouting things have gone to shit and production is broken, when a single feature is missing from the application. It's your fault for not making sure the specifications were correct or not testing in QA before going to production! Just because one minor feature is missing does not mean production is broken you dimwit! It just means you suck at your job and we have to fix your fuck ups. It would also be really helpful if you morons accepted the fact that the teams want to do daily releases and continuous development, instead of having to deal with your insanity of pushing releases to a specific date so we have everything ready from marketing to Steve the janitor

Killing people is bad. But, there should be a law to allow killing people who don't write proper unit tests for their code. And also those "team leaders" who approve and merge code without unit tests.

Little backstory. Starts with a question.

What is the most critical part of a quoting tool (tool for resellers to set discounts and margins and create quotations)? The calculations, right?
If one formula is incorrect in one use case, people lose real money. This is the component which the user should be able to trust 100%. Right?

Okay. So this team was supposed to create a calculation engine to support all these calculations. The development was done, and the system was given to the QA team. For the last two months, the QA team finds bugs and assigns those to the development team and the development team fix those and assigns it back to the QA team. But then the QA team realizes that something else has been broken, a different calculation.

Upon investigation, today, I found out that the developers did not write a single unit test for the entire engine. There are at least 2000 different test cases involving the formulas and the QA team was doing all of that manually.

Now, Our continuous integration tool mandates coverage of 75%. What the developer did was to write a dummy test case, so that the entire code was covered.

I really really really really really think that developers should write unit tests, and proper unit tests, for each of the code lines (or, “logical blocks of code”) they write.

QA/stakeholder person: can you add the following links to the footer?
devs: sure. easy.
devs: oh wait, 3 of those links are 404. Are you planning to create those pages? or were those urls just a suggestion?
<crickets>
devs: ok well for now we'll leave those out.
stakeholder (a day later): hey these 3 links are still not in the footer!
devs: yeah we asked about that yesterday.
boss: the links are there now
devs (quietly): fuck you.

How to disconnect from work after working hours? Im working for the last 4 months as a mid level dev in this company. I mean Im able to problem-solve and do my work but sometimes I get so addicted to problem solving that I get worried and become obsessed, hyperfixated (especialy if Im stuck on something for lets say a couple weeks). It goes to the point where I work from home 12-14 hours a day just to figure out some bug in the flow.

Thing is, our codebase is large and when doing every new refactor/feature some surprises happen. I dont have a decent mentor who could teach me one on one or even do pair programming with. All i have is just some colleagues who can point me to right direction or do a code review from time to time. Thats it.

I dont know why I take this so personally. For example I had to do a feature which I did in 1 week, then MR got approved by devs and QA. After that during regression they found like 3 blockers and I felt really bad and ashamed. While in reality our BA did not define feature properly, devs who reviewed it didnt even launch the code and poke around in the app, and our team's QA tested only the happy scenario. Basically this is failing/getting delayed because of a failure in like 6-7 people chain.

However for some reason Im taking this very personally, that I, as a dev failed. Maybe due to my ADHD or something but for the next days or weeks as long as I dont find solution I will isolate myself and tryhard until I get it right. Then have a few days of chill until I face another obstacle in another task again. And this keeps repeating and repeating.

My senior colleague tells me to chill and dont let work take such a toll on my emotional/physical/mental health. But its hard. He has 7 years of experience and has decent memory. I have 2-3 years of experience and have ADHD, we are not the same. I dont know how to become a guy who clocks out after 8 hours of work done everyday. Its like I feel that they might fire me or I will look bad if I dont put in enough effort. Not like I was ever fired for performance issues... Anyways I dont know how to start working to live, instead of living for work.

I hate who Im becoming. I dont work out anymore, started smoking a lot, dont exercise. I live this self induced anxiety driven workaholic lifestyle.

Question for devs who work in large multi-team environments:

A) What is your code review process like? Does a senior review it once and then it's off to QA or do you have "levels" of approval?

B) If you're launching a feature that depends on another team how are you coordinating it? Do you just talk over a ticket and then hit merge and deploy at the same time or like what's your process like?

C) What CI/CD tool do you use? Also what code hosting platform do you use? Github/GItlab/etc.

D) Are you currently happy with the CI tool you're using? If not what are some common issues you're facing?

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 😔

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?

Triaging this project that's running on IIS makes me feel like my skillset is wasted on such banal garbage - while at the same time hoping nobody realizes what a mistake it was to put me on it because I have no idea how to troubleshoot or fix it.

I try not to be that guy who blames every issue on their tools but I can't believe some of these issues and respective fixes. Our QA was down for 2 months because I hadn't uninstalled a default module which prevents POST requests.

Writing my first code review. Even though it really is a nice review and I'm happy with the solution code, I still somehow feel like an asshole for each critique I make. Maybe it's unavoidable with code reviews / pull requests?

Issue: very long feedback loop. Code goes to a development environment, and manually gets deployed to a QA environment and then sometimes manually deployed to production. Sometimes features get cherry picked (yeah, this is very new to me) instead of applying something like feature toggles. Raising this issue up, and some manager 'DO WE NEED TO ADD ANOTHER STEP BEFORE PRODUCTION TO MAKE SURE IT'S THERE?!?!' .... what? You fucking numbskull! Weren't you listening! Someone said the feedback loop is way too long and you're suggestion is to add more steps?! HOW ABOUT REDUCING STEPS FFS!

Question about scrum in terms of developer/QA workflow. We have a problem in our team: basically when a dev submits an MR it needs to get 2 approvals from devs and then task is marked ready for qa. Now problem here is that qa takes 2-3 weeks to get to the task and when they do usually MR has merge conflicts and since QA are quite new-ish they have to wait for dev for conflicts to be resolved, ergo rendering the MR unable to be tested until dev resolves the conflicts.

Our teamlead proposes to solve this by forcing devs to rebase everyday (even if QA will get to working on the task 3-4 weeks later). Problem with that approach is that each conflict resolve removes approvals. So I had a situation where in 3 weeks I rebased like 15 times and 5 times I had resolve coflicts and because approvals were lost I had to annoy all devs and ask for reapprovals. And this is only with 1 MR. Now imagine all devs doing rebasing daily and spamming each other for reapprovals. Its not efficient.

Anyone could advice how to solve this issue?

What is the future scope of QA automation, is it good or should someone switch to Dev asap !?

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.

QA is annoying, imagine talking about the same thing a million times

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

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.

Best tools for QA that you use for web and app development? 👊🏻😉