Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
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.17 -
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.18 -
Testivus On Test Coverage
Early one morning, a programmer asked the great master:
“I am ready to write some unit tests. What code coverage should I aim for?”
The great master replied:
“Don’t worry about coverage, just write some good tests.”
The programmer smiled, bowed, and left.
...
Later that day, a second programmer asked the same question.
The great master pointed at a pot of boiling water and said:
“How many grains of rice should I put in that pot?”
The programmer, looking puzzled, replied:
“How can I possibly tell you? It depends on how many people you need to feed, how hungry they are, what other food you are serving, how much rice you have available, and so on.”
“Exactly,” said the great master.
The second programmer smiled, bowed, and left.
...
Toward the end of the day, a third programmer came and asked the same question about code coverage.
“Eighty percent and no less!” Replied the master in a stern voice, pounding his fist on the table.
The third programmer smiled, bowed, and left.
...
After this last reply, a young apprentice approached the great master:
“Great master, today I overheard you answer the same question about code coverage with three different answers. Why?”
The great master stood up from his chair:
“Come get some fresh tea with me and let’s talk about it.”
After they filled their cups with smoking hot green tea, the great master began to answer:
“The first programmer is new and just getting started with testing. Right now he has a lot of code and no tests. He has a long way to go; focusing on code coverage at this time would be depressing and quite useless. He’s better off just getting used to writing and running some tests. He can worry about coverage later.”
“The second programmer, on the other hand, is quite experience both at programming and testing. When I replied by asking her how many grains of rice I should put in a pot, I helped her realize that the amount of testing necessary depends on a number of factors, and she knows those factors better than I do – it’s her code after all. There is no single, simple, answer, and she’s smart enough to handle the truth and work with that.”
“I see,” said the young apprentice, “but if there is no single simple answer, then why did you answer the third programmer ‘Eighty percent and no less’?”
The great master laughed so hard and loud that his belly, evidence that he drank more than just green tea, flopped up and down.
“The third programmer wants only simple answers – even when there are no simple answers … and then does not follow them anyway.”
The young apprentice and the grizzled great master finished drinking their tea in contemplative silence.
Found on stack overflow https://stackoverflow.com/questions...8 -
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 -_-12 -
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.13 -
"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.3 -
Every company has a test environment. Some are lucky enough, to also have a production environment3
-
I told my colleague today that he didn't pass the Turing Test.
He did not understand.
Which proves my point. -
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 😂8
-
When your client still need your work to be tested in IE7....next, should I ask whether I need to test it in Netscape?4
-
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 pointing1 -
If any of you guys is (or was until recently) a developer for Smappee, the payload message test was a success
1 -
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 😡😤😣9 -
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.12 -
I'm not scared of a computer passing the Turing Test. I'm terrified of one that intentionally fails it.
Source: https://reddit.com/r/...2 -
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?9 -
"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 ;)2
-
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.3 -
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 ☹️
8 -
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 -
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
7 -
Continuation of rant https://devrant.com/rants/975261/...
I PASSED THE TEST!!!!! YEAHHHHH
Now only an interview left. Please....
If i fail this interview, no more tries.
Wish me luck.
From this point, all personal projects and requests will stop.7 -
"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.)8 -
!dev
Me in the bus to Office
me: *press the stop button*
me: *see my Station driving pass me*
me: Sorry? I pressed that button?
bus Driver: Oh! You wanted to Exit?
me (thinking): no, this is a unit test and your unit just failed….
me: uhm, yes? thats why I pressed that button...5 -
> Some unit test is not behaving well in my local environment
> Weird, I should print the response from the server, maybe the client isn't receiving what I think it's receiving
> see this
SAY SIKE RIGHT NOW
9 -
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.3 -
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 goes7 -
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
13 -
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.4
-
It's 4 am in the morning.
I have an important test at 9.
My laptop decided now was just the right time to make the screen go black.
Sometimes Murphy just politely hands you your ass.1 -
Good guy teacher doesn't care if you write Javascript global functions wrong on a test because "your editor will fix that for you"
-
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.11 -
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 CUNTSTICK9 -
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.1 -
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 😰 -
How many people have faced this?
When the test suite completes 99% and fails on one stupid test thats not even part of what you updated.5 -
When you run your test suite with 320 assertions in 64 tests and it all passes..
Something is very wrong somewhere x)6 -
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.1 -
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/302 -
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...4 -
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!1 -
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...1
-
You know you have a quality teacher for C code when you are writing a test and you have to write the code on a piece of paper4
-
"Let the developers consider a conceptual design,” the King said, for about the twentieth time that day._
“No, no!” said the Queen. “Tests first—design afterwards.”
“Stuff and nonsense!” said Alice loudly. “The idea of writing the tests first!”
“Hold your tongue!” said the Queen, turning purple. “How much code have you written recently, anyway?” she sneered.
“I won’t,” said the plucky little Alice. “Tests shouldn’t drive design, design should drive testing. Tests should verify that your code works as it was designed, and that it meets the customer’s requirements, too,” she added, surprised by her own insight. “And when you drive your tests from a conceptual design, you can test smarter instead of harder.”4 -
!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.1 -
"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!" -
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.4 -
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!
15 -
for ( let i = 0 ; i < Number.MAX_SAFE_INTEGER ; i++ ) {
console.log("I will never write code before writing test again in my life 😭😭")
}5 -
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.2
-
So, I just did stress test on my code out of curiosity.
Umm, the results weren't very satisfying to say the least. 😅
Now, I'm under a stress test! WTF!7 -
Me: I finished the tests! Almost 1000 lines of testing data. They're actually pretty thorough. We're ready to push the changed.
Manager: That's great! But the requirements changed. We're gonna change the schema and queries quite a bit.1 -
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.5 -
@tahnik has been fighting me for days over which one looks better. Time to see what you guys think.. top or bottom
22 -
A designer pointed out that at a certain screen size (small tablet or large mobile), a menu was overflowing but had not yet collapsed into a toggle.
The manager comes to me and asks "why don't we have a unit test for that?"6 -
*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 me6 -
Been a long ass day, then some later afternoon prepush testing that went long and wrong which led into night - and after all was said and done we had to throw our hands up and say...
https://youtu.be/Qy-Y3HJNU_s
-
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.2 -
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.3
-
The "unit" in unit test does not mean your ENTIRE APPLICATION. Ever heard of scope!?
I am amazed how often people write overblown test setups, mock hundreds of unrelated services, just to test one tiny bit of logic.
That bit of logic could have been a pure function.
For that pure function you could write a dead simple unit test. Given that input, I expect that output. Nothing more, nothing less. (It helps even more if the pure functions only accepts primitives, like string and numbers, or very simple immutable value objects).
No I don't care that the service is used by another service, as your mocked interaction also doesn't test the service as a whole but you just assume the happy case most of the time anyway. You want to test the entire application? Let's not use unit tests for that but let's use a different kind of test for that (integration test, functional tests, e2e-tests).
If you write code in a way that easily allows for unit testing, your need to mock goes away.1 -
Written coding test, first question :
Form the minimum spanning tree of the given graph using Kruskals algorithm.
Plot twist : No weights given. Assume unweighted graph4 -
Someone mentioned being frustrated with people who answer "either/or" questions with "yes". I figured out why. They are not human. They are a robot and their processing of language is failing.
A simple question:
Q: The car is red or the car is green?
A: Yes
Breakdown:
The car is red. Yes, True
The car is green. No, False
The car is red OR the car is green.
True OR False
True || False = True
True = Yes
So they dissected the language like a computer treating "or" as a logical OR. This proves they are a robot pretending to be human. They failed the Turing test.8 -
Hi everybody,
what is your Personality Type?
We are currently taking the test at https://www.16personalities.com/ company wide.
My result is “THE LOGICIAN” (INTP-A) ( https://16personalities.com/intp-pe... )
--------
The Logician personality type is fairly rare, making up only three percent of the population, which is definitely a good thing for them, as there’s nothing they’d be more unhappy about than being “common”. Logicians pride themselves on their inventiveness and creativity, their unique perspective and vigorous intellect. Usually known as the philosopher, the architect, or the dreamy professor, Logicians have been responsible for many scientific discoveries throughout history.
--------
As everything I read in the description and explanations of my personality type fits astounding well, I asked myself, what kinds of personality types are prominent on devrant?
So, if you take/took the test, I'd like to read about your results. ☺35 -
I am learning about CI/CD and DevOps, and i finally made my first build/deploy/unit test script.
I use arch btw6 -
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... -
BANE OF MY FUCKING EXISTENCE. STOP POLLUTING MY PRODUCTION CODE WITH TEST CODE, YOU FUCKING CRETINS.
-
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.1 -
Departure: 13.00 Train: test Destination: A1 Delay 18888min
Now it is 15:43 and it is still on...
Finaly poland joins the testing in the prod club!
Station is Wroclaw if anybody is interested.
2 -
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 vent6 -
Unit test works, unit test works... commit it, push it, take screenshot of it, and go to sleep... peacefully...
4 -
During my job hunt as a Java Developer looking for job while on a job just like what every other developers do, around twenty twelve i got an invite from one of the companies i applied for, i wasn't expecting a test though but i was prepared for it anyway. The test proceeds, i and the other partakers were given separate systems and spread out across the room like teams in a football match, i don't know if they planned on making us nervous, it seemed so very awkward. First question was *Who originally developed Java (like seriously???? i almost cummed!) i skipped... skip skip skip. After so many skipping minutes i then arrived at that question ***Check string for palindrome, hmmm i then noticed my system was connected to an open wifi (don't know if it was a dumb mistake or on purpose). I definitely googled and faithful loving heavens i found the website were they got all 21 questions with their answers from (https://simpleprogrammer.com/progra...). I answered all questions using different approach, applied xml commenting, state possibility and outcome of each code block, added wiki references, i flawed the test. Few days later i received a call for final interview, got there and the interviewer was like "Do you teach/lecture on coding or something? cus you really did pretty good on the test the other day", I felt like a god and was like "no, i don't. just did what i had to do". Seems like he loved my reply and i got the job without a second question. The open network is still a mystery to me till date.6
-
Not gonna lie, this week was first time I really got pissed in a awhile. I implemented an apply and buy for a very large (top 5) US bank. There docs specify on an api call. Returns of specific information marked as "Required" hence information that "will" be there no matter what.
After release to production they are testing flow.
Its failing fix your code and let us know when you are ready to test again.
Logging the response from api. All those "required" fields are empty.
Bring it up with there technical lead "In production those fields will always be there!"
This is a production test and well they aren't there.
Still waiting on response while my managers possibly believe this is a fault in my code.3 -
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...6 -
Functional test are failing.
Expected: 7109
Got: 9000
Grep code-base for 7109. No findings. 0_o
Dig through test setup written by a drunk.
Find:
assert(actualPrice === 1800 * conversionRate)
Goddamnit. You shall not calculate your expected values in a test setup.1 -
So I was asked to do a card redesign A/B Test
The results came in
Redesign performs 20% worse
PM’s report says “no significant difference, redesign approved”
He just wanted his redesign to be published
smh, why trouble with A/B Test when results are known faster than during elections in North Korea1 -
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 passed5 -
It wont go down, he said, it can't crash he said,
several DDoS later
You won your coffee and honor,
Touchè -
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."
2 -
Works in production?
Yes: Copy changes to dev and test.
No: Start humming and walk away from the computer. -
tests? ain't nobody got time foh dat. my brain already does all the job. it assumes and says to myself "all tests passed ✅" whenever i make quick changes
i like to live dangerously 😂1 -
Public Service Announcement;
Test your shit!
That will be all!
Source: https://dev.to/stealthmusic/...
1 -
So... I take over this one ticket to test... the ticket mentions some visual component popping up when a button is clicked. It says there is a success and a failure message. The title of the story also mentions another functionality.
I start testing and some fellow QA asks me why I'm testing in this environment. Turns out, three people are sharing one environment and three different things are deployed...
I ask the dev whats going on because I heard there are multiple people deploying stuff...
He just tells me "oh, my changes are deployed I just checked".
I tell him that it's not about that but about communication and testing one thing at the time. Then I tell him, that I wouldn't test until his stuff is the only stuff there.
Some time later he hits me up again, now with the env to himself.
I test and quickly I see, that there is only the positive message even when I make sure that the backend is not reachable. I tell the dev what I found and he tells me "oh no, it's just the implementation of the popup thing, it's just frontend for now"...
I tell him, that the ticket should say so.
No answer for like 1-2 hours. Then I get an "ok".
End of the day.
Next day I come in and the fellow QA tells me, that the dev asked him to test the ticket.
I ask him if he changed anything about the scope of the ticket, he says no...
I'm like "ok... know what... begin testing and then tell him what I already told him".
So he's testing and then tells him again to update the scope.
Later in the daily the the dev's update is besically "they won't test my ticket..."
It would have taken him like 1 fucking minute to update the ticket...
The whole QA team was always trying to being helpful and even when the tickets where sometimes not 100% clear we always made it work... but now we are more and more going towards "MR does not meet ticketdescription, fix it" and "I don't care if its just a small thing... fix it and then come back to me"...
Seriously frustrating some times...2 -
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.
-
Ok so, why not. Let us send a bunch of sms tests, they are cheaper than push notifications, right?
4 -
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.2 -
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 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 -
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. 🙄 -
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 soon4 -
Who else works at a company that enforces test driven development? And after doing TDD do you think you could ever go back to NOT doing TDD?
-
So I'm currently "assigned" a task in which I need to fix a slow query problem, which isn't a big deal. The biggest problem is that the original team of this project haven't got any means to develop things on your local machine. Looking at their docs and scripts, it seems like everything is deployed to a dev server. But whilst looking for details for this server, I found out that the network team have decommissioned the server!
So my dilemma right now is that I can't test any of my fixes on anywhere besides staging, or possibly production! Inheriting projects is the bloody worst!5 -
Ugh... some people...
Just left the office early because of the toxic climate. That one infamous collegue is basically unable to communicate without being a narcissistic 5-year-old and was arguing whether we should write a test (I was going to write the test) that would need a single additional branch in the build system.
(The test was for a parser and it should test whether it can handle absolute paths. A simple regression test with a file and an expected output. Because absolute paths are different for every platform and user, the files to be parsed would have to be generated with appropriate paths before the tests were run. Well that would require one single python script and a single line in the script that runs the script and DONE)
Well that guy was unable to focus on his own work and started an argument about whether that test was necessary.
Even though I still think it is necessary, it might have been a reasonable argument if he would have acted more agreeable. But he was saying the feature was useless anyways "everyone will use relative paths only anyways" and "because noone here cares a ratass about maintaining the tests it will all fall on me again" ..
Wtf was this guys problem, I (CAPS) was going to write the stupid test and since when do we not write tests in order to better maintain our product? I get that he worries that the test environment will get more messy, but thats better than having the product code go messy or unfunctional! And c'mon guys, how are absolute paths a redundant feature... -
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).5 -
Make someone create a shitload of tests for your shitty code, then don't give a shit when your commit break almost everything, finally; make the guy who wrote the tests figure your shit out.
Bonus points: Whine about something that's been broken for weeks "without you knowing" when the test suites have been saying exactly that since your commit.1 -
I just want to use Jest to unit test my Typescript classes, but that appears to be impossible!
Testing the compiled Javascript instead doesn't seem to recognize any classname at all :( -
Today I read a great article on mutation tests, how to use and why they are important. It looks like a great thing, but...
I have never wrote any unit test in any of my jobs. Nobody in my workplace does that. And now it seems like 100% test coverage is not enough (I remind you, that I have 0%), they all should mutate to check if the quality of unit tests is high.
It seems that I'm left behind. I played with tests in my free time, but it seems the more you write them, the better you get at it, so I should be writing them in my job, where I code most of my time. Not only that, of course, I would also want to ensure that what I'm working on is bug-free.
Still, it will be impossible to introduce unit tests to my project, because they are novelty to the whole team and our deadlines are tight. The other thing is, we are supposed to write minimum viable product, as it is a demo for a client, and every line of code matters. Some might say that we are delusional that after we finish demo we will make things the right way.
Did any one of you have a situation like this? How did you change your boss and team's mind?8 -
Wasted 15 minutes by:
Put the `done` in the `describe()` callback instead if the `it()` callback in a mocha test.
1 -
I’ve just received a Code test to make an entire game before Friday and I’m kinda sh**ting myself...12
-
Test: this time, I copy a line with line break, because, when I did this yesterday, it fucked up devRant web.
Not copied:
Five brave knights write code in one night for free, because they like it
Copied:
Five brave knights write code in one night for free, because they like it
Does this fuck up the web-version? If so, @dfox needs ta parsed a capied text and add the needed line-breaks...1 -
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.2 -
God dammit, I hate my bloody coworker sometimes. He's doing a huge refactor, and committing... which is fine, but he's clearly NEVER run the fucking test suite. I didn't write that much coverage so you could commit something that breaks the build and then fuck off to lunch.
Not only has he not run the test suite, I don't think he's run his changes AT ALL. The bloody modules don't even import the way he's written it now.2 -
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.4 -
Google codelab's logic :
"uncomment the code from a xyz function
run the test
test fails
uncomment the code from abc function
run the test again
test pass
Congratulations you learned test."
Well apparently this is not how world works Google 😥😌😴 -
We had a test in class where one of the questions was "What is SQL injection?" and I wrote what it was and even gave a bang on simple example where I showed how you could end up with a truncate statement on your customer db. The last part of it was:
"This will be the SQL that gets executed:
INSERT INTO Customers (Name) VALUES (' ';TRUNCATE Customers;--);
When I got it back after we had a session of "grade each others work" I got the comment: "What makes this an attack against a database?"
I mean, I'm not sure what I could have written. That it truncates the database? And, correct me if I'm wrong, but if a user truncates your DB, is that not an attack?
-
!rant
[Update on previous rant at the bottom]
So I had the technical test last friday. I did not try to implement any automated test as it is not my forte.
I had three hours to showcase my knowledge of data structures and OOP so I did that.
The test was somewhat long actually, so I left out one part that I did not have time to implement: validation of input files.
Today I got feedback, everything went well, they liked my code and I only got two negatives: Error handling and automated tests xD
Now I'm going to the second phase: phone interviews and they are gonna asks the whys of my implementation.
I'll have to explain why I did not implement automated tests and the girl on the phone told me "they didn't like it much that you had no tests because tests are very important for us".
I guess I'll have to come clean and say that I'm not very strong on that but willing to learn, so I didn't want to risk it doing something I'm not really good at.
I hope it ends up well.
prev rant:
https://devrant.com/rants/1607302/...5 -
I need help for a dev test.
So the company that I work at is hiring a couple of new devs and they’ve put me in charge for test in order to see if the applicants are any good.
When I was hired there were no tests so I don’t have that many ideas for a good one.
Have you guys any good recommendations for a test or what it could consist of?
I’m thinking of having multiple small tests so if one misunderstands the task it’s not the whole test they fail. Would that be a good idea or not?
It’s for senior and junior web developer.
Any idea is greatly appreciated 😀5 -
Confession: a very important feature of the website I'm developping wasn't working for a certain time. The boss wasn't aware because he doesn't go on the site, and I only found out last week because I needed to implement a new feature that used the previous one. Problem: the bug was only on production, not on local (and of course we don't have test server).
I took advantage of the absence of my boss today to clear the situation by making all of my tests on prod. I hope no customer tried to pass a command today, but it's finally repaired. I am both proud and shameful.4 -
About to checkout Gatling for load test to my REST api, any other suggestions?
So far their docs look straightforward to follow, requires scala but it doesn't look that complicated for that particular case.
Dotnet core devs, do you recommend another tool?8 -
This fucking ci/cd test keeps deleting my dB collections and I can't see what the fuck is going on. Circleci is of the devil and I won't stop fucking using it. I must crack this shit😡4
-
Who I hate:
People who put their tasks to ready for (integration) test without even once running it against real services and the actual database instead just the mocks of the unit tests.
=> I want to test business logic, not fix your internal server errors... -
Hello wonderful Salesforce peeps. I need to take the Salesforce platform app builder credential
What is the best site to use as a study guide/ exam prep?
Cause honestly I've been using Trailhead and I feel it's just a big advert for Salesforce and it's so condensed it feels like a beginner course and I'm scared the test questions will be more profound than what is displayed in there.
I am a complete noob in Salesforce but I do have CRM experience, DB experience, Security experience, and programming experience.
Help a Newb2 -
When comments find their way to class tests:
“TODO: Finish conjugation of montre in the whole text”. I had no idea of the conjugation and finished under time pressure so this stayed in the class test (gave it back last second) and I was well aware of it.
Just wondering what the teacher must have thought. Didn’t say (or write) a word about it tho.
Should see if someone tweeted or posted this (I mean someone wrote a book only with examples of stuff like this)
Idk, I should ask if I’m allowed to write class test in an IDE. And set MARK, TODO, etc. Would make them a lot easier.28 -
We have an unit test that tests the average of a sequence of numbers generated randomly using a gaussian distribution. Of course it fails from time to time, it's random! Failing to fail, would mean that the generator is not generating random numbers, therefore failure means success, but success does not mean failure.
Wait, why did we add this test in the first place? -
Your dumb post passes!
var result = qualityService.Evaluate(yourDumbPost);
Assert.IsFalse(result.IsFunny);
Assert.AreEqual(Wittiness.BelowAverage, result.Wittiness);
Assert.IsNull(result.Value); -
Just did an IQ test and got the score of 132. B-)
Are these tests real or am i just dreaming?
i performed the test on this -> http://www.myiqtested.com
21 -
I'm really bad with unit tests
I feel a bit embarassed about it especially cause I do this professionally but I really don't know what to do about it. I thought it would be helpful if I checked out some examples by others but they mostly seem like "self fulfilling tests" and I fail to see their purpose. There have been few instances where I thought a test would make sense. I feel like I have writers block whenever I try to write unit tests and learning by doing doesn't seem to help me much.
Do you have suggestions on how I could get better with unit tests?11 -
So... I have a technical test today (in 7 hours) as part of a job interview. I have a lot of experience in Java but none in TDD or test automation.
I'm pretty sure they use TDD, so they'll probably value it in my review.
Should I try to learn some TDD in the next two hours and apply it in my technical test?
or Should I not, avoiding messing all up and go with my tools and skills totally honest?5 -
When you don't know how to write test:
either you unit test the fuck out of system (couple test test to code) or you don't write anny
-
Something you really should not do:
*adds a new feature*
*build & run*
*See no difference*
Me: "Hmm.. Maybe 1 is not the best test integer, let me pick something higher..."
*build & run*
*INTEGER OVERFLOW EXCEPTION*
Feel free to share your "let me choose anothee test integer"-stories, which gone terribly wrong.1 -
Just spent half a day trying to figure out why the hell were my automation scrips not running.
"There was an exception but the IE JS engine didn't return any error message"
Very helpful
Turns out the dropdowns that looked the same weren't the same. There was a different table for each selected radio button that was getting displayed and the dev tools didn't reflect that in real time.
I managed to notice after spending a while in table hell (we're talking 4-levels deep nested tables)1 -
Let's talk about one of the two hard things in programming - what's your preferred test naming convention and why? I'll have to create plenty of those now, while the project I'm working on is still small, and I don't know which way to go. It's Spring (Java), but I don't think it matters that much 🤷4
-
Hooray! voice is now working on localhost! Now to find a high latency, low reliability connection to stress-test the thing. Do you reckon sending the packets 3 times to echo.websocket.org is unreliable enough?
-
I'm starting to gain a dislike for OOP.
I think classes make it easy for me to think of the entities of a problem and translate them into code.
But when you to attempt to test classes, that's when shit hits the fan.
In my opinion, it is pointless to test classes. If you ever seen test code for a class, you'll notice that it's usually horrible and long.
The reason for this is that usually some methods depend on other methods to be called first.
This results in the usual monolithic test that calls every goddamn method on the class.
You might say "ok, break the test into smaller parts". Ok. But the result of that attempt is even worse, because you end up with several big tests cases and a lot of duplicate code, because of the dependency of some methods on others.
The real solution to this is to make the classes be just glue: they should delegate arguments onto functions that reside on its own file, and, maybe afterwards emit events if you are using events.
But they shouldn't have too much test code classes though. The test code for classes should be running a simple example flow, but never doing any assertions other than expecting no exceptions.
For the most part, you'd be relying on the unit testing that is done for each delegated function.
If you take any single function you'll see that it's extremely easy to write tests for it. In fact, you can have the test right next to the fuction, like <module>.xyz <module>.test.xyz
So I don't think classes shouldn't be used at all, they should just be glue.
As you do normal usage of this software this way, when a bug is discovered you'll notice that the fix and testing code for this bug is very usually applied to the delegated functions instead of being a problem of classes.
I think classes by themselves sound sane in paper, but in practice they turn into a huge fucking messes that become impossible to understand or test.
How can something like traditional classes not get chaotic when a single class can have x attributes and y methods. The complexity grows exponentially. And sometimes more attributes and methods are added.
Someone might say "well, it's just the nature of problems. Problems can have a lot of variables".
Yeah, but cramming all of that complexity into a single 200 lines class is insanity.12 -
Hey! Just curious, is it normal that a technical test/challenge takes me more than a day to do?
I have been interviewed for a front-end role, and was given a react challenge. They said that it shouldn't take more than 2 hours ('hopefully' is what they added at the end). But i've been doing this challenge for a day now and it's only 60-70% done.
It's not complicated, and I do know how to do it, and, even, do it properly, it just takes a lot of time for me to code, i.e. develop components, change webpack when needed, read react materialize-ui (css framework) docs, then destructure json response from the api they provided and put this information on a page, then try to compile to the right format (they want single .html element with inline js and css as a deliverable).
So my question is, am I shit or is it unreasonable for a company to ask do so much coding or a little bit of both?
What's your experience usually when looking for a job in 'hip' and 'cool' startups?4 -
As part of a technical test, I've been asked to test and report bugs in the production application of the company. Is that normal? Or are they making me do free work for them?.
So far I've only seen challenges like this to be done on a custom application for test.7 -
Devs from company that develop/modify a service for us say "you can test on <env>".
Description of how to test: scattered across multiple tickets, comments and slack messages in multiple conversations...
Oh and please... Could you not directly merge 20+ branches directly to the dev branch without testing...
So much going wrong with this project... Already a month overdue on the first release... -
Dealing with government bureaucracy today. Prepare for pure anger.
First of all, what fucking dipshit site does testing and maintenance in production without letting users know? Bitch I'm getting an invalid date error when I use your own stupid date selector and I had to waste the office lady's time asking about it because you couldn't be arsed to either test your shit properly or actually take it down if it's broken. Who made that stupid ass decision and why the fuck did nobody question it. Fuck you.3 -
How does it look honestly?
>roots android
>makes it home test server
>works on self project for 3 weeks
>finds devrant
>can finally get real feedback without getting asked "what am I looking at"
😀🔫
7 -
!rant,
Belonging to the last 3 of the intake procedure, tomorrow a final test and then im a php dev maybe WOHOO -
!rank
Hi fellow devs and sysadmin's I'm currently working on building a portfolio of applications I build and servers I have setup as I'm planning on working freelance I'm already MTA certified and if I had the money also N3 certified if anyone needs a server setup or something like that feel free to contact me on my website https://haazen.xyz.
Feel free to ask me anything to test me or to send me fun assignments to test me or let me learn new things to as I love learning more.3 -
Why is my test not failing? The actual and the expected json is completely different? What the fuck!?!
It says:
static::assertJson($expected, $actual);
right there.
Oh wait.
Nevermind.
`static::assertJson` only checks for any VALID json string that I always provided in with my own expectation m)
Use `assertJsonStringEqualsJsonString` instead.
What.
Who needs meaningful defaults.
(I would claim that `assertJson` should be defaulft for string equalness, and assertValidJson should be for any Json validation. But you are free to disagree.)4 -
That kind of devs that creat unit test for a method never used in code instead of deleting it. #CoverageGoals
-
I posted two of my projects a few days ago to producthunt one did very well and what came out of it is i got offered a fulltime job in my town.
That will be my first job if i pass their test im doing tomorrow and Im scared beyond shittless. Not from test but from the whole experience. All of it happened too fast. Im starting to doubt myself now. And once again scared shittless. Fuck you brain!2 -
We had a bug with our Karma test (JavaScript unit tests). The headless Chromium crashed after test 272 or 273, every time since a week. I fixed it, but I even don’t now, we Chromium crashed 🤷🏼♂️
-
Scenario: Enabling yet another python test suite on vscode. No big deal.
I start the test init and discovery. Says it cant find the test files. Okay; usually the issue is there's no __init__.py in the test directory. It's okay we can fix that.
Oh wait it's still not working. Okay well this isnt good... After about an hour of searching, i finally find out that the file that vscode is discovering tests with doesnt exist... In fact the whole testing directory doesnt exist!
Okay so now what do i do... Reinstall? Doesnt work. Reinstall and delete the extension directory? Yes! Victory!
Dont know how i got a half-baked extension download but hey... Could've beem worse. -
If you were given an aptitude test for a job and they put you on a laptop with an wifi connection, would you use the internet to solve any questions you struggled with? I mean is it cheating or is it just using your initiative?2
-
Local company has an API service that I'm interested in playing with. Most services would just have you sign up or just read the open api docs. But not this one. Wants me to jump through hoops because its part of their "KYC" policy. I just want to test something before I think of using it for real and they can't provide any test accounts/environment for that. Oh well, at least, I can document my rough experience and perhaps guide others to do and use (or not use) it.
-
My partner was notified that he didn't make it past the coding test during a job interview process. He was thrown off in the beginning of the assignment by lack of instructions, but besides that I know he is a skilled developer. He hasn't asked them what exactly he lacked but I'm curious now. What's expected of the interviewee in a coding test?
This makes me feel threatened for the interview processes I'll need to go through soon myself.5 -
Sometimes I deploy to production without actually testing the changes. At least I have my unit tests!
-
Fuck testcomplete, fuck having to spend 40 minutes mapping out every element just to still hang 5 minutes every time you try to check the existence of one, fuck having a software who's sole purpose is to automate testing and save time take hours upon hours to do what a person can do in seconds, and fuck me for having to use this piece of shit to test every single change made to our site.
-
So I took this ocd sensitivity test 😂😂 . Apparently, I'm a perfectionist & need to take it easy lol.
Here's the link to play :
http://playbuzz.com/monicawoods10/...
8 -
It's past midnight here and I'm studying for my first Calc 1 proctored test (derivative rules). I'm taking the class online and this is the 2nd test overall. The test is in 8 hours...2
-
TL;DR: Embedded software guy needs to create a multi-instance sandbox environment in Jenkins for testing and not sure what good solutions are out there. Looking for suggestions.
So at work, we have these really cool integration tests that validate our system for flight safety. What's not so cool is that due to factors outside of my control, each test has to be run serially and the entire test suite can take many many hours. This is mostly due to a hardware limitation (not enough physical NICs), but there are other SW factors as well.
What I would like to do is somehow be able to wrap up all the resources into a neat little package and then deploy that package into some kind of virtual environment that can be instantiated on a Jenkins job. The NIC issue would be replaced with a virtual one and *theoretically* I should be able to spawn as many instances of this virtual environment as my CPU and RAM can handle. In short, I want to pseudo parallelize our test suite and drive down our testing time. Somehow I would need to be able to control this entire thing from a script of some sort.
Does anyone know of something out there that would satisfy these kinds of requirements? Double internet points if it's open source. -
Got a job test today and I’m already almost done.
All that’s left are two features and I don’t know how to do them and I just wanna cry and all my momentum has gone to waste4 -
Got a technical test coming up for a job. Had never been asked to do one before so I don't know what to expect 😅
(test at home and no time limit by the way so that's less pressure I guess) -
I want to learn, How to add test cases in android And also about layer code pattern. like Controller, View, model, persistence, network etc...
So Please suggest a few tutorial or blogs that help me.
And please give me some links that have a test for network functions and intent related test.
Something like the test for other methods that work of different thread. (Asynk task, Volley or etc..).3 -
Ah, strong motivation: get to 80% (or so) test coverage before my Goland trial expires today or tomorrow.
-
!rant
Does ayone knows of a
+ Good
+ Open Source
+ Free
Data test generator tool?
I'm on my first work with a development that will go to production, and I'd like to test performance, UI and all of that with random generated data. I know about dbSchema but it's trial pulls me back -
So we're supposed to test even the most imporbable edge cases to make sure that our software is reliable. But there is a limit. We let a marketing intern go bug hunting. We use the same component in two tabs of our SPA, but we distinguish them through some parameters. The intern found that if you switch back and forth between those two tabs super fast a couple of times, the program for some reason confuses those two tabs and swaps them. Now management has listed it as a priority. When are the customers _ever_ going to do that?!4
-
PHP test
Only one exercise I failed so meh.
In all case : next week we get back to JS and that's my jam -
When you do some group programming and let yourself get led wasting an entire day into writing 6 out of ~12 tedious higher level unit tests with lots of data setup and jerry rigging, that turn out to not even test the code changes you made on a ticket that another team is depending on.
But thank you to your tech lead for helping rope you out of that stupid shit with knowledge and clout.
Unfortunately the ticket has your name on it and everybody except the goon squad probably thinks you're a retard for going down that adventure (which was not your idea or desire).
I need to learn how to articulate no this isn't worth it, the complicated monolith software architecture with many different moving parts, among many other things. -
2 weeks+ ago I made a PR into our codebase containing sample refactor that streamlined a significant portion of code. Also, I did refactor only on two handler packages (for MVC folks, that's Controller) as proof of concept, to figure out how convinient / logical the part would be for everyone.
We have rule of 2 approvals for merge (for 5 team members)
While writing refactor, it obviously blown up a lot of unit tests, but still coverage was fairly poor (that stuff was rushed, there was back than no time for unit tests). After my refactor I spent couple of days writing tests that hit fairly sweet (comparatively) coverage. (I managed to bump coverage from low 20s to high 80s, and have less code for tests)
I got first approve pretty much immidietely, other team member was on vacations, and 2 of them forgot.
We generally try to close PRs fairly quickly (usually same day kind of deal), but that one was just.. hanging in there. So I pinged everyone to re-check it to greenlight it but of course, loo and behold, merge conflicts arised. I ended up fixing actual logic (just some method signatures changed, not a big deal) and ran the units.
So, one of that handlers got quite a few of edits, and guess who is pretty much rewriting unit tests for second time now...
Dude, sometimes I question why tf I even bother with these tests... Feels like sabotaging my productivity, especially with bullshit like that4 -
A young new dev was working on his first ticket, about a bug during parsing of an uploaded excel file. Our issue was that if the file contained an empty line, all remaining rows were ignored. So the task included extending our tests to cover this case. After 2 weeks (!), his merge request comes in. His idea (without ever asking for help) was to parse the whole file (in some cases huge) in the production code a second time, just to count the rows (!!) and save the count in a public static int field, which was verified in his new test.2
-
I am integrating with different third-party payment provider via their API. Just wondering what is the good approach of testing these third party service/API?
Consumer/Producer contract testing?
end-to-end test?1 -
When the vendor did a search page but retrieve all the records from the database and paginate them with js, and the load test crashes with 20 concurrent users!!!
-
!rant
I would like to pick up some Test Driven Development practices. So that the most people benefit: "What book/material would you suggest for each language?"
So that I also benefit: I was hoping to find some books on C#, but some of the reviews gave me doubts. -
Is unit test helpful in React web app? Why do I think it is just wasting of time? How often do you use unit test in your web app development?12
-
Stop screen on a widget test
I have a screen which contains a button,
Pressing the button will
1. call a function showloader() to show progress indicator,
2. then awaits to perform some logic.
3. Then calls function hideLoader() to hide the progress indicator.
My question is how do I perform widget test on loader, the problem is when I do tester.pump() it gives timer error and when I do tester.pumpAndSettle() it will go ahead and call hideLoader() and the indicator gets lost and finder cannot find any widget and test fails?
Is there any way of stopping a screen on execution, so that finder can find a widget?1 -
That feeling you get when starting a new scala project. Fresh start! Lessons I have learned:
1) Add a linting tool before the code gets inconsistent to the point where it has thousands of style errors.
2) use test driven development from the start so that refactoring later is a breeze.
3) Write top down, no matter how much I want to implement the algorithms first.
4) write the tests first!
Top Tags
Weekly Rant
View