This is a fun conversation I had:

Test Engineer: 😑 The test bench burst into flames.
Me: 😪😲 Do what now?
TE: 😐 The test bench burst into flames. It made a pretty impressive fire ball.
Me: 😮 . . . How are you so calm about this?
TE: 😐 Well it's not on fire now.
Me: 😶 Good point.
TE:😧 made me mad as hell though.
Me: 😕 why's that?
TE: 😬 Cuz I only had one damn step left in that test procedure and it was to turn the damn test bench off.
Me: 🤔 Correct me if I'm wrong but the test bench is off is it not?
TE: 😐 Well yeah.
Me: 🤔 and you caused it to be turned off by your actions no?
TE: 😕 . . . yeah . . .
Me:🤔 sounds like you turned it off to me.
TE: 😒
Me: 🙂
TE: 😐
Me: ☺
TE: 😑
Me: 😎
TE: 😐 but it won't turn on again.
Me: 🤔 do you have a requirement to be able to turn it on again after you turn it off?
TE: 😑 It's implied.
Me: 😐 not what I asked
TE: 😧 No not explicitly.
Me: 😎 sounds like you completed the test procedure.
TE: 😑
Me: 😎
TE: 😑
Me: 😎
TE: 😧 that's not how it works.
Me: 😎 doesn't it?
TE: 😑 No.
Me:😎
TE: *walks away* 😧😧😧
Me: *turns back to computer* well I was just trying to help YOU out 😒

I am the best at interpersonal communication.

Senior: Why did you refactor those ten files?

Junior: There was a method copy-pasted in every one of them, so I moved it to a utils class.

Senior: Don't you know we will have to test all of those changed classes again? Please, rollback!

Junior: ok.

... two days later ...

Senior: Why did you just copy-paste that method? Don't you know it's bad practice?

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.

overheard someone say "test driven development is essentially 'debugging a system into existence'"

.... And to be honest I can't disagree, it's quite an accurate description of TDD.

I might have posted this before. But I am going to post it again. Because emojis.

Me: 😁 Software lead I have finished coding the thing.
SL: 😀 Cool, good job. That is going to really help out the analysts.
Software Manager: 😐 hey I noticed you have coded a new thing and pushed it to integration.
Me: 😁 Yes.
SM: 😐 Well how do you know when it's done?
Me: 😑 . . . When you run it and it does the thing?
SM: 😐 Did you write test steps?
Me: 😕 Yeah . . . they're in the issue ticket.
SM: 😐 Yeah but how do you know those are right?
Me: 😕 Because I wrote the thing and the test steps?
SM: 😐 did you put any steps in our acceptance test procedure?
Me: 😕 No.
SM: 😐 why not?
Me: 😧 Because the acceptance test procedure tests requirements. There is no requirement for this functionality.
SM: 😑 Then why did you do it?
Me: 🤔 Because it was an internal request from the analysis team. There is no customer impact here.
SM: 😑 I really think we should write a requirement.
SL: 🤔 But what requirement is he going to attach this to?
SM: 😑 We don't have to attach it to a requirement. We can just test it once and remove it.
Me: 😒 SM, you know we never remove anything from the acceptance test procedure.
SM: 🙂 We do sometimes.
SL: 🤔 When was that I have worked here for twenty years and we have never removed a test from that document.
SM: 😑
SL: 😒
SM: 😑
SL: 😒
Me: 🤐
SM: 😧 I really think there should be an acceptance test written.
SL: 😧 Looks like you're writing an acceptance test.
Me: 😒 Alright as long as y'all're payin'. Shit I was just tryin' to save y'all money.

*acceptance test written and sent to peer review*

Peer: 😐 The requirement tested section doesn't have any requirements spelled out.
Me: 😅 No.
Peer: 🤔 Why?
Me: 😓 Because there is no requirement associated with this test.
Peer: 🤔 Then why are we adding an acceptance test?
Me: 😡 WELL AIN'T THAT A GOOD GOD DAMN QUESTION!?

My boss caught me out the other day. He asked which browser do we test on. In our documentation it's ff chrome and ie10. In reality it's not ie.

I opened ie for the first time in a long time the other day to find a crap load of bugs. Including the attached.

I curb procrastination by throwing in a random "sudo rm -rf --no-preserve-root /" to my test cases to see if I have unsafe evals. It's like Russian Roulette every test.

So today I got a call that an end user decided to try to be a developer. He built and ran a bulk edit script on his company's server.....

Without a scaled test....
As root....
From root....
Without backups....

How's this my problem again?

Oh right, it's not (yet)!

I was expecting a 4th interview this afternoon for a position as a fullstack elixir developer.

Got a response from the CTO.
'Even if you pass all the tests with success, we could not go further because you're a junior and we're looking for a senior'

Well, dude, you've seen me 3 times and didn't understand that I was a junior ? My CV is not enough explicit ? It's written at the top of it...

So after a motivation interview, technical test, technical interview and Phoenix framework interview, they only realized yet the plot.

Good luck for your seniors to pass their knowledge to other seniors.

One month ago. By email.

Boss: so, this client A has a problem with one of our devices and he believes that it's a bug in the software.

Me: all right then, what happens?

Boss: well, he says that the parameter P in the option menu does not changes the device's behaviour as it is supposed to. I'll forward you his mail. You will find attached an excell file with the results of his test performed with and without the parameter active.

Me: < read mail, read excell file > well, boss, his tests are performed in completely different conditions, how could he expect to infer a meaningful results from this?

Boss: damn, you are right. Send him a test plan and follow up.

Me: < send detailed test plan >

No answer in a week. Then...

Client: hi, there, I made this tests, I attached the excell with the results, can you check the software now?

Me: < read another bullshit filled excell file with none of the suggested test performed >
You know what? Just download the procedures you are using from the device and send them by mail, specifying the software version you are using so we can perform some tests here in the lab and get yo a solution asap.

No response. For a MONTH.

Super Boss: client A still has his problem, how could possibly be that it takes more than A FUCKING MONTH to solve his issue??

Me:...

micromanager: "Quick and easy win! Please have this done in 2-3 days to start repairing your reputation"

ticket: "Scrap this gem, and implement your own external service wrapper using the new and vastly different Slack API!"

slack: "New API? Give me bearer tokens! Don't use that legacy url crap, wth"

prev dev: "Yeah idk what a bearer token is. Have the same url instead, and try writing it down so you don't forget it?"

Slack admin: "I can't give you access to the slack integration test app, even though it's for exactly this and three others have access already, including your (micro)manager."

Slack: "You can also <a>create a new slack app</a>!" -- link logs me into slack chat instead. After searching and finding a link elsewhere: doesn't let me.

Slack admin: "You want a new test slack app instead? Sure, build it the same as before so it isn't abuseable. No? Okay, plan a presentation for it and bring security along for a meeting on Friday and I'll think about it. I'm in some planning meetings until then."

asdfjkagel.

This job is endless delays, plus getting yelled at over the endless delays.

At least I can start on the code while I wait. Can't test anything for at least a week, though. =/

Boss: I wrote some tests and there is a bug in your code but I cannot find it. Fix it
Me: Sure. I'm on it.

Narrator: 5 minutes later

Me: Boss, I found the bug. It's in your testcode...

Seriously... WTF?!

(before someone suggests that my code should handle all test cases... He tried to measure the time the program needed to response and fucked it up...)

It's official I just got a phonecall after my interview/2h test today!

I'm starting my first software developer job on Monday! 🤓🎉

.. so I'm back here finally after a few months as I thought I didn't belong , but now I do, yay ,

🙏🏼

-made a password-protected zip to backup my homedir
-launch the update to Fedora 28
-oh look Jessica Jones season 2 is available on Netflix

...

Some hours later

-Fedora 28 boots
-copy back my backup.zip
-shit what's the password already
-proceed to bruteforce the zip
-let's go back to Netflix while it's doing the job

...

Some hours later

-password: test
-proceed to self-fuck

Accidentally left a test line in an API method - the first line returned a 200 OK response.
It was a notification API for our payment portal, so when they complained our API didn't work our logs always said all was fine...

After an hour of listening to our help desk guys saying "everything in our logs says it's fine", I looked at source for 2 seconds, fixed the problem, went home, had a whiskey and went to bed!

I have a variable called 'stuff'. It's a test to see if my colleagues really read my pull requests.

I got a 9.8/10 for my programming test. I went to ask the teacher what the issue was. He showed me my test but there was no red mark anywhere. So I asked why, and he said it's because I used LINQ, and I couldn't use it because others students might not know it...

I bet you he doesn't understand it aswell...

Why the fuck do teachers take points off for coding style. Like really placing my open house brace on the same line as an if is what looks good TO ME. And breaking from a while loop with an inverted condition is nicer than a huge if TO ME. Fuck it I like the m_ for member variables too. And yes C++ usually names functions like someFunction, but I like how c# does SomeFunction. Like shit, it's personal I don't care that I lose 5points every test I do it just to say fuck you

Yesterday I received the API documentation from an external company. Over half of the endpoints are either wrong or send invalid data and even the given test requests are fucking failing.
It's a nightmare. We have to finish a website until friday and that company did nothing for 2 months and now we have 2 days left.
The sheer incompetence is too damn high.
My boss said it would have been much better if we had implemented the API on our own. Damn right.

I jump on an existing scala project.

git pull && sbt compile test

Tests are failing.

Me: "Hey team, the tests are failing."

Team member: "That cannot be. They were passing for the the last run."

Me: "Did you run them locally?"

Team member: "No, on Jenkins. It was fine."

I check Jenkins.

Me: "What do you mean it's fine. The last successful deployment was on the end of May."

Team member: "The Pull Request checker always went through successfully."

I check how our Jenkins tasks are configured. It's true that the Pull Request Checker runs successfully yet due to a "minor misconfiguration" (aka "major fuckup") the Pull Request Checker only tests a tiny subset of the entire test suite.

Team members were were fine if their Pull Request got the "Success" notification on bitbucket's pull request page. And reviewers trusted that icon as well.

They never checked the master run of the Jenkins task. Where the tests were also failing for over a month.

I'm also highely confused how they did TDD. You know, writing a test first, making it green. (I hope they were just one specific test at a time assuming the others were green. The cynic in me assumes they outsourced running the tests to the Jenkins.)

Gnarf!

Team member having run the tests locally finally realizes: "The tests are broken. Gonna fix them."

Wow. Please, dear fellow developers: It does not kill you to run the entire test suite locally. Just do it. Treat the external test runners as a safety net. Yet always run the test suite locally first.

~ Freelancer.com Week #1 ~

Project: I need someone to debug an application's code and review it. Budget 30 bucks.

Bid: I am an experienced developer I can probably review it in an hour.

client: Hi, need you to check if app is contains virus [link to scam website]

me: sure, download supposed "social Bitcoin miner" and run some AV tests...8+ positive flags for a Trojan virus.

>Me: It's a Trojan virus mate it's not legitimate😟

>Client: Can you remove the Trojan virus so that the legit not stays?

Me: Umm there is no bot mate it's just a virus 😕 I wouldn't open it outside a sandbox

Client: But here it says Bitcoin faucet bot [links shitty how-to youtube video]

Me: 😒 it's not real dude you are about to get scammed, I can test it in a VM if you. . .

Client: I opened it already, it's working

Me: 😮 r u sure?

Client: yes, can you install VM for further testing?

Me: sure, in your computer?

Client: yes

Me: just download the windows image and text me when it's done

Client: My disc is full! Only 3 gb left

Me: 😑 call me when you clean it

Client: [ offline ]

>> this === rant
<< true

At beginning of this year, I only knew HTML, JS, and CSS so I just applied for offers like "Jr Apprentice Dev in Front-End"
In a interview call, the woman told me that they will send me a test asking about my JS and HTML5 knowledge.
When I look in my inbox, the mail subject says "Back-end Test".

Then I call the woman:

Me: "Hello, I have received the test mail, but maybe it's wrong. I applied for a Front-End position and the test is about backend! "

She: "Do you have skills in JS and HTML5?"

Me: "Yes!, and CSS3"

She: "Well, the test is about that. JS, jQuery, and HTML5"

Me: "..."

Me: "Sorry, that languages are Front-End. In the subject say 'Back-End' and Back-End is PHP, SQL, MySQL, Java, .Net... I don't know nothing about that. I only know HTML, JS, CSS."

She: "It's the same"

Me: "I sorry but it's not the same. Fron-End is client-side, what users sees. Animation, colors, FXs, buttons, forms... And Back-End is server-side, what users doesn't see."

She: "Well, JS, HTML, and CSS is backend for us. We call it that way too"

Me: "Sorry but that is wrong. I invite you to read some basic info. Now I am confused"

Of course that I am not confused. That idi0t was wrong.
Perhaps recruiters should take some info about areas where they are recruiting... (:T)

I have to make this a separate rant.
It's been going on for months, and I don't have alternatives.

This.

This is what I pay 35€ per month for. Every evening it's like this. Usually it can't even load the speed test. Right now it can't even load the upload meter.

A big FUCK YOU to Vodafone in Berlin. Giant ass FUCK YOU, for just promises and appalling service.

Spent all day on this.
Debugging hardware is fucked man...
Me proud.
Wanted to make a devrant logo like always (its my Hello world to test my CNCs now).
And.... When I finally had the machine calibrated... The pen stopped working lol.
I'll just continue tomorrow, it's finished...
Probably gonna use a few times and make a bigger one.

Recruiter: "Take this culture survey. It's not a test. There are no right or wrong answers."

Me, internal voice: Then why give me a list of words to choose from that I think describe me best and another list of words to choose from that describe how I ought to behave at work? Clearly, there's a matchup you're trying to do here. So clearly there's going to be a wrong answer if I don't choose enough of the former to match the latter.

"It's just a tiny change in one function. What can go wrong? I don't need to test, I'm not that stupid to mess this up". Apparently I am. Pushed the changes, and the [Firefox] extension basically stopped working. Lost about 1.5k users in 2 days. Good times ;)

So I've taken the first steps into mobile development this past week, I attached two joysticks to a basic unity app to check if touch input was working and I guess I never got around to uninstalling it. so I go to school and finish some class work early and decide, why not check and see what it would take to get my current main Alpha project working. I open my unity folder and see Joystick_Test and someone walking by asks "what's that?" To which I reply tapping on the app "it's a touch screen test, to see if the phone can detect me touching the screen and dragging my fingers. I hand him the phone and he asks why nothing is happening which I respond with "it's just an input test, it's not ment to be anything fancy I just need to program the joysticks and the scripts are still in development" and he hands the phone back and says "your lazy as shit. I can make the controls work in under a minute" and he walks away. It's lunch now and I manage to catch him in the library. I open Unity, and Mono-develop and call him over. I get out of my seat and say "program the left joystick to move around. I'll give you a hint, vector3". He sits in the chair and stares at the screen for a solid minute until I see him type
Console.writeline("hello world");
And he said it would work and just walked away.

You guys should really take a look at your YouTube history sometimes (If you use it). It's amazing how I move from one video to another.

Here is what I did yesterday:

- I watched a GOT Season 7 review
- Then for some reason, I watched Underground nuclear test
- Several HD footages of Nuclear tests
- Top 10 Demolitions gone wrong 😕
- "No Planes" in 9/11 attack 😕
- Amber Heard's Sexy Prank 😕

Fucking hell, I need to get back to work ☹️

A) Create something that works, is fast, minimum bugs, have edge cases covered, nice testes, clean code. Cool, you did your job. END.

B) Create something shitty with bugs, performance issues, non or poor test coverage, mess code, etc. Cool, you did you job. But...

Next week you reduced bugs by 50%. Wow, you're rockstar.

Another week you improved performance by 15%. Again, you're the hero.

2 weeks later, you reached 85% test coverage. Management is so happy that almost got orgasm.

"A" took 3 months, "B" took 3 months plus few months of fixes. The only time where B was winning was first 4 weeks, where A was carefully building it's architecture and quality.

Yet B is seemed more successful.

This industry is F****d Up beyond my understanding.

I've found that suddenly and infrequently, for the past week or so, letters are missing from typed code, and I have to go back and fix them.

Now that is not super weird I guess, but as someone who tends to type quite accurately, and uses a high end mechanical keyboard...

I'm just wondering if the keyboard is broken, or if it's a brain tumor.

I've tried to test it, but every time a letter is missing I'm not actually completely sure I hit that key...

And considering the price of the keyboard, I'm also not completely sure which cause I prefer.

FUCK FUCK FUCK FUCK
I HAVE A TEST TOMORROW AT 8 AM AND I'VE BEEN TRYING TO SLEEP SINCE 12.30 AM. IT'S 6 AM ALREADY, 6 AM!

I guess when they no screens before sleeping they really mean it. I'm fucked, I'm really fucked. I guess I'll stare the ceiling until the alam goes off and accept an awful day and hope I get pumped up during the test or something. Fuck me. I want to fucking SLEEP. Fuck.

I just wanted to install vivaldi before sleeping and watch the last rick and morty episode. Does that fucking make me a fucking night owl? No. I could've use these precious time learning or writing code, or even sleeping, but fuck! I'm stuck here in time, just waiting for fucks sake!

Good night...
OR That's what I WOULD say if I could sleep...

In a UAT meeting with representatives of our project partners,

The account executive, who set up the project, said to my PM in front of everyone just before the test started: "I hope your system won't fail, because everyone here will be watching"

My PM: "No it won't. But in that case, I believe it's your fault for setting an unrealistic deadline without consulting us, the development team, first"

All the representatives, being also developers from multiple companies, proceeded to stare at her with disgust.

Holy fuck this new GitHub feature is amazing!!!
It's called GitHub Actions and you can easy automate your work flow using a simple graphical editor!
I need to test this out right fucking now!

"I'm almost done, I'll just need to add tests!"

Booom! You did it, that was a nuke going off in my head.

No, you shouldn't just need to add tests. The tests should have been written from the get go! You most likely won't cover all the cases. You won't know if adding the tests will break your feature, as you had none, as you refactor your untested mess in order to make your code testable.

When reading your mess of a test case and the painful mocking process you went through, I silently cry out into the void: "Why oh why!? All of this suffering could have been avoided!"

Since most of the time, your mocking pain boils down to not understanding what your "unit" in your "unit test" should be.

So let it be said:

- If you want to build a parser for an XML file, then just write a function / class whose *only* purpose is: parse the XML file, return a value object. That's it. Nothing more, nothing less.
- If you want to build a parser for an XML file, it MUST NOT: download a zip, extract that zip, merge all those files to one big file, parse that big file, talk to some other random APIs as a side-effect, and then return a value object.

Because then you suddenly have to mock away a http service and deal with zip files in your test cases.

The http util of your programming language will most likely work. Your unzip library will most likely work. So just assume it working. There are valid use cases where you want to make sure you acutally send a request and get a response, yet I am talking unit test here only.

In the scope of a class, keep the public methods to a reasonable minimum. As for each public method you shall at least create one test case. If you ever have the feeling "I want to test that private method" replace that statement in your head with: "I should extract that functionality to a new class where that method public. I then can create a unit test case a for that." That new service then becomes a dependency in your current service. Problem solved.

Also, mocking away dependencies should a simple process. If your mocking process fills half the screen, your test setup is overly complicated and your class is doing too much.

That's why I currently dig functional programming so much. When you build pure functions without side effects, unit tests are easy to write. Yet you can apply pure functions to OOP as well (to a degree). Embrace immutability.

Sidenote:

It's really not helpful that a lot of developers don't understand the difference between unit, functional acceptance, integration testing. Then they wonder why they can't test something easily, write overly complex test cases, until someone points out to them: No, in the scope of unit tests, we don't need to test our persistance layer. We just assume that it works. We should only test our businsess logic. You know: "Assuming that I get that response from the database, I expect that to happen." You don't need a test db, make a real query against that, in order to test that. (That still is a valid thing to do. Yet not in the scope of unit tests.)

Hiring process is fucking broken ok?
We all do have something else to do, nobody wants to do "homework" for 4 fucking hours. Which let's be real, isn't 4 hours. It's always more. I try to squeeze it in a least amount of time which means mistakes will be made. I always try to show my knowledge of the language and it's features. But, you didn't do X. That's it, that is a no from us.
Dude, I just wrote a high production grade small project with 90%+ test coverage and you are telling me that those 2 small shit I made is a big deal? Fuck off

Most companies I worked with have a code full of shit and here I present to you, with a poetry and it's a no because of X?

My bet is that if I ever started to work there I would find a code that isn't tested and is in shit state

\rant

It's about a guy that knows better.

I was working as a subcontractor on a bigger system. We (subs) were not allowed to deploy code, we had to wait for contractor to deploy.

One day I got an email that my code is bugged and that my feature is not working on production. I checked it on test env, everything was fine. Then I checked if the code I wrote was deployed. It was not.

I send an email explaining that if they deployed my code it would be working. Then I got a response. There was a bug in my code.

Another email. I asked how would they know? Do they have a test on their environment that failed?

No. There is one guy that READ my code and he said it should not work, so he will not deploy it. He was not a programmer, he was a business consultant responsible for the documentation.

His issue was that I used a function that was not in a class. So if the function is not declared it's obvious it will not work. I had to explain to him in another email, that you can use object of another class inside your class and then call a function, that is not in your class. It was the last time this guy blocked my deploy.

TL;DR, I had to explain a non-dev how object composition works in order to have my code deployed. Took four emails.

What's worse than a written test? A written test for web programming! Seriously, how do they expect us to write CSS for a full fledged page when even they know that it's just wololo magix

When you spend 3 hours writing a script and it's time to test 🤔

Most tedious part of my day...

While meetings are boring and awful and all, it's probably spinup times for me. Each and every change requires a minimum of 35 seconds of spinup to test. If i'm testing something with mailers or other daemons, that increases to easily 90+ seconds (plus the worker thread pickup times).

It's not enough time to do anything useful, and more than enough time to lose my focus. It turns every task into boring, tedious struggle. It's awful.

Apart from my coworkers, this is the single worst part about my job. (Okay, the awful code quality totally pushes this to third place.)

Client tests app 100000 times, app works fine
Client tests app once, app doesn't work
Client sends email to everyone,
"Hey, @CodesNotHot, this app is not working at all! Can you please look at it right now!! This is URGENT!"
I test the app, it's working fine.

I just want to high five someone with a machete on the face right now.

SQL injection holes everywhere... The original author of the product put concatenated SQL queries throughout the whole application. If it's not the client asked for a penetration test, we as developers wouldn't even be given chance to fix this shit.

I'm actually glad to have the chance. I can't live seeing them every day but force myself to ignore them.

Developing something which, for real world testing, would require a smartphone with a gps chip/capability or however the fuck you call that.

I do have that but it's so goddamn hard to get a lock on my location which makes it very hard to test this IRL.

😥

Am I the only one who doesn't judge a programmers contributions by commits or change history?

Frequently I'm always near the bottom of contributors, because I don't make a million commits when it's broken. And I don't commit lines that will likely disappear in later commits. I like to finish a function, test it, check it, rework, and then make a "made function()" commit, as apposed to:

"Wrote function()"
"Wrote unit tests for function()"
"Fixed error"
"Code cleanup"
"Style guide compliance"
"Reworked function()"
etc.

Sorry that I keep my commit history clean and ensure it builds.

3 hours making this beautiful circuit to test stepper motors.
Arduino nano + L293D + pot
Fucking bitch has a short circuit somewhere and can't find it out...
Made the same project in a breadboard in 15 minutes and it's working.
Fuck hardware bugs.
Cutted in the middle of all connections, took out excess solder... Nothing.
Fuck it, moving to the next ideia

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?

I fucked again...
This is second time I've accidentally executed sudo poweroff on test server via ssh assuming it was my machine :(

It's all because my mind was not stable as we were testing few issues on test server and at the same time from client side someone was doing the changes from Admin side(Wordpress) and we saw menu and few text got disappeared.
Such a bad day. smh

So I wrote code to show the FUNCTIONALITY of my module , which has temporary variables and temporary code.
Boss after verifying : so it's done right ?
Me: no the code needs to be written .
Boss : but it's working...
Me : yeah , but this is a test environment , I need to put everything in place and test .
Boss : so it'll be done in 15 minutes right ?
Me : ...
Boss: ...

Client: *uses Oracle on AWS RDS*

Ora: *licence about to expire*

Client: we need a cheaper and equally performant solution.

AWS: we have an outstanding Aurora db! Its performance is flawless!

Client: shut_up_and_take_my_money.png

Engineers: *migrating to Aurora mysql*
Engineers: fine-tuning the db for 2 months, adapting app code.
Aurora: *shits its pants during test ramp-up, delivers ~70% of Ora perf*

==========

Client: we need to do better!

AWS: try Aurora Postgresql!

Engineers: *migrating to Aurora postgresql*
Engineers: fine-tuning the db for 1 month.
Aurora: *shits its pants during test ramp-up, delivers ~40% of Ora perf*

AWS: let me see...
AWS DBAs: *fine-tuning the db for another 2 months*
Aurora: *survives ramp-up, delivers ~70% Ora perf*

AWS DBAs: your application is wrong.
We: Ora didn't complain about that...

AWS DBAs: umm.. Err.. Then your load test is wrong
We: ora wasn't complaining about that either...

AWS DBAs: errr.. Ummm.. Oh, I've got it! Your queries aren't optimized!
We: we cannot change queried - they are hardcoded by our framework's vendor

AWS DBAs: well there you go! Your queries aren't optimized! It's your fault, not aurora's

yyeeahhhh... Riight...

From my xp, aws support and aws engineers ALWAYS try to put the blame on a client. Always. Even when they're obviously wrong.

I find a poor tester copy/pasting data from the test environment to the live one, as he accidentally broke it. I ask the DBA, " why isn't syncing SQL records part of the deployment pipeline?"

"You're front end. This is my job. Go do your job."

"... but it's an easy query, and you're exposing us to human error."

"You need to go sit down."

Building my own accounting software because everything else is overly complicated and is trying to compete with enterprise accounting tools. All I want is some budgeting, some bill tracking, and categorization.

Writing in Ruby because I'm a masochist. Using built-in minitest because again 😈.

I have currently around 62 assertions. As soon as I add ANY new test that's literally asserting true, everything comes unglued and 20+ failures pop up. Take it out, 62 passes.

I feel like I'm going crazy at this point. The errors also don't make ANY sense. Shit like, "that record doesn't exist" when it's clearly a part of fixtures and is only used in ONE test(the one that's breaking).

Installed minitest bisect, and it's like 🤷‍♀️"lol get fucked bro!"

So I came here to rant about this before my battery dies and I go drink myself to sleep.

Thank you for coming to my dev-talk.

So, CS student here.
Gave TCS "national" level test.
Quoting from the question:
"if you have 3 bytes of memory, it can be used to represent 2^3=8 values in the memory"

This test is a waste of at least 30000+ human hours and these guys didn't even put 24 hours of effort to make sure questions are correct.
Fuck this fucking IT industry.
Fuck the people who designed this testing process.
Fuck the people who endorsed this process.
Fuck the management for passing it as a test.
The people who wrote the test question can go die in hell.
It's not my problem that their mothers fucked Neanderthals.

Uh! All I want is a job but ended up wasting 200+ hours of time.

This was some time ago. A Legendary bug appeared. It worked in the dev environment, but not in the test and production environment.

It had been a week since I was working on the issue. I couldn't pinpoint the problem. We CANNOT change the code that was already there, so we needed to override the code that was written. As I was going at it, something happened.

---
Manager: "Hey, it's working now. What did you do?"
Me: *Very confused because I know I was nowhere close to finding the real source of the problem* Oh, it is? Let me check.
Also me: *Goes and check on the test and prod environment and indeed, it's already working*
Also me to the power of three: *Contemplates on life, the meaning of it, of why I am here, who's going to throw out the trash later, asking myself whether my buddies and I will be drinking tonight, only to realize that I am still on the phone with my manager*
Me again: "Oh wow, it's working."
Manager: "Great job. What were the changes in the code?"
Me: "All I did was put console logs and pushed the changes to test and prod if they were producing the same log results."
Manager: "So there were no changes whatsoever, is that what you mean?"
Me: "Yep. I've no idea why it just suddenly worked."
Manager: "Well, as long as it's working! Just remove those logs and deploy them again to the test and prod environment and add 'Test and prod fix' to the commit comment."
Me: "But what if the problem comes up again? I mean technically we haven't resolved the issue. The only change I made were like 20 lines of console logs! "
Manager: "It's working, isn't it? If it becomes a problem, we'll work it out later."
---

I did as I was told, and Lo and Behold, the problem never occurred again.

Was the system playing a joke on me? The system probably felt sorry for me and thought, "Look at this poor fucker, having such a hard time on a problem he can't even comprehend. That idiotic programmer had so many sleepless nights and yet still couldn't find the solution. Guess I gotta do my job and fix it for him. I'm the only one doing the work around here. Pathetic Homo sapiens!"

Don't get me wrong, I'm glad that it's over but..

What the fuck happened?

So my company was building a software to allow users to use a screen without the screen being touch itself.
It was made using a camera above the screen and then with openCV detect where the hand was.

Anyway I had to test it on the place.

And the place was a factory where they did produce pipes.
It's the biggest company in my city, and yet I was there, in the break room, coding a raspberry in winter in a factory.
The only source of heat was the fire used to melt the metal

That was literally awesome

Had a blast from the past the other day. Testing an issue with an AngularJS app in IE11 on a project managers Surface.

Nothing works. Just a blank screen. I open the JavaScript console to hundreds, maybe thousands of errors. They all seem eerily familiar, but I can't place them. It's like something from a past life.

Then I see one that brings the issue into sharp focus.

"{{variable_name}} is a reserved word"

No it isn't, I think. That hasn't been a reserved word in JavaScript since...

Me: "Is your browser in Compatibility Mode?"

PM: "Yeah, it's for one of our legacy programs"

Me: "You need to turn that off to test this app. It thinks you're using IE6, so it's having a 2 decade old shit-fit. I haven't seen those errors since I was a teenager making crap on Geocities"

I never thought an error message could make me feel so old 😩

Crushed my first week at the new job. I'm not a software engineer yet, but it's a QA job with a fair amount of test automation, so lots of programming and another step toward my goal.

I'll be honest, I've never understood why people say that numbers generated by a computer are pseudorandom and not random.
I know a lot of algorithms for number generation, and I implemented mine, based on time of invokation expressed in nanoseconds, taking digits, manipulating and transforming them. Then I analyzed the probability distribution and it's absolutely flat. So, if you know the Touring test, we can use a modified version of it. If I give you a sequence of random numbers generated by a computer and I give you a sequence of random numbers invented by a person, and you can't notice the difference, so the test is passed.
What's wrong on it?

Has anyone felt the astonishing effect that is writing a whole bunch of test classes, hitting run for the first time and they all pass.

I'm kinda sitting here staring at my screen in disbelief, either these tests all passed, or I've really missed something and they passed anyway, or it's just a lying piece of shit trying to question my own abilities... all are possible right now.

And no, they are not " assert(1,1) "

Maybe in special dedication to @kiki.

I cut the unit tests down in LOC size by roughly 50 - 60 % in most projects.

It's really easy once one sees unit tests not as a dunking pile of copy pasta wild west, but rather as a code base that needs architecture and design.

Some extensions, some annotations, some good old helper classes.

Pooooof.

Why I did this? ...

Because it's fucking annoying when you read a PR with tests and need a fucking diff tool to spot the difference between two tests cause they're 80 % the same.

Yeah. Thx for giving me brain cramps, motherducker.

I'm not an expert in unit tests, but if all test codebases look like the "usual stuff" in our projects...

It's no wonder bugs exist...

Nobody Unit Tests.

So it's already 1:15am late night and I am all tucked up in bed watching Roy Oshrove talk on unit testing and ways to write correct unit test. My friend walk in and finds me in bed watching this. He seems surprised as what are you doing ??
I replied it is an interesting talk on unit testing.

He says are you mad? Who the hell does unit testing ?
People out there are spitting on unit test code base. And they don't write unit tests.

Nobody unit tests.!!

I stay calm. I know there is no point of arguing. I said I'll sleep in some time.

And he works as developer, a job that I applied an never got because of connections.

I am optimistic someday I'll find a job that I deserve. The developer world is in danger. !!!

When you don't test before release..

It's a thing you notice now and then here in Belgium...

After 3 interviews with test:
"Ok very good, I see you are good with JavaScript, Php, MySQL and some frameworks, it's exactly what we need because we use only on the edge technologies and we do very cool products."
"Thanks, so what about the first app?"
"App? oh no eheh, now you must manage our 12 wordpress sites and edit the CSS!"
"Very good, so while I see you all goin to fuck monkeys I with to you a nice day"

I'm a contractor at a product company and today I had the pleasure of working with some jQuery.

A function needed to be called before another function, hard work right?

So I moved the call to the function 3 rows higher, checked it in, set the task as ready for test and started to look for other tasks.
Within a couple of minutes I get a direct message from another dev, let's call him Steve.
Steve wanted me to set the task to ready for code review instead of test, so I did just that and tried to move on.

Some minute or two later Steve contacts me again:
"It would be great if you'd move the comment so it'd be over the call to the function"

Well, I'm not one of those who likes comments... If you need a comment, it's probably not good/readable code. In some cases sure, it might be a complex block coming up.
Sorry, lost my train of thought.

I answered Steve : "Are you sure, I could just remove it instead?"

(for readability S will be Steve and M will be me)

S: Well, it's always good to have comments
M: In this case I think it will be alright.
S: But it's nice to see what the function is doing.
M: I'll do it if you really want me to.
S: It's better to have the comment than to not have it and needing it.
M: Okay then

The name of the function : LoadOrganizationTree()

And this is the comment :
//Load organization tree

First Rant here.

So I was working on some integration test issues when I found this by accident made by a professional level SW engineer:

@Test
public void testMethod() throws ApiException {
Response res = null;
try {
res = serviceToTest.callMethod();
} catch(Exception e) {
assertNull(res);
}
}

Was wondering why tests were being green after some code changes I've made cuz tests could have not been green afterwards.

Together with a senior (I'm also professional only) I've tried to explain him for a good 1-2hrs why this code is useless and he still did it. Good thing there are no errors in the real implementation from him after fixing the tests as it's code freeze here and we are having go live in a few days 🙃

Also luckily he isn't working on our code anymore and has only been doing so for a few weeks.

Wasted a day with it and gonna check all of his code now before I run in the next surprise.

Customer: as soon as you get a proof of concept could you send it to me?

Me: sure *sends app to test* here is what it currently does and does not do.

Customer: thanks, here is a list of 59284 things that dont work or need changed.

No shit sherlock. It's not done, you wanted a very early version, and of the things you listed I already mentioned half of those.

About to start coding my first complete website. Oh boy. Everything I learn up until this point. Just basic HTML is all about to be put to the test. Lol. Grant it. It's not for a client. Just school assignments but man I'm nervous.😂😂🤷‍♂️

Pissed off. Planning on imposing a company wide hook that prevents you checking in code with a @Generated annotation. Seriously, never even heard about it being used outside of auto generated code until some bozos here seem to have started using it to silently drop complicated classes from test coverage metrics. Is this a thing with new coders these days, or are my lot just cowboys?!

No more, anyway. Sometimes it's convenient to be able to pull rank.

/*
"Not wk135, but blah blah blah"
Please don't misuse wk135 (Sorry)
It's about coding tests
Thank you. */

=>
A company took their technical test on this really weird website. There was a Windows Narrator guy's voice giving instructions while a timer was running. I had to flash my ID to the webcam and then fit my head on an outline on the screen. It was for a web dev position. I had to speak into the microphone to answer the Narrator's questions and then send the video to them. The questions were weird and hypothetical, mostly. I just thought that their process was dumb and unnecessary.

=>
I don't like aptitude and algebraic tests. One company, I remember, had their test on Google Forms. For some multiple choice questions, they put check boxes instead of radio buttons. So, I could just blaze through it selecting all options. Some of the questions had their first option as "All of the above" 🤔. Fortunately, I didn't pass the test.

=>
The company I'm interning with, starting from next month, had a good interview process. They asked me questions on JavaScript, CSS, and a few on algorithms and data structures. I was also given a task where I had to make a css animation of trees. I'm glad they didn't have an algebra entry test.
😊

One of my colleges complained that the remote vm he uses to test his Java-Code is so slow that he thinks it's actually just a potatoe.
I said to him... Well you know... 3 Billion Devices run Java.

When you encounter a bug in your code while writing a test and you have absolutely no idea what's wrong...

...and then you see it's a type problem.

Want to fuck other developers? Then make a quite probable project name illegal without documenting it, nor providing any helpful information in the error messages.

I tried to name my Flutter test project flutter_test. Turns out that that name is reserved (it's a package). Fml. 🤦🏽‍♂️

*Goes to record a video and upload a demo video*

Hmmmm.. internet is being slow... Let's do a speed test

*Realises our speeds have been caped out to a max of 256kbps*

Why... Why... Yes I understand it should be limited so it's not 'data for free' but at least give us 1mbps so things are actually doable but limited rather than just usable as long as all you want to do is Google something slowly -,-

When test team reports a bug that has been happening for at least a year and all of a sudden can't deploy until it's fixed. 😳

Had a PHP test for a job application yesterday. The test contains nearly 20 questions, most are 2 points. I had to write the answer into a word file and cannot use search engine. I thought I did okay because most of the questions were asking like 'what is php', 'what is isset', etc. which I could answer all of them and pretty confident that I answered correctly but the recruiter contacted back today that I failed...:(

It's my first time applying for a programing job after been working in the field for almost 3 years. Feel so bad.. Feel so unqualified 😥😥

A funny story I just remember while my code is compiling :

Back in high school, in Math, we were taught how algorithm works, and we made some exercises with practical examples.

I didn't know anything about it back then, so was curious. Was pretty fun, but one day, my teacher said that a IF is a loop. I said "no, this is a test" but she keeps saying that it was a loop, ignoring me (I dunno if she actually heard me) and no one actually noticed it as she repeated it several times (while I was saying that it's not). I just gave up trying to say it's wrong.

I love arriving at work to see in a mail that a co-worker is literally saying "please test things before delivering it"

Like I did it, it worked, and most importantly, it's their part of the code that had a problem.

Fuck off, learn how to communicate without reproaching stuff you should have done before

I'm finally writing unit tests consistently thanks to a simple file organization decision.

I'm not doing pure TDD, but at least I'm writing the tests immediately after writing a module, and I make sure they run ok.

What I'm doing is Instead of putting the test files in a "tests" dir at the root of the project, I have the tests right next to the source code.

So if I have a dog.x file, I also have a dog.test.x file next to it.

I'm not inventing gunpowder here. I've seen several people do this.
But it's something that is not generally made a default or advised to do.
Like I said; test frameworks in general go with the classic "tests" dir.

But for me this is day and night in whether I write the tests or not.

Which makes sense. Imagine the classic scenario of the "tests" dir, and you just created a file deep into a hierarchy, let's say src/lib/console/windows/dog.x

This means that if you want to write tests for that, you need to make sure the hierarchy tests/lib/console/windows/dog.test.x exists

If the test file already exists, but you want to access both files, you need to traverse deep for each.

Also, it's actually harder to keep track which files have unit tests and which do not.

Meanwhile, if the test files are next to the source, all these problems disappear.

That doesn't mean there are no other challenges with testing, like testing untestable things, like system calls or http requests, but there are ways to deal with that.

During a period when devs had been told "The board has been promised that we are improving quality, so you must not do anything but write unit tests", I wrote a unit test that compares the number of system colors in .NET to a constant. It's still running today (a couple of years later).

Friend of mine had a perfect day today:

It's 3am, you're coding hard, can't even see properly, but you know only a two or three proper lines and you are finished. A few minutes later you set your pc to hibernate because you can't go further and go to sleep.

In the morning/noon you log in, see only a mess. Half of the new variables are probably obfuscated or in some alien language because you can't read that shit and a cherry on the top - 1/4 of a _big_ test suite reports errors. What a lovely day.

Yesterday me and my friend started a project. I set a github repo and said him to "If you make something with code just commit the changes to github so I can see what you did". After a while he said "I've commited something". And I checked what he did. There was 3 commits and they were exactly like that;

Commit 1. Test
Commit 2. Test 2
Commit 3. I wrote something

Then I said "please explain what you did when you commit changes". And he said "why we just upload the codes to the cloud it's more easier".

Today project is ended. Uploading codes to the cloud...

When you give your team and the client a month+ to test the app and get no feedback, then all of a sudden once it's live in the app store you get an email filled with bug reports....

Were you guys not testing it at all?!

😡🤦‍♂️

Google in their *infinite wisdom* has decided the .dev domain they bought should be forced to https in Chrome 63 fully knowing it's a common test gTLD for Web developers.

Used a starter to scaffold a new project. Have never used that starter before but it has more than 1400 starts on Github.

Two days after.... so far so good. The created project structure used some tools I haven't used before, some are good, others are not so good, but anyway I am towards the first release of my codes. I have done countless 'npm run build', 'npm run test', 'npm run fix', etc., but.... my fault, I haven't committed once since starting the project, thinking I would commit when the next function is implemented, next test case passed.... after all, what could go wrong anyway?

Finally, one last test case passed, I think I will commit and run 'npm publish'.... but wait, had a glimpse of the scripts section in package.json, there's a command named 'all'. An voice came out of nowhere was talking to my subconscious mind, "all.... build, lint, prettier, test..... yeah you should run all... it's another build script, the worst you can get is just some harmless error messages.....", and my fingers typed 'npm run all'...

Time stopped for a few seconds, file structure in project explorer was shifting, files & folders were disappearing & appearing, what's happening... and I looked at the 'all' script closely for the first time....

WHAT THE HELL, WHO SHOULD PUT 'git reset --hard' IN A BUILD SCRIPT WITHOUT ANY PROMPT????!!!!!!!

MY PLAN WAS TO COMMIT AND GO TO SLEEP, IT'S 1AM NOW!!! WHERE CAN I RECOVER THE LOST FILES????

Things that seem "simple" but end up taking a long ass time to actually deploy into production:

1. Using a new payment processor:

"It's just a simple API, I'll be done in 2 hours"

LOL sure it is, but testing orders and setting up a sandbox or making sure you have credentials right, and then switching from test to life and retesting, and then... fuck

2. Making changes to admin stats.

"'I just have to add this column and remove that one... maybe like a couple of hours"

YOU WISH

3. Anything Javascript

"Hah, what, that's like a button, np"

125 minutes later...

console.log('before foo');
console.log(this.foo)
etc..

Don't reuse your fixtures!

Each test case should be isolated. Don't ever think just because some function requires a similar input, it's safe to reuse it ALL OVER THE PLACE.

Why? Because someday, you want to change one functionality of one unit.

And you adapt your tests, fix your code, and suddenly, by changing one fixture, you break dozens if not hundreds of unrelated tests and now you have to clean up that mess.

It's even worse for functional tests with all those interwoven parts so that it becomes hard to reason about the scope of your tests when lacking proper documentation.

How I know? BECAUSE I AM CLEANING UP YOUR MESS RIGHT NOW!

When the boss has a meeting at 4pm with the client, it's 1pm, I didn't have lunch yet and I have to release the product in 1h, and test everything before he starts the meeting... :/

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

I'm going to have a test tomorrow... And I still don't know the grade of the test I've done over 1m ago (2nd of November)... And people are saying the teacher told them the grade is coming tomorrow when he told us on my class (2 different shifts) that it was coming out today... Someone send help please
In the uni's regulation it says that if teachers don't release our grades for a test 3d before the next one, we can talk to our pedagogic commission and ask to do something about it. People from my course on fb were talking about asking to remove the minimum grade on the average of our 2 tests, but IDK how that situation is and I don't think there's much we can do about it so on top of tomorrow's test. And changing the date of the test isn't really an option because we have 3 tests left on the next week and 1/2 and it's all so on top of each other so the only solution would be to make it after the 20th (that's our last test, and people have already booked flights to go home)

Oh no...

A <FlatList> as a DIRECT child of a <ScrollView>... I mean, I'll give you the benefit of the doubt if you forgot or it was buried in a nested component... but... it's just sitting right in front of you on the same exact component... it's like, did you even test this once and see the warnings?

God these 'affordable' devs truly aren't actually worth it.

They really aren't.

You spend just as much time fixing their clownish mess as you get for "saving money" with their cheap rates.

Another day, another clown dollar in clowntown...

SHEESH

Ran a bamboo test suite which just printed '408 tests ran successfully'. It's only had return true :P

Periodically update test number.

Is it just me, or are the media / journalists once again putting a stupidly unfair pessimistic spin on that SpaceX launch?

"SpaceX rocket launches but explodes shortly into flight"
"Musk's SpaceX big rocket explodes on test flight"
"SpaceX rocket explosion: None injured or killed"

They've said time and time again, it's the first test of a massively complex rocket that's bigger than anything that's ever gone before it, and success is just defined as "getting off the launch pad" and collecting data. They did that and then some.

But instead of spreading excitement about the data, the fact it launched, that it's a world first, etc. - it's all doom and gloom, implying that the whole thing was a failure and people could have died 🙄

And people wonder why I have a low opinion of journalists.

I wonder what data type dfox uses to store the voting score. We definitely know it's not a byte. Next up, let's test if it's an int16

When the PM decides to test your build for bugs at 3PM on a Friday and it's been ready since 9AM...

Why would someone name a method test() if it's not actually used for testing?

probably every time I see my tests failing.

Each time I am writing tests I'm convincing myself "it's an investment", "spend 2 hours now to save 2 days later", "unit-tests are good".

And each time I'm chasing away ideas like "perhaps they are right, perhaps writing unit tests is a waste of time..", "this code is simple, it should ever break - why test it??", "In the 2 hours I'll spend writing those UT I could build another feature"

Yes, it is terribly annoying to write tests, especially after writing the production code (code-first approach). Why test code that you know works, right?

But after a few weeks, months or years, when the time comes to change your feature: enhance it, refactor it, build an integration with/from it, etc, I feel like a child who found a forgotten favourite candy in his pocket when I see my tests failing.

It means I did a very good job writing them
It means it was not a waste of time
it means these tests will now save me hours or days of trial-and-error change→compile→deploy→test cycles.

So yeah, whenever I see my tests fail, I feel warm and fussy inside :)

When you work for a week day and night to compete a feature, because top management said it's the highest priority. Then when you're about to send it off to test, they tell you it is no longer required.

It works locally, it works in Dev, it works in Test, but fails to deploy in UAT. Is it a data issue? I don't know, I don't have permissions to see the UAT database. Literally all I know is that this API is returning 500 instead of what it's supposed to return, but only sometimes.

Guess I'll sit here all day and try to solve the problem telepathically as there is literally no way of troubleshooting other than scrolling through the code and hoping that a cartoon lightbulb appears above my head.

So I got a telephone interview for a job that a recruiter found for me. Call went well, comes to the development test. Small application in ruby on rails, haven't used it in about 2-3 years so a tad rusty. Completed the test under two days (was given until Friday) not too bad if I say so myself. It's for a junior position anyway so I'll assume they wouldn't mind giving me a refresher to help jog my memory.

Gotta love it when everything works flawlessly with the test API endpoint and credentials, but when I try to go live, there's suddenly a ton of additional configuration to get the third-party APIs working.

Why the fuck do you even provide a testing environment, if it's completely different from the live one?

Created a Service for drawing online. Just as a canvas test. My friends seem to like it. :D

It's a WebSocket based system, I hate that node module but it works.

I once got something weird during interview. I had to do an assignment on site taking the whole work day of time. In the end, I got bashed on how much I delivered and had to defend it. Defending was easy: the project was decent while not being much. A Mercedes without electric windows. I just told them it's what I prefer.

Later got a phone call and got hired.

The social test was the hardest

I hate dev politics...

PM: Hey there is a weird error happening when I upload this file on production, but it works on our test environments.

Me: After looking at this error, I don't find any issues with the code, but this variable is set when the application is first loaded, I bet it wasn't loaded correctly our last deployment and we just need to reload the application.

Senior Dev: We need to output all of the errors and figure out where this error is coming from. Dump out all the errors on everything in production!!

Me: That's dumb... the code works on test... it's not the code.. it's the application.

Senior dev: %$*^$>&÷^> $

Me: Hey I have an idea! If test works... I can go ahead and deploy last week's changes to prod and dump those errors you were talking about!!

Senior Dev: OK

Me: *runs Jenkins job the deploys the new code and restarts the application*

PM: YAY you fixed it!!

Senior Dev: Did you sump put those errors like I said.

Me: Nope didn't touch a thing... I just deployed my irrelevant changes to that error and reloaded the application.

During my university days, we had a basic programming quiz. One of the questions is to "write a program that will determine if a number is even or not".

An annoying seatmate asked me silently if his answer is correct. Then I saw his window:

=========================
> Enter an even number: 10
> The number is even.
=========================

I told him it's correct.

After the test his answer is marked as wrong.

"You told me it's correct!", he said to me.

I approached the professor, and told him that his answer is correct.

"What if I enter 3?", professor said.

I told him, "User Error".

When a test server goes down and it was a few mins away from it's next backup. 😐

It's like a stab into your fucken heart when your coding competition entry gets rated "you did everything perfect! :) But it's not enough for the top 3. :(" with multiple minus points across different requirements bUT NO GOSH DARN EXPLANATION WHAT I DID WRONG. I PARTICIPATED TO TEST MYSELF AND LEARN SOMETHING, NOT GET PUNCHED IN THE FUCKEN FACE FOR NO REASON FFS MAN.

Don't you love working out a piece of code in your head that's been troubling you for ages but you can't test it because your at work... It's horrible.

Tempted to whip out vs code and just quickly test my theory in JS...

!rant real talk though.

I am frustrated. Lately i have been having a slow time on the job, and it somehow dulled me down a lot.

In games you often have to think about transforms and rotations and offsets and hell knows what else.

I am usually pretty good at 3d object manipulation, it's one of those IQ test skills i generally score well on.

However lately i have not been able to come up with jack shit, i am simply unable to coherently think through a set of positioning and rotation changes to aquire the correct outcome for a mechanic and it pisses me off.

I have to fall back to slow as all hell trial and error and i don't even know what to do otherwise. It's been months now, do i have brain cancer or some shit? Arrrrrrg!

Went on Vacations to Dominican republic !

It's a paradise !

Going back to Canada in 2 days... Oh WAIT ! Positive covid PCR test, welp, 14 days to stay in a hotel room :( And ofc need to take vacations days for that

and hotel only offer 7 days, other 7 will need to pay :( But at least I have a nice view

So I got in contact with a recruiter who said they have a possible job for me. The catch is it's in c# (I am a python java dev) and that there is a assessment test for the language to test for competency. I told the recruiter that's fine but I would need a week to highlight the main differences between the two languages and at least do a couple of educational programs for my learning sake. All was fine and that was the plan.
The next day the recruiter notifies me that the test is being called off on account of the company being swarmed. So the recruiter then proposes another similar test (in c#) the recruiter will use to measure my skills and that the recruiter will send the test via email that same day. Later that day I check my email and don't see the test. So I message the recruiter and never get a response. Next day comes and I decide to give the recruiter a call; no response. I then wait until the next day and message him on linkedin that I still needed the test. Linkedin was showing he read the message, but of course didn't respond.
I told my brother about this and he said to send a message saying: "Hi [recruiters name] because of the lack of further feedback I decided to go with another opportunity. Best regards, Lane"
After I send it I get a message the next day from the recruiter saying: "Hey, sorry I haven't gotten back to you. We had to install a new phone system yesterday so it was a busy day."
"I'm going to send it to you today so that you can look at it over the weekend. "
I can't help but think the recruiter is full of shit, but I may be jumping to conclusion. I know they can have a busy schedule, but if you have time to look at a message on linkedin how long would it take to type a short message explaining what's going on? I would like to know any opinions or insights on this.

Fuck me I'm pissed. This sprint, my tech lead has been away and a senior dev has been covering for him. We plan a load of work and distribute stories and we churn threw it quite well. However, my senior dev says let's not deploy until all the works done. I was like, how is it going to be tested? He was like well it will be fine because it's all one test. Bs. We now have 2 days left, tester is getting stressed because they don't know what to test or what's been finished. Scrum master is asking why all of it should be tested at the same time and I'm here like this is fucking dumb. Also the tester decided to start testing with the most complex piece of work, rather than prioritising.

Starting to wonder if I'm just the outsider or whether no one understands that granularity is better.

We basically don't unit test at work. I write some tests for my code and honest to God people complain I'm wasting time saying a test bed and manual tests are good enough. We don't write test beds for about half of our production code and rely on integration tests for the rest. We only test release builds which have been symbol stripped, I get handed a crash report with no stack trace that I'm unable to reproduce and expected to stay late to fix it for some arbitrary internal deadline.

I've since moved to R&D where basically I'm left to do my own thing so it's better.

We don't project manage. Project leads take time estimates and double them so management might cut them some slack. This doesn't matter because management made up time estimates before the project started. Last project I was on had a timeline of 3 months and took a year.

We have released broken products. Not that any of the above really matters, our software products have made about 50k revenue in 2 years. There are 6 people on software. Fortunately hardware has made about 3 mill. That said our hardware customers are getting frustrated with us as we keep fucking up, shipping broken products and missing deadlines.

I've been working there about a year and a half and will be looking for a job at the end of the current project.

I joined devRant about when I was most pissed off with my job, my rant frequency has definitely gone down since I moved over to R&D.

It's 3am, just submitted an app for review for iOS... go to take one last test drive on the release build for android, and I get stuck in an infinite loop of "system up stopped working". An factory reset and an hour later, I'm saying fuck this, android waits, and fuck whatever Xamarin did to my phone. While I'm at it, fuck Apple for making me have 20+ icons in different sizes, and their shitty walled garden approach to a so called marketplace.

I've got staff, I've got staff
And they bill time and a half;
Now I only write the gist you see
And they can code the rest

Open source, Fraying nerves
Smoothing out regression curves;
Try this framework, it's ambitious
It was made of spit and wishes.

Coffee rings, at first glance
But of course miss, he's freelance;
And this code base is a truly scary mess
I can't expand the menu
Even chance its home brew, unit test;
Unit test, unit test!

Optimization issue pops out with one of our queries.
> Team leader: You need to do this and that, it's a thing you know NOTHING about but don't worry, the DBA already performed all the preliminary analysis, it's tested and it should work. Just change these 2 lines of code and we're good to go
> ffwd 2 days, ticket gets sent back, it's not working
> Team leader: YOU WERE SUPPOSED TO TEST IT YOUR CHANGE IS NOT WORKING
> IHateForALiving: try it on our production machine and you'll see the exact same error, it's been there for years
> Team leader: BUT YOU WERE SUPPOSED TO TEST IT

Just so we're clear, when I perform a change in the code, I test the changes I made. I don't know in which universe I should be held accountable for tards breaking features 10 years ago, but you can't seriously expect me to test the whole fucking software from scratch every time I add an index to the db.

If you are going to tell me you develop using TDD, it's a good idea to actually have tests in your test project.

I've added front-end development to my professional profiles. I've described myself as a "junior" developer given that my useful experience is measured more in weeks and months.

I've been advised to drop the "junior" and just describe myself as a "web developer". Presumably potential employers will read in the "junior" bit when they consider my experience and abilities.

What's the best way to handle this?

I don't want to cripple my chances right out of the gate. At the same time, it's pointless to mislead people about my capabilities - it's easy enough to test them.

I've built multiple profitable SaaS apps in my career, from scratch, by myself...

...but it's sure damn important to know wether fucking Cindy or Bob or neither can fit into a parking lot after muddling through stupid obtrusive rules that don't mean anything

"its to understand how you think"

yep, clearly don't know how to do that, that's why i'm taking this labrat, i mean, cognitive test

🐀🤡🐀🤡🐀🤡🐀🤡🐀🤡🐀🤡

Interviewing with a company that brands itself as "AI-powered software development company".

Get sent code test and rules are no AI to help with code test.

I get it, but it's just so ironic...

So I wrote a service a couple of years ago to generate PDFs from some documents. Fully working, covered it with tests (unit and integration). Code was clear and easy to follow.

I've been promoted and the engineer that took it over just went in and rewrote half of it. That would be fine, but they also just deleted every test. So now it's untested.

Glad that's not my problem anymore, I geniunely hope it breaks

That moment when you have hundreds of lines of code for your website, then you wanted to add a simple modal which looks great on w3school.

Then you recreate the modal on your site, click the button and nothing happens....

So now, you are spending hours trying to figure out why it's not working, new file to test, tried another modal concept, change the CSS, refresh the page until the F5 button doesn't even work anymore!!!

To find out, there is a extra "." in the href file tag plus the tag is in a id not a class

The moment when client test team rejects a fix as it "doesn't work" when it's clear they haven't read the documentation 😂

Are there people here who actually unit/integration/end-to-end/stress test (almost) everything? Or is it a common fact that nobody has time/budget and/or needs to do so?

I like to think I test all the code I write, but to be honest, I think it's closer to 1 to 5%

Man I hate programming tests that have no practical application. I'm not doing one yet, just saw an example question that made me go...ok...I kinda get what you want but..why would you EVER need this. Googled and the consensus is that..*drum roll* you wouldn't ever need it because it's only useful to see if someone can solve it in an interview.

Why not give actual problems or at least actual test cases of things that way you can see if people can solve actual real life problems. Wouldn't that prove that people can reason their way through things or not? See if they can provide a good solution for something that someone else has already encountered instead of some nonsense that wouldn't have an actual practical application?

Maybe it's just me but if you give me a problem that sounds like it's useless for some reason my brain just goes, "Ah this sounds like it's useless, better not actually devote all my brain power to this"...

a friend of mine has applied at a company who have sent them this task* to complete before the job interview.
They gave about 10 days to complete this.
*I rewrote it

Personally I think this is super overblown and way too much to complete as a test before the first interview.
They expect the applicant to configure an SQL database, a backend with a custom API and a UI.
It's like a fullstack prototype software, not a task.
Im not in web development and I wouldn't feel confident learning these technologies in my free time in just a few days.

I said that this felt like some HR manager writing up the test or that they want the applicant to create a prototype for free.
Am I being too extreme here? To me it feels overkill, what do you all think? Is this common?

Oh and I should mention, this is for an internship position for a bachelors student.

We have this marketing class that none of us gives a rat's ass about and it's not related to software engineering in any way, and our professor knew that.

So to make things easier for him and for us, he made the rule that if we do at least 30% right on the test, we'll pass.

If we got a question right, we get 1 point, if we got it wrong 0 points, and if we left it unanswered, a quarter of a point.

That meant that if we didn't do anything on the test, we get 25 % anyway, so we almost pass by doing nothing.

Fucking genius.

I only answered 5-6 questions that I knew were right and left the rest unanswered and passed

Just got to test the app from the frontend team... Oh God why!!
5 minutes, found 5 bugs (c'mon testers!!)

Worst (and now it's a rant) why do designers insist on working with big screens and don't test it on a standard screen? You know? Those typical screens your users are using?

So, it looks great in a 24" screen but the focus is terrible in a 15.6" screen... No time to fix it... What should I tell the users? Works better at 85% zoom out? -_-

You just fucked up the main feature of the app! Congrats!!! The rest looks okay I guess

How to conduct yourself in a job interview
Simple test"Write a for loop".
First, write some nonsense bullshit for twenty minutes. Then, when you realize time is up, pass to the next question. After write more nonsense bullshit in SQL and jQuery, it's time to breath fast and panic.
Deliver your exam.
Pack your stuff and go to a cave where nobody ever will find you, cry the next three years and commit to a life of self punishment, shame and tears.
That's how you nail a job interview, suckers.

!rant

Just spent the last few days learning about unity's custom editor stuff.

Gotta say it's really fun making tools that help setup stuff a lot easier

The thing I made has a bunch of actions and you randomize the action thats picked. You give each action a % chance and even have a % decrease when the action is used.

I ended up adding in a simulator in the inspector so you can test without even running the game :D pretty happy with the result!

Can anyone recommend some android alternatives?

I'm not looking to move away from android permanently but I'm just curious, I enjoyed my time with UBports (fuck QT) and seeing projects like the PinePhone and Librem 3 just get me curious what is actually out there.

Currently rocking a pixel 2 XL but not shy on buying new hardware to test stuff out as long as it's within reason.

Currently had a look at PureOS (not available) and Sailfish, any others to give a whirl?

Do you guys have any issue with Firefox lately?

It's lagging and hanging a lot on my laptop since like two weeks ago.

I usually run like 2 windows with no more than 7 tabs each. So 15 tabs max in total.

The rest of service I run are sublime, terminal, Mailspring on my lubuntu LAMP stack. :(

The latest app I installed and used is Mailspring, so if nobody has similar issue, I'm gonna disable it and test.

More WTFery from official corporate training.

This gem of a quiz comes​ right after the slide saying not to click on or open emails you suspect are spam. To reinforce the idea, click on the spam!

It's the kind of test that makes me go, "is this a trick question?"

My company insists on working in one production environment to save time and every time I try to convince them to set up a work flow with a dev and test environment, they tell me we don't have the time...

Even after I set one up anyway as I'm scared shitless to touch production. They tell me it's faster doing it all in one environment.

They launch an update. Site buggy as hell and doesn't load 90% of the content...

Sigh....

Live coding interviews basically make no sense.
It's even worse when you can't use an IDE.
Like, bro, what the fuck? You want me to write code in fucking notepad?
Alright then, I can play that game. It's so easy to memorize the algos and pass the test, yet that's not indicative of a good engineer.
I wonder if the roles were reversed, how good the interviewer would perform.

It's more of a QA rant....
A Website takes address information via POST. Since Selenium can not do POST properly devs said: "no worries, we will make the site accept addresses via GET url parameters"

Me:"Why not make a simple page with input fields that just behaves like the site calling our site via POST?"
Devs:"Nah we don't need that. Will be fine. We will ensure that POST service works via unit test."

Come release week... Dev:"Guys, POST isn't working, IT Analyst tested with the other site..."
Dev1:"Why did QA not test this earlier?"

Dev2:"He wanted to, we told him that we would unit test this. He fucking knew it. He fucking knew it so don't blame him!"

Me: :3

Been using Linux for about a year, now starting to customise it. Since it's full of Gnome garbage, I'll test out everything and then do a fresh install. Deadline is September 3rd, if it does not work fast and reliably till then I'll have to get Gnome because I need it for school.

Let the race begin.

"learning" html and css

So, there are these courses in my school, "ÜK" ("Überbetriebliche Kurse") we call them.
It's 5 days, a Tuesday to Thursday, next week Tuesday and Wednesday, last day in the afternoon we have a test.

Today is that Wednesday

I know html and css pretty well, so if was pretty easy, I didn't even bother to do some of the tasks we had
I did look through the book over the weekend to make sure I knew my stuff right

Now, the theoretical part of the test had stuff like "colspan" witch was nowhere to be seen in the book and PowerPoints, and some stuff was just unclear as fuck, seriously...

*looks up colspan*

Apparently it's a table cell that spans two columns, or more, if you want to

I never needed something like that, and we never looked at it, that's why I didn't know about it.

There where other unclear questions as well, so I went to the teacher after the test and told him.

He gave me an empty test where I made an X for stuff that wasn't in the book or the PowerPoints and wrote a bit for the stuff that was unclear.

I did know some more then some in the class, so I generally xed the stuff that we didn't learn
The teacher will correct it accordingly, and cut out the questions that we couldn't have known.
So that's at least something
For the next class, he's going to have some "theoretical learning" or whatever he called it

I mean, in the end it's fair, but it annoys me that these courses aren't as well thought out as they should be...

So after this course I can say:
I DIDN'T LEARN A FUCKING THING

Btw, the second part was changing a website up the way its telling you to, that was easier the the theoretical part, witch was ticking the right fucking box...

Shady business practices. You see a lot of stories of people getting fucked over on here. Companies giving applicants a "coding test" to get work done for free, or guys promising to pay when the work is done(and then bailing), deserve to be thrown screaming from helicopters.

Some quick advice for people starting out:

1. If it's important, get it in writing. Promises are worth precisely dick, unless it's legally binding.

2. Exercise caution in interviews. The shadier companies know a lot of applicants are desperate, and they take advantage of that fact if they're allowed to.

Not sure if I'm rambling at this point, but fuck it. 🤣

Spent months building a full regression testing framework app at the request of my boss...

Now he just says need a simple app to test a few static URLs...

I could've written that in 1 day... FML...

And now I've been pulled away from the main thing he wanted me to work on...

and keeps asking if it's done yet...

So my team got this new clueless "Delivery manager" who doesn't know ANYTHING ABOUT AGILE!
Her favourite timepass ? To eat development team's time asking stupid questions just to make her presence felt. And she does that by visiting each developer personally. MULTIPLE TIMES A DAY !
Why can't you leave the team and let them do some actual work??😑

She would join our scrum meetings to ask questions like "what are story points again?", "How do we calculate team velocity?"
Dear miss Clueless: It's not cool to be dumb! It's cool to take up an online agile crash course if you insist to contribute.

The other day, she suggested a QA guy to "test properly" with a smirk!
I mean seriously ? Was that actually necessary to tell them? This team was working just perfect without you. How about you look before you leap?
I try being nice to her but at times it's just too much to take.

22.30 PM: "Please ceheck all the points in (30 pages long extremely bad and scarce) documentation. Import doesn't work and customer is pretty unhapy."

me: "So do we have an error or am I searching for a needle in a haystack?"

PM: "Just general error."

FFS i'm sick of this. I can't even test the import because it's on a stupid retarded 3rd party software that expexts CRs on new lines and craps all over the place if it sees a Line Feed&#^$/!&@$&'

When your project has no unit tests and you just accept that it's non testable anyway. Especially because the company won't put any effort into making a test environment for it.

I received a call from a company that I applied for to come for a design test. The guy said he would email the details and noted down me email address. I said OK. I didn't ask the guy's name. It's 2 weeks now and didn't receive any email. What do I do? The phone number connects to company's reception

I created an ASP.Net Web Application as my personal Web site. Tested it locally then wanted to test it in a live environment. I purchased a domain/hosting package then publish via FTP. Point it to homepage and nothing shows up. I call customer service and they say it's hosted on a Linux server but their options don't show that it is Linux based. So I had to change it to a Windows platform that it should have already been on. SMH 😣

So our Chief Test Engineer left the company because of overwhelming frustration and stress. We working on new stuffs so we test our partly done product with partly done test tool developed be another of our team. His successor started to drop most of the 3rd party tools and workflows and documentations to trash expect this one unfinished test software.
Now he wants that we add more features to this software so it can replace everything he trashed already: run tests, generate test reports, generate documentations and so on.
On top of that he organized a workshop to read all this software's source code together, understand how it's works so we can rewrite the whole software from scratch.
WHAT?!

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

So, after having my mental breakdown with the 500k LoC Zend Frameshit PHFuck 5.5 with 0 test project, for a whole year; and after moving to a better job, I now inherited a React/Node/GraphQL project with a shitty architecture. It's so shit technical debt can almost be payed with actual cash... or flesh, ass-for-arch.

However, line test coverage is over 90%, so I guess it is an improvement.

!rant

For the first time ever I actually did well on a Computer Science test. I didn't even hand it in with any errors. It's the baby steps of progress that make me feel pretty happy.

Once I maintained one of the most used and fucked up codebases on the market with almost 1M+ daily users. (cannot say more, sorry).

It's written in PHP and is absolutely terrifying,
the first time I saw some lines of code I was about to scream and cry.

- spaghetti code
- no indentation
- random SQL query unoptimized
- unused vars
- Code is split among several files with no logical reasoning
- Mixed procedural and oop programming
- Unsanitised user input (yes, you got it right)

No test environment, no backup database, every commit goes straight to production.

It's a real disaster but the company prefers to keep it as it is without refactoring or anything else.

Just to make it clear:
It's not hatred against PHP, it's against the code's current status and the older programmers which used to work on it.

So I gave my younger brother my OnePlus One since he is now using an even older Google Nexus and don't care much for phones. The camera is slightly better basically.

Asked him to test drive it:

Me: so did you set it up yet?
B: nope, what's the rush?
Me: well you see it's running a custom OS (Lineage) as it technically doesn't support it. You need to test drive it and make sure it works with your SIM? May need to change some configs
B: sounds like a pain, should I just get a new phone?

Me: ... yes probably...

He's a just graduated CS major that doesn't like tinkering with tech...

(Well can I have it back then so I can play around with it?)

Finally made my node production server stable enough that I could focus on writing tests*. I start by setting up docker, mocking cognito, preparing the database and everything. Reading up on Node test suites and following a short tut to set up my first unit test. Didn't go smoothly, but it's local and there are no deadlines so who cares. 4 days later, first assert.equal(1+1, 2) passes and I'm happy.

I start writing all sorts of tests, installing everything required into "devDependancies," and getting the joy of having some tests pass on first try with all asserts set up, feels good!

I decide to make a small update to production, so I add a test, run and see it fail, implement the feature, re-run and, it passes!

I push the feature to develop, test it, and it works as intended. Merge that to master and subsequently to one of my ec2 production servers**, and lo and behold, production server is on a bootloop claiming it "Cannot find module `graphql`". But how? I didn't change any production dependencies, and my package lock json is committed so wth?

I google the issue, but can't find anything relevant. The only thing that I could guess was that some dependencies (including graphql) were referenced*** in both, prod and dev, and were omitted when installed on a prod NODE_ENV, but googling that specific issue yielded no results, and I would have thought npm would be clever enough to see that and would always install those dependencies (spoiler: it didn't for me).

With reduced production capacity (having one server down) I decided to npm uninstall all dev dependencies anyway and see what happens. Aaaaand it works.....

So now I have a working production server, but broken local tests, and I'm not sure why npm is behaving like this...

* Yes I see the irony.
** No staging because $$$, also this is a personal project.
*** I am not directly referencing the same thing twice, it's probably a subdependency somewhere.

==============
Getting Feedback Rant!
=============

When "this is simpler" feedback results in a function of 500 lines of code.

When I get "don't do X" in the feedback. Thank you very much. What do you want me to do instead?

Unclear feedback.

When the feedback giver changes his mind after I applied the changes!

When applying the feedback introduces a bug.

Simply opinionated feedback that is not enforced by any tool or backed up by any facts.
Please find something better to do in life.

Unactionable feedback.

"Consider X"
I will not consider thank you very much.

"Verify this works"
Duh..

When the feedback giver knows something that you don't.
I know this is a legit case.. still annoying.

"I disagree with the feature"
Go argue with the PM, not relevant to me, thanks!

=====================
GIVING FEEDBACK RANT
=====================

I rewrote the system. Please review it.

No need to review, just approve.

I will change this as part of the next ticket.

I would like to keep it the way it is.
lazy ass..

You can't test this.
It's impossible to test this.

No need to test this.

There's no point to test this.

I'll test this on production.

Not sure why this is working..

Please document this..
Because documentation is like a thing, you know.

Oh, this code is not related to this PR, I just don't want to open a new branch for such a small change. ignore it.

Ignore this.

This will be meaningful in my next change.

Started working as a "working student" in an it company to write unit tests. (which then will be executed automatically - so automated unit tests)

Realised that I write more or less the same code just changing the names and some parameters (sometimes more if it's not an number but a bool for example but it's pretty much the same scheme)

So I bought a tool for 1$ to use "auto complete" on custom templates.(I type testgetbool and the tool replaces this to the test case only asking for the variable name.)

So now I'm writing automated automated tests 😁😅

(which is btw pretty boring but cost & time effective)

Don't you just love it when a client turns around at this time of year and tells you that there is a new project and it's due by the middle of January!

And then they tell you the specs... Wait... What? How? Ummm... So you want a test app that is basically a fully working product that would take months to build ready in 15-20 days.

I'd rather drag my balls along sandpaper and dip them in vinegar...

Hm... Apparently I've been doing TDD all along... it's just that I don't save the tests in a seperate project.

I just keep editing Main() to test whatever i'm working on (each class).

Also the NJTransit site is sneaky as ****. It seems the devs know a bit about how to prevent site scraping by checking Headers and Client information...

Took all afternoon to get this test to pass....

it works in Chrome but not in my code... and even after I spoofed all the headers... including GZIP.... it wouldn't work for multiple requests...

I need to create a new WebClient for each request.... no idea how it knows the difference or why it cares... maybe it's a WebClient bug...

And this is only the test app. Originally was supposed to be built in React Native but that has it's own problems...

Books are too old, the examples don't work with the latest...

But I guess this also has a upside... learn TDD and React rather than just React... hopefully can finish this week...

I'm actually on vacation... yea... i still code like a work day... 10AM - 8PM....

"I don't know about changing that part of the platform"
-"Do you see any other way?"

"No, but this one is pretty complex"
-"Would you like me not to do it?"

"No, but like, really test it, OK? It's a very complex part of the platform"
-"Would you like me to include the phrase 'this was really fucking complex' in the release documentation?"

Sometimes I think my boss is against coding :/

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 ;)"

Nightmare morning. Woke up for the fact that my app in app store is crashing on opening. Yesterday submitted improvements to the app (react-native).

Tested locally on simulator and also on real machine by react-natives --variant Release. Worked ok. But now when I build it with xcode and sent it to app store, it's no longer working at all =/.

Im losing users by every minute. Was able to immediately make a hotfix, but apple has not taken any hurry in reviewing it. Also it's not possible to revert previous version in app store, I just have to submit a new version that will be reviewed. I even called them and they promised to hurry but nothing's happened and it's been like 4-5 hours already.

I got so bad luck because usually in review they test the app, but now they didn't, and this time it didn't work at all. And I thought that testing it by react-natives --variant release mode would be enough, but apparently theres something different when you build and archive it with xcode. I feel my app is doomed now, many of the users might abandon it completely =/.

If I learned something it is that always try to test the last modified version of the app. Even if the modification seems small. Don't trust react-natives --variant release for testing an ios app.

If your unit test has a bunch of mocked up dependencies which you puppet to do whatever the fuck you want. Something could be improved perhaps

- write a test at a lower level if possible where the dependencies can be abstracted away, or you pass down what you need from them
- write a higher level integration test, i.e. which uses real spring context instead of mock dependencies

But my senior tells me that a unit test will almost always mock all of its dependencies, it should only test the logic in it's tiny atomic piece of work. Mock everythign else out.

Devrant, how do you unit test? I'm looking to learn more on the topic and hear how others do it.

Me : Hey, can we add datas in the database so we can test every single possible situation with it ?

Worker : Nah, it's better that you don't touch it, lemme do it.

*Later*
Worker : Hey I've added data to test our code.

Me : *fetch data, see only three similar objects that fits in only a situation, I can't test the others" Thank you, that was really helpful.

It's been almost 4 months since i got my first software engineer job.... They only have me doing test support. Should i be concerned? Or is this a regular thing?

Project for a client, release date: tomorrow.
We handed over the project two weeks ago, for their QA to test everything.
Guess when they complained about having no access.
Hint: it's today

Last week I had an initial interview for a mid-senior C# position, and I got asked to do a technical test to check on my actual skills.

The problem is that the skills required to meet all the criteria in said test are far beyond my actual knowledge, so I'm 100% sure I'm going to fail the test.

Now, the question is, should I be honest with the person that's going to review whatever I manage to do, and tell them upfront that I've never done this or that? Should I even try to do it on the test, even if it's the first time I try to do some of the points mentioned on the criteria?

It's the first time this happens to me, and I'm tempted to just tell them I don't feel capable of completing it, and leave it there.

Just found out that Ruby does not have any formal langauge specification. Instead, they just use the ruby-spec test suite. If your compiler can pass those, then it's probably a ruby compiler.

This is a pure duck typing at a compiler level. LMFAO.

"You'll be doing X, and be sure to test everything you do. But we don't do unit testing. They aren't paying us for that."
- PM to intern coming via college (it's like a forced internship that counts as another subject for the degree).

Debugging a task, that's sending emails to too many customers.
Supervisor: "Never mind, just test in production, there is a dry run flag for the tasks."
Just in case I test locally...
Flags tried:
--dryrun="TRUE" => Error, failed to send mail.
--dryrun=TRUE => Error, failed to send mail.
--dryrun="true" => Not trying to send mail.

If it's THIS PICKY a little more documentation would be nice.
And by a little more I mean: more than the task base class in a giant php monstrosity without phpdocs expecting its code to be self-documenting.