Do you follow test driven development?

I have mixed feeling about this test result

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.

We all did that at least one time

When you don't test EVERYTHING...

Project handover:

"Mmh okay, so what about test coverage?"

Dev: "zero"

Team taking the project "why???"

Dev: "You don't need test if you write perfect code"

Silence in the room... Followed by awkward laugh.

"Tests are only for developers that can't write good codes"

-My senior, 2016

When you get client to test a feature.

Turing test

Your program isn't working. You just haven't found the test case to break it yet.

In unit test
Me: *uses everything I have , writes a program with my own logic, tries to make it better by adding some user friendly features and also documents the whole code*
My Friend:*copies from textbook*

RESULT
ME:9/10
HIM:10/10

"Your code isn't present in the textbook, so I can't say if it'll work but still I've given you marks" -_-
What kinda system is that -_-

Apparently this is "unacceptable" testdata.

Please stop me if I try to name my children test, test1 and test2

Thanks

Is there a natural cure for eye cancer?

Someone called me an incapable, arrogant bitch today because I didn't let them test in prod. We had words.

The monologue from Full Metal Jacket went through my head at one point, and I almost didn't mute my phone in time before I said it rather than just thinking it. I'm not sure I would still have a job if I did, but I kind of wish I didn't mute my phone.

The other side of the coin.

Every company has a test environment. Some are lucky enough, to also have a production environment

Am I a joke to you, windows?

Life as a test engineer.

"Can you work on this ticket? It's kind of urgent."

-- "OK"

"And could you please not refactor? Just get this done."

-- "Why? What's the issue?"

"The logic is complex. We should not break it."

-- "Erm, that's what the tests are for. So yes, if the need arises, I'll refactor. The tests are my guidelines if the logic breaks or not."

There's a reason we create tests. So let's not hinder code base improvements by some random fear that stuff might break.

If breaks due to refactoring, we'll fix it by adding a valid test case during and then fixing the bug.

If my refactoring does not break the tests, I'll assume the code base is stable.

If your code is untested, then we have a complete different problem.

I told my colleague today that he didn't pass the Turing Test.
He did not understand.
Which proves my point.

A billion dollar company just sent me a nice email template.

Probably the dev missed a tutorial.

DEV 101

NEVER USE PRODUCTION DATA FOR DEVELOPMENT

Watching a user test your product for the first time...

Dedicated to All Programmers Who hate Testers

Only write unit tests. It will be fine.

that feeling when

ɴᴏᴡ ᴘʟᴀʏɪɴɢ: devRant Podcast #3 (Feat: Mark Zuckerberg)
─●──────────────────────────
◄◄⠀▐▐ ⠀►►⠀⠀　　⠀ 4:𝟷𝟾 / 𝟷𝟹:37 ᴴᴰ Sound ❐ ⊏⊐

Today I got my programming test back. 50/50 points. I only deserved 40 of them, since I wrote horrible code, so I told the teacher "I don't understand my points." His reply: "I also don't understand." I was laughing for at least 5 minutes 😂

Feedback: Bad UI.

Dev paradox: When you test your new test framework to see if it can test.

The server room is guarded by three guards:
- One always tells the truth
- One always lies
- One stabs you if you ask tricky questions.

When you changed a logic structure but the tests still pass.

True Story . . . .

When your client still need your work to be tested in IE7....next, should I ask whether I need to test it in Netscape?

Me seeing my code can't find ./script.js but debug says it can find it

A quote to live by

How secure is devRant? <script>alert("test");</script>

Class: And this is how you do a Hello World program in C.

Exam: Explain where this pointer of a pointer of a pointer of a pointer is pointing

<?php
echo 'asdf';

ok. php file works.

They said, try new unit tests...

I got through the first stage for a summer internship at Amazon. They send me a link to a technical test with a 7 day deadline to complete.

The link brings me to a 404 page. Fuck.

I contact customer support, reach out to Amazon directly, don't get any response whatsoever. The week has passed and the link is still dead and I s received no word from them.

FML. And fuck Amazon for teasing me like this and for having such shitty technical support.

My favorite dev tool is our automated test suite AKA the users in production

Who has an "Testing Stuff" Project?

Dev: My VM is not working. Something is wrong with VM.
Me: Have you made any changes to the code?
Dev: It shouldn't matter my VM is not working.
[I go and check the Dev's VM.]
Me: ಠ_ಠ The build output literally states your unit tests failed

Currently waiting to pass a test in order to get in a French dev school next year. Wish me luck!

When you learn to write tests..

FUCK THE RECRUITERS WHO ASK US TO MAKE AN ENTIRE PROJECT AS A CODE TEST.

Oh you need to scrape this website and then store the data in some DB. Apply sentimental analysis on the data set. On the UI, the user should be able to search the fields that were scraped from the website. Upon clicking it should consume a REST API which you have to create as well. Oh and also deploy it somewhere... Oh I almost forgot, make the UI look good. If you could submit it in one week, we will move towards further rounds if we find you fit enough.

YOU KNOW WHAT, FUCK YOU!

I can apply to 10 others companies in one week and get hired in half the effort than making this whole project for you which you are going to use it on your website YOU SADIST MOTHERFUCK

I CURSE YOUR COMPANY WITH THE ETERNITY OF JS CALLBACK HELL 😡😤😣

World class Korea's Scratch (yeah, the orange cat scratch) Test

You see the blocks, see the requirements, then DRAW the scratch blocks and do block coding IN PAPER.

WTFFFFFFFFF

no, no, no, no, no, no, no, no, no, YES! Wait... why did that work?

Was in a meeting today with a team I just joined, I asked what they used to write tests.. they said they don't write tests because no one would see them..

This is crazy right?

Thanks to Devrant I've learned about rubber duck debugging. Never heard of it before! It reminds me of a story many moons ago when I worked for a certain multinational company as a business analyst. The company brought in some consultants who basically stole the work my team was already doing on a big project (a horrendous series of spreadsheets linked to data coming from the core systems) and sold it back to the company for an insane amount of money as their idea.

When they launched the new product, the team I was in was asked to test and review it. It took my colleague ten seconds to bring the whole thing to its knees and trigger a corrupt data export back into the core systems. Bearing in mind this external company somehow managed to charge tens of thousands of pounds. So what did my colleague do? Hack the system? Some kind of complicated sabotage? Nope. He typed "FISH" into one of the spreadsheet cells! Thus the FISH test was born.

That day I learned several things: it's easy to break things with a fish; the importance of validating your input; and the satisfaction of showing up the smug bastards who stole your ideas and work.

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

I was convinced by a lot of people here so let's try this out...

Wrote a C++ program that calculates the binomial coefficient C(n, k) using a 2D vector of 64-bit unsigned integers, and without thinking gave it the input 65535 for both n and k to "stress test" it. Only after my laptop froze did I realized that I should have upgraded the RAM to 32 GB before pulling of this stress test.
Felt like a dumb user afterwards ☹️

My PM once inserted test data directly into the dev database [ We do have an admin panel ].

Took screenshots of what was not working properly with the imagined data.

Posted them on the WhatsApp group.

Greets me in the fucking morning with "I WROTE TEST CASES YESTERDAY".

FTW

-Why don't you get married?
-We are testing each other for bugs .

Had a first test-run of my new first app (Cordova)!
I deserved this

When I want to try a trial version of a software and it requires a credit card

yay! Almost done learning basics Nodejs REST :D

Now time to learn how to make gitlab auto build and test, then new features to my little project

Next in line:
Testing UI in React Js/Native T_T

The only book that will never be written

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

I don't always test my code...😬😬😬

I just found out at my company it is policy to perform random drug and alcohol testing of all employees. I guess this makes some sense for other parts of the business where people use heavy machinery, etc. but they also test office workers.

I don't take drugs and I never drink during the day but I don't want to be tested. I am a professional person and I am trusted with development of our software and valuable internal and client databases so why cant they trust me with this? There are many developers who produce poor quality work even without any drugs, etc. Surely the quality of my work is enough.

Apparently here in Australia if I am asked to take a piss test and refuse they have the right to sack me. If they ask me I think I might resign.

I think ill root my phone now.

Call the Android paramedics if you don't hear back from me.

!rant
Wrote my first unit test. Strangely feels satisfying.

Friend of mine: so I wonder how do you test your applications in the startup?

Me: testing? *grabs his coffee laughing*

Actually we have a complete build pipeline from commit/pull-request to dev and production environments. No tests. Really. We are in rapid product development / research state.

We change technologies and approaches like our underwear (and yeah, this is frequently). If we settled some day and understood the basic problems of the whole feature palette, we'll talk about tests again.

Taking the test that I have been waiting for 2 years. Wish me luck!

I got a ASP.NET and SQL test today from my bootcamp

Wish me luck devranters

finally started test driven development

Chrome is getting its ass whooped and then crying like a whiny bitch.
Using 90.1% of CPU.

PS: I have a i7 8th gen processor.

In my first year of college right now, and on the first test we had to write some C# ConsoleApplications. We got instructions of what we have to taken as input, what we had to do with it and output it to the console.

I've tested them all and they all work correctly, which was the main objective. I have used the correct data structures, but I didn't get top mark. Instead, I got lower because "I didn't do it her way".

WELL F*CK YOU TOO!!! I hope this is not how every test/exam goes

Sometimes I get frustrated so I grab a decommissioned computer and take it to the roof, then I watch it plummet 4 stories to it's death.

This hangs in the test-section at our office 😂

I was just about to post on here asking for a final round of beta testers for my web app before launch, and just before I hit “post” I thought of a massive issue.

FUCKING CUNTSTICK

Typos kill, kids! And deploying to production.

Instead of "for item in items" in my script, I accidentally did "for items in items". Thus, an exponential loop has been entering things into the database for the past few hours before I found the place to fix it.

By the way, this runs on cron every minute. So there are processes still running exponentially right now, possibly 180+.

Yeah, I'm setting up a a test server instead now.

Good guy teacher doesn't care if you write Javascript global functions wrong on a test because "your editor will fix that for you"

Strange definition of "fast".

how not to name tests

The feeling when you completed all tasks but one in the programming test 😣😩🤪
No, I can't be happy because I could have had 30/30

TFW you’ve been trying to debug an issue for over an hour and you find out you typed:

variable1 == variable2

Instead of

variable1 = variable2

AARRGGHHHHJJHHHHHRIFNRIDKEJXJDJ!!!!!!!

😔😔😔😔😔

Just fuck you, you and your "documentation"...

When people use Thread.sleep in unit tests to delay execution of threads

Fuck the tests...

Apparently the fire hose in our building wasn't connected to the water main, because the legislation stated the building owner had to install a fire hose, not connect a fire hose to the water main.

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.

Just received a test for a job I'm interviewing for. I was interviewing for a C++ position. Practice test: Create an REST API using SpringBoot, Spring Data, document with Swagger and implement continuous integration testing.

To be fair, I also mentioned I'm fluent in Java. But I've never touched SpringBoot or done any backend webdev, since my intention was to never get near it.

Deadline: Sunday. Game on...

Unit testing is bullshit. Junior spotted!

*has a test in school on html and javascript*
*Studies a lot and checks to see if code works*
*it works*
*goes into test confident*
*None of the Javascript works* (legit nothing)
Kill me

Not sure if it was 2016 or late 2015, but it's a fun story anyway (and if it's not you'll at least learn something from it).

Back at the time I was quite new to unit testing (weird how it has become second nature in a years time). I was writing some software that was supposed to send out some SMS to customers. Of course this had to be tested. However, it was a bit difficult to test (or so I thought) without actually receiving an SMS to know if it was sent. So I decided to use the live API key to make sure the sending of SMS was actually working correctly. I tried it a few times but didn't receive an SMS. So I kept working on it and running tests.

The testing setup I had at the time was just a continues loop that went through all tests to make sure it all still worked (I've moved to only checking on file changes now, but that is besides the point). Keep in mind I was still running these tests, in a loop, with the _live_ API key.

So the end of the working day arrives and I go home and sit in the train. All of the sudden I receive some test SMS. I was thinking "hey nice, it did work". Then I started receiving more. It soon turned out to be an alarmingly big amount of SMS. It stopped around 100, but don't think that was the end of it. Oh no. I had changed the number to send the SMS to from my own number to a different number (+31612345678 to be exact, which I found out later isn't an actual phone number. I really hope I was right about that). I was beginning to become nervous, but there wasn't much I could do.

The next day I returned to work and checked the API for sent SMS. Turns out I had sent a couple of thousand (I think between two and three thousand) SMS in a couple of hours. Most of them to the test number I had supplied.

This probably cost the company a couple of hundred euros. Luckily my colleagues and team leader all thought it was pretty funny, but did tell me not to do it again. And I haven't of course.

Lesson learned: don't use live API keys during testing (among other things :)).

So yeah that was probably my worst dev experience.

We had a unexpected math test on thursday. Our teacher had the questions on his pc, when suddently it turned off. The power didn't drop, when he turned it back on, it turned off again. We have been saved. Btw it was windows 10 on hp aio

Discovered yesterday that my boss does tests with production database... and I'm responsible for the fucking backups and he doesn't even care to let me now when so I can at least schedule one at slave. Come on... it's not that hard to let others know or test on your own machine...

!rant

Hahahaha just typed "teste" (Portuguese for test) in duck duck go and it showed me a picture of testicles ( I guess...) With huge "Testicle" written above it in the middle of the office hahahaha

Hope no one saw that, it was funny.

"We need more test coverage!"

it("should test that function") {
subject.function();

expect(true).toBe(true);
}

Coverage goes up 30%

"Awesome! Now we're TDD!"

My co-worker, still studying but working as a "senior dev", just decided that we don't need a test/staging environment anymore. We just "validate" (we also don't use the word "test" anymore) newly created features in production.

Makes absolutely sense...

Thank god I have a new job from february on!

Public test of an assignment I had to do

When you run your test suite with 320 assertions in 64 tests and it all passes..

Something is very wrong somewhere x)

Unit testing in JS be like...

Rant about the Hungarian corruption.
Today I was on a driving test with two others, I was the last one.
They just flat out told us that two of us will pass, the first two who bribe them(the driving instructor and the inspector)
I was the last in line, and both paid before me so I failed my driving test automatically and I have to retake it(because if all three pass, than attention is brought onto the corruption), and even have to pay the fee to be able to retake the exam, and now I will have to bribe them too, so I can pass.
This pisses me off so much, I wish I had alexdelarge as my personal rant writer so he could express my pure anger and hatred.

So first of all I'm not a dev.

I'm a software tester and my test manager is a douche, but this is not it.

Today I went to the end user place along with him to teach them how to test properly and how to manage the software test cycle in JIRA.

I did a demo and showed the users the software the dev team developed and of course there were a lot of rants about it.
Users noted down a list of things to be changed and we kept going.

By the end of the demo, my test manager started discussing the fact that I told these guys to open Bugs without test objects on Jira.

I mean, we don't have a test cycle or test cased yet but these guys found issues already, what's the point?

So here's the funny part.

He then starts telling users (which ignore testing fundaments) to create a test cycle called 'meeting of today dd/mm/yyyy" and create tests below it which were named with the names of who created them.
All of that without a logic and ignoring the fact that these tests were not tests.

I was laughing my ass off while assisting this total mess and I almost lost control.

And this is my manager.

Luckily, tomorrow is Saturday.

I'm a female software dev and I just realised: if I apply th Bechdel test to my life on an average day: I'd fail. I'm not boy crazy, I'm just constantly surrounded by men. Because of my studies most of my friends are male, there are 5 females in the building where I work so of the people I see every day that leaves only my mother (and my dad's usually in the room when we talk).

When your code has had it with test too.

Sometimes they pay off...

Stupid me.
We were on a time crunch for giving a demo. A friend wrote a piece of code and he said it was working exactly the way it should be and that we can directly transfer to my machine and run it. He ran the piece (on his machine to show me) and it worked.
I take the source from him transfer it on my machine (because mine was going to be used for the demo).
Demo begins, everything goes smoothly ...all up until the point of the last module demo. Alas, the transfered module didn't work. Tried debugging during the demo as everyone was cooperative and patient. Turns out I hadn't done an initial setup required for that module. Embarrassed! 😓
Should have tested before the demo. 😞
FML. But from that moment forward i make sure to test every code I get from others as well as the one I write.

For anyone planning to ask me, I don't remember what the piece of code even did. It was a small time side project with a company. Not revealing the company's name.

unit testing

Been going interview crazy this week! The Dev rant community has helped me so much I'd like to thank each and everyone of you for helping me finally get running!

Have my first coding test to do today, have to build the attached file and i'm excited to get started! If you spot any pitfuls please let me know!

Thanks you guys so much! Will let you know how I get on!

Borrowed from Reddit and Twitter:
Everybody has a testing environment. Some people are lucky enough enough to have a totally separate environment to run production in.

Huh?....

for ( let i = 0 ; i < Number.MAX_SAFE_INTEGER ; i++ ) {
console.log("I will never write code before writing test again in my life 😭😭")
}

Can we fix it?

BANE OF MY FUCKING EXISTENCE. STOP POLLUTING MY PRODUCTION CODE WITH TEST CODE, YOU FUCKING CRETINS.

When you made business logic changes but the unit tests still passed

@tahnik has been fighting me for days over which one looks better. Time to see what you guys think.. top or bottom

Hoo lets do this app on windows with Visual Studio, never done windows desktop apps and I want to learn :D
....
....
2 days later : boot -> linux -> eclipse -> files -> new Java project. 😑😑

Not for me sorry...

I'm starting to think, that these programming tests that companies give out, are just a way for me to their work... especially when they don't reply.

Some one at !DEA CELLULAR not doing his/her job well :D

a lesson that I learned the hard way: Don't test a code or a library on your master branche, in other words: don't shit where you eat.

What's your go to "test" user and email ? I always go with Cyril Figgis from Archer

I'm a programmer who is still learning, and I've been having some nasty impostor syndrome lately. How do you deal with it? And does anyone know some websites with good programming tests/quizzes? I want to see how much I know.

(also first rant yay)

Written coding test, first question :

Form the minimum spanning tree of the given graph using Kruskals algorithm.

Plot twist : No weights given. Assume unweighted graph

Does anyone want to criticize my c# code for a quiz game I made in like 10 minutes?

It looks like Im torturing kids :o

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

You lousy fucking test class of an ass wipe,

TLDR; it fails and it passes all at the same time.

So during a deployment, one of the pre-deployment test classes fails, not something anyone has worked on so figured I run it manually to see what’s going on, but no the shit of a thing passed second time around.

Now because we can’t deploy without 100% of the test classes passing so I have to organise another deployment which it fails again. Fuck this,

Unprotects master

Git checkout master
Git merge dev
Git push master -f

Protects master

Skrew this!

Well would you look at that, it works now 😰

About to send a test project to a cool company, wish me luck!
Hopefully everything works 🙈

I have a UML test in a couple of hours 😩
Wish me luck....

I am learning about CI/CD and DevOps, and i finally made my first build/deploy/unit test script.

I use arch btw

Had my junior test at work yesterday, and...oh boy. I don't think I've ever been so stressed in my life.

>inb4 "welcome to the real world kid"

Yeah yeah I know but god damn, this was too much. I heard from seniors that you get used to everyday stress, it comes with the job, but junior test ( aka "stress test") is the breaking point for most "new" arrivals.

The test itself tho is not even that hard. Dealing with so much stress and time pressure for the first time is what gets you. Not knowing what happens if you don't pass certainly doesn't help.

I broke down at one point and even after finishing, going home (got no sleep) and coming back today, that feeling of hopelessness is still there.

No real point to this rant, I just needed to vent

I spent the entire weekend studying C#.

..Forgot I had a test today. Whoops.

I really want to stress that we should add the ticket for adding the missing test cases in *this* sprint and not postpone it any further.

-- "Isn't there something more important to be added instead?"

There. ALWAYS. Is. Something. MORE. Important. The real problem was that we implement the test cases in the past to begin violating our definition of done. We have to fix and one point and we have to own that decision as nobody else will care about passing tests and test coverage. It's our job to care for that.

Yes, we can instead focus on all the other high-priorities task that should have been done yesterday, yet that won't change the fact that large part our codebase will remain an untested messy blackbox just asking for weird bugs and wild goosechases in the future.

Don't hide behind "high priority tasks". A job is done when it is fucking done and tests are part of that. Hurrying from one important task to the next will just mean we'll never do it. There is no better time than right now.

If code coverage got left behind in the past, then we'll have to suck it up in order to fix it as soon as possible, otherwise we'll just suck forever.

Fuck...
I'm not getting that job then.

So I just had one of those interview coding tests on hacker rank and screwed it up big time.

I'm a C# guy and it was a Java position. I worked with Java, like 10 years ago, and they're pretty similar so I brushed up over the last week when I had free time.

Absolutely blew it. It's not like it was hard, I just got into one question (of 6) and it ate up all of my time. The task was simple, make a JSON call, read the data, check if you need more calls, pull out a data field from all the concatenated results and return it in a sorted list. ONE HOUR it took me. A combination of not knowing the API well enough, simple syntax errors and relatively slow compilation.

Godammit.

The next question was implement an Object hierarchy but since I'd run out of time, all I got was the class declarations before the timer ran out.

fuck, fuck, fuck.

I guess the test did it's job and weeded out someone who can't contribute to the team...

I guess everyone in their company knows how to write unit tests except us.

Unit test works, unit test works... commit it, push it, take screenshot of it, and go to sleep... peacefully...

Am I being too literal with this test question?

Hey fellow ranters. You all have probably seen me CONSTANTLY alluding to or outright mentioning the fact I was working on a web app, before it was strictly for devs but I've decided to broadened the scope.

So I have the MVP (minimum viable product) 95% built-out, so I think I should be able to move to beta testing in about another 2 weeks (give or take a week). I was wondering would any of you, when the time comes, be open to trying it out & giving me feedback??

Easy to pass the tests if you don't write any.

Had some fun running automated UI tests today.

Background: My project is a cloud based tool for running automated tests against a 3rd party SaaS product, so when you start a test run, it opens a Firefox window and runs some selenium automation against the 3rd party product.

Our UI tests also open a Firefox window to log into our local env and run some selenium.

Today I tried to run 4 of our UI tests in parallel.

So each test case creates a Firefox instance, and each of those starts a test run which creates another Firefox instance, sometimes 2, depending on the process being tested.

In short, at one point I had 11 different Firefox windows open, all running selenium automation.

My laptop sounded like it was trying to take off...

Whats your test/experimenting variable name?

Unlike foo,bar,baz..
Mine is banana/baba/apple 😂

toilet.flusher.show()
... hmm ... not a UI issue.

toilet.flush()

Crash: "No function found"
... must be private, mother fu**** ...
...
...
// ¯\_(ツ)_/¯
user.leaveFloater(true)

When you let your friends test you application. All of this happened in about 3 seconds. I directly shut down the server haha. Translation: "page ... couldn't be loaded."

WHY WON'T YOU LET ME HAVE THE SATISFACTION?!!

My code works, their test case is garbage.. 😒

I'm relatively new to the whole development and stuff, so I have no idea how usual process goes.

So when my project moved onto closed beta, I thought I could rest a bit.

NOPE.

Apparently half the shit I've done sucks so much and I need to debug the shit out of it.

Bless the testers.

Got a technical test for my job application 4 days ago, a very simple web project, tasks should be done in native JS, within 50 minutes.

Simple but tricky and I panicked when I did it, can’t even remember half of what goes through my mind when I was doing it.

Then after I finished, I recapped my answers, AND the instructions.

First mistake, there was an injected script in the provided json data, and I dealt with it with too much workaround. What supposed to be a simple way of rendering content turns out to be layers of workarounds. And it wasn’t even perfect. I want to strip the script but I didn’t manage to find the right regex in time.

Second mistake, I didn’t read the instructions thoroughly. The function was supposed to sort the data on descending order on a key and if there are equal values, sort those on ascending order based on another key. I just sorted it on ascending, and forgot about the rest.

Third and worst mistake of all, again, didn’t read the instructions, I was suppose to change ONLY the JS file. But I modified some part of the HTML because I was in a frenzy and didn’t want to bother writing 3 lines of

document.addEventListener

This could have been prevented if I wrote those 3 lines, aside of me reading the instructions or not. And I just might able to justify the other 2.

But well, it’s done, it’s submitted, and it was a good experience.

I still feel goosebumps everytime I opened the folder to see my answers.

Works in production?

Yes: Copy changes to dev and test.
No: Start humming and walk away from the computer.

The job I recently accepted scores a facking 5 out of 12 on the Joel Test 😦😦😦

I'm glad to have gotten a job, but it seems like I'll be looking for one again soon

I just had the most embarrassing moment in programming... I am writing an administration / client / invoice webapp and I was testing an export function that worked locally, because everything that was being exported was inside the folder.

So I exported the files in test production, but some invoices didn't exist. So when they don't exist, the system creates a new invoice.

Because I was running on the test production (with client data) the system emailed the created invoices to the clients.. now I have to contact some clients and tell them the invoices were sent accidentally.

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

Unit test!!!
Grrrrrrrrrrrr

TFW when you discover your tests have bugs, and your code was broken all along 😡

Is this what I think it is?

Some one is testing in production... Shall I report this ? (I'm student btw)

Fixing unit-tests that expects 2017... kills my motivation at first workday this year.... I hate my coworker -..-

It wont go down, he said, it can't crash he said,
several DDoS later
You won your coffee and honor,
Touchè

Why we always found the worst problems 2days after going to production? No matter how we tested?

Coworker: Do you use testenv or prodenv?
Me: I just Test :/

Guess what I'm testing!? 🚧

Just passed technical verification for senior dev, then went to subway. Question from the lady behind counter where tougher :P

Test...

Today I spent an hour teaching a QA guy some GCSE level maths to be able to test my code

That moment when I finally got tests and CI up and running for my project.

The more I work on the backend forms validation side of my .NET Core project the more I understand how to fuck up web forms in general... 😈

Never underestimate the necessity of a backend validation other then the frontend one. 👿

Me: Where is your unit tests?
Dev: I tested manually and it worked.
Me: What if there are changes to the code in future?
Dev: We'll manually retest the implementation. It'll be fine.

*flip table*

Sometimes I commit fixes for issues on my crypto exchange api repos without testing them and tell the issue author to test it themselves because "I don't have api keys for the respective api" to test it.

I'm fully registered on every exchange from here to Japan. 🙄

Did a technical demonstration test to assess my digital skills for a job today...on paper.

When I'm stuck at something and can't think of a way to solve it, I just keep running the unit tests and stare at the screen. And then youtube. And then I feel terrible.

Waiting for the feedback after sending a test version to the customer

Worked all day yesterday (8am to 11pm) trying to get a regression test developed in ReadyAPI to behave properly in Maven/Jenkins. All I have to say is that I have some words for Smartbear.

I have just been invited to a Technical Test Server for the game I currently play most, but I have some development in progress! God my life is full of hard choices!

Spoiler: I'm playing on the TTS right now :x

When you are new to a technology and language, but have to make full use of its feature.
You know, make tests, implement production code, planning deployment, build a CI. All by myself.
No regrets, though. Challenge accepted!

We've told our client they can test their brand new distribution modul with a new test account already 42 times (not exaggerating, I counted). At least half these, we've sent also the test login data which they could use.
Just now, a new issue message from them says distributors couldn't see some data, we should fix the problem. Well, they already can't see those, but client has logged in with their own account again for testing...

I’ve just received a Code test to make an entire game before Friday and I’m kinda sh**ting myself...

Unit test for the sake of humanity

*Executed maven build*

Me: What's this "no tests found?"
Senior: Nevermind it's not important. Just check if your code works.

!rant

New to linux

So I deleted all of my games, pron, and installers just to free up some space for testing dual boot in my laptop.

I will study all the basic commands in terminal and make use of my time to coding.

Yahoo Mail

When big enough number is not big enough.

If compiling a java app is as easy as running a node app 🙄🙄

How do you identify a programmer with just one question? Ask him to pick a number from 1 to 100.
(Disclaimer: 1% of margin of error).

Happy halloween!

My halloween schedule

1. Start 3 new game projects

2. Study f***ing C for the test in coming Saturday and Sunday

3. Study math for the test in coming Sunday

4. Play werewolf in codrTalk (hopefully)

5. Start my f***ing logo after a disasterous fail.