Friend: "What is devRant?"
Me: "A place where programmers tell jokes and complain."
Friend: "Why dont you just do that irl?"
Me: "Because we never test in production"

teacher gives a question in a test : can you save a word document as a pdf.

me :Yes

teacher :that is wrong

me : shows her how to do it..

teacher : "oh well "

Do you follow test driven development?

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.

Not a coding test, but:

Them: So you are interviewing for a programmer opening. Do you like programming?

Me: yes.

Them: do you make logos?

Me: ...I can...?

Them: good because you won't always be writing code here.

Me: I'm out.

Currently acing an interview, had to do a typing test, got 67wpm and 98% accuracy.

"If you want faster I'd have to bring my own keyboard, this one's a little small"

"You can go faster?"

In case anyone was wondering if Apple ever actually tests updates during review, they do. Sometimes, apparently, they also use devRant with the provided test account. Hopefully their rant/comment quality improves, but they are trying!!

Travelled 4 hours to an interview to do a JavaScript paper test with questions copied from W3C academy👌

Jingle bells,
Batman smells,
Don't push to prod today!

But if you do,
Make sure you
Test it all the way!

Happy holidays, y'all!

Lead engineer: "Well, uh... I haven't really prepared a test for you but the HR insists that I should test you before wrapping up this interview.. so uh.... what do you suggest we should do now?"

Me: "Um... how about we walk through my latest project code and you can ask me to optimize it?"

Lead engineer: "Sounds cool, allright let's do that. How much time do you need?"

Welp. Did I just pick my own interview question?

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

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

*acceptance test written and sent to peer review*

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

I highly doubt that Apple does TDD.

College placements, one of the leading tech companies comes to hire people on day 1, I miss the first round coz I overslept, woke up and realized the test started an hour ago, finally went in after the test was done. They still let me take the coding test but with reduced time, and kept talking to themselves that if this guy gets through, I'm fucking done with placements. Managed to do well in the test and then proceeded to the interviews, aced the interviews and was offered a job. People at work still call me "that guy who turned up late and still got the job"

Passed the online test.
Passed the technical interview.
Need to pass the final interview.

I'm applying to this company as a JS developer (backend). Their engineers are amazing and the fucking have 99.94% coverage on their test suiteeee; that gave me a code-boner.

If I get this job I'll finally say good bye to fucking PHPShit and Zend Framefuck and all this hacked bootstrap and 15k LoC "core.css/js"

I CAN DO IT

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

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

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

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

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

🙏🏼

"Your resumé looks really good. We would really like to hire you. But you need to do this completly job unrelated test/coding challenge first."

----

"Is the test Android related?"
"Yes"
*Opens Test* -> "what ist the complexity of this function (written in c)"
*Scrolls*
"Implement algorithm xyz in Go lang"
*Closes test and breaks something*

----

"You will need to Code on a small Android projekt so we can see how you work"

"OK, how much time will i need to plan for it?"

"Our lead dev decided to make it small so its only 4-5 days."

----

What is it with all this stupid hiring test these days? And what do these recruiter think?

- Did someone tested it on our test machines?
- No there was no time to do this.
*preparing for nuclear fallout from customer in 3..2..1..*

Indian web dev company (during the interview)::
We follow standards

Me:: Hey, can I get the project's github link so that I can fork it, do my tasks, run test cases, push and, make pull request that you can review, run integration test, and finally merge.

Indian web dev company:: What?? Here's the ftp credentials.

Me::

I jump on an existing scala project.

git pull && sbt compile test

Tests are failing.

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

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

Me: "Did you run them locally?"

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

I check Jenkins.

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

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

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

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

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

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

Gnarf!

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

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

*Le Me writing some functional test*

Friends : How do you test your test ?

💣💣💣💣💣💣💣💣💣💣💣💣💣

Best fuck QA ticket. "Images are not loading good." No page. No more info.

What am I suppose to do? Test the whole fucking site.

Guy: - Why the hell do you keep adding new tests with "TDD" in the commit log? Is this because you're wearing this stupid TDD t-shirt!? You're only supposed to maintain this! There's nothing to develop! Nothing here will ever be test-driven!

Cprn: (turns around)

T-shirt: *Technical Debt Development*

Tl;Dr: Client-side validated online test

Some stupid questions in an online test.
Not all of them were coding questions, but all (yes ALL) were client-side validated and to solve the tasks all I had to do was to copy one array into another and set the time I needed for that task to a legit number.

Well at least it was an online test that doesn't required 3hours.

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

Teacher gave us the wrong specs for a project we had to do on 3 years, learned it 4 weeks before the final test ...

Do you guys know any Github repos with really Bad C++ code?

Just wanna see if I can understand it, as a test... 🤔

Mom: what is it you do exactly?

Me: I make web sites and test computers for bugs.

Mom: What is a bug?

Me: it is when a program does something you do not want it to do.

Mom: k, I don't understand how money is made in that. But, you know (random store) is hiring.

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

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

😥

I was with the train in Vienna already when suddenly I received an email that the test can't be held today because of technical problems 🙄

Now we have it next week when I also have to study for a maths test, do statistics exercises and exercises for database systems
Fml

boss: we should map all the possible ways to do things in the system so we can test them and make sure we fix the bugs.

Me: yeah, well, that is exactly what automated tests are for, every time we find a non-mapped way that breaks this we make a test out of it and fix, this ways we end up mapping the majority of ways.

Boss: yeah,yeah ... Let's sit down latter and map everything on a document.

I bet my ass we are never gonna have tests as a part of our workflow.

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

Image : TL; but do dear.

Had human values and professional ethics test today.
This was a question.
Would like to hear the views of some professionals in here.

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

About to do my first certification... Its an online test and I am nervous as fuck...

Wish me luck!!!

What do you need a boss if you can find the idea, analyze it, design the product, code it, test it, setup the cloud and even do the marketing.

Dear bosses,

I am a developer not a God!

6pm: will do one final test then commit
.
.
.
11:45pm: fixed 10 bugs...time for cofee

😭😭😭

My first new year resolution for this 2017 is learn to do the f****ng unit test before implement the code

A discussion about writing tests for frontend applications.

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

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

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

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

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

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

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

If body { background: red; } isn’t the first thing you do to test a CSS file is included, then I don’t know what kind of developer you are.

Test server not working as expected - check with test team.
Test team experiencing the same problem - report to dev.
Dev team says the issue is not on their side - check with the service owners.
Service owner says it might be a problem with the request and gives me another point of contact - send an email with all the info.
POC says it doesn't have anything to do with him and copies "the right person".
Next person says to ask a different team.

Get reprimanded for asking too many teams.

Jeez idk, maybe if you stopped passing on the blame like a hot potato and actually helped me out I wouldn't need to.

The most frustrating situation
when you do competitive coding...
2/50 test cases failed . tried all possible .. and still not done !!
its like "operation success patient dead" .....

My blood test report came. Both vitamin b12 and vitamin d3 alarmingly low!
How do you keep your health working from 9-6 as a programmer?

I got hired to run an A/B test between a competitor landing page and a new page. While I didn’t do the new page initial design, I did advise on and completed its final tweaks. The result was a 430% increase in leads generated over the original.

So this just happened...don't test on production kids (....sometimes you have no choice BUT DON'T F**KING DO IT OK!?)

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

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

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

For myself, I choked on the following:

- "Why do you want to work for us?"
- "Why us, specifically?"
- That stupid logic test with the guys wearing the red and white caps
- "Convince us how you're not overqualified. We're simple people."
- "Convince us how you're not going to leave us in the long run."
- Stupid db test: here is a scenario. You have 15 minutes to write an entire relational db with 20 tables, keys, relationships..
- "Why would we want to hire you?"

Why the hell do you keep commit+push your shit to the master branch! We have develop, feature and hotfix, you *************!

Just because you want to test something in prd environment, you don't mess with the master to build the production image. And you do not even rebase fucking develop branch and keep it out of sync you POS!

Excuse my language, thank you.

*Writes code, doesn’t test* “Ah this works, I’ve done it before”

*Finishes project, runs test, errors everywhere* “FUCK!”

I do it on non-important projects... but I need to stop before I start doing it on important projects 😑

I just want to share this:

When I start working at my last job, I have little idea of what a unit test was.

My boss on one meeting said that unit testing will be mandatory (wich is ok and umderstandable).

Almost a *year* after that, no one still care about them. I see myself doing them the best I can, but I saw things like wrap the assertion line with "try / catch" to lie to the coverage and unit test percentage. Or in other cases directly uploading *manually* the code on the server without test at all.

And then, as the only developer who do the unit test ok I have to do the missing ones and repair the fake ones.

Then when something explodes the question all the managers love to ask "Did we had the testing?"

At least I quit... that job was some crazy shit, this is just one story of many.

Like that other time that my co-workers did not understand why I needed to do POJOs on an android app because the big bad JSON that the app used was working fine....

Me, programmer(not employed yet): you know what is crazy about coding test? I can easily do manually what test said, but teaching it to computer is surprisingly hard.

My brother, teacher(not graduated yet): I can easily solve middle school problems too, but teaching to kids is hard part. It seems like we do similar thing.

Unbelievably slow connection. Wanted to do speed test so I can post with proof. The connection disconnected the moment I click the "Test speed" button.

Public test of an assignment I had to do

What the hell is with startup CTOs thinking dev applicants are willing to do an "8 to 10 hour" take home coding test before even a first in person interview?! Seriously?

online coding exams.

Ask me how to do a rest api, ask me how to do a certain visual in the website, ask me how to setup a docker service running grafana, please just ask me something about the actual job.

Dont ask me to create some mind game that was ambiguously phrased in a timed hackerrank question that expects me to write runnable solutions that pass all test cases.

I have way too much work to play around with hackerrank for weeks so i prepare for your useless test

we need you to do migrations in a legacy codebase which includes changes against a tool you will not have access to test against

Was writing a functional test in AdonisJS that queries an API endpoint with data and my test stays red with a dainty `expected 500 to equal 200` assertion failure.

In frustration, I yelled "What must I fuchen do to get my 500 to become a 200". Then my dev friend, an absolute fuchen genius tells me, "Subtract 300." I hope the prat stays debugging his code for a week!!

I created some test entities specifically for our staging site. Written in all capitalized letters in the BIG TITLE of the entity I included DO NOT DELETE. This is very clearly visible in the CMS. What's the first thing the content managers do?

You guessed it.

I guess if plain English doesn't work, I'll have to use Kindergarten rules and put a custom lock on them so they can never be deleted.

Muad'Dib fullstackchris can already predict the future, in a few weeks: "hey!!!! fullstackchris, I can't delete these test entities!!!!! whats wrong with the system?!?!"

sigh...

When you want to do a few test deploys (project going into alpha today) and your Internet is too slow to even login to the server 😭

I made some substantial changes to the codebase.
I run all the unit tests, as usual.
A test that has nothing to do with the feature I'm working on breaks.
"Huh that's odd, let me debug that"
I set a breakpoint with the condition set so that it pauses before the test assertion goes red.

I start the debugger and.... all tests pass

Turns out it only happens like 500/10000 times....

This will be fun

Do you know that KDE is more lighter than MATE? In the screenshot the RAM usage you can see is from a live. The same test on the same PC with MATE take 900 MB and with GNOME 1,5 GB. Test made with the latest LTS of Ubuntu.

Unit tests that do not test anything, even no assertions at all in some of them.

Remember to always setup and test your production setup!

Seem like a local college forgot to do some QA 😂

I didn’t turn down a dev freelance project when the client decided against going with best practices because the solution I offered was a well-established design pattern but created a need for a financial management change she didn’t like. I stupidly built what she asked for. It worked fine in the 3rd party vendor test environment but failed on production. After hours of analysis of code to ensure no changes happened to my source during test->prod deployment, and the vendor denying they had config differences between them, and the client refusing to pay, all I could do was abandon the project.

I would make unintelligent customers disappear.

Reason:
What did I do today, one may ask? Spent the entire day debugging code and creating test cases to fix a high priority trouble ticket submitted by the PM of a program.....where nothing was wrong to begin with.
User error makes the world sad.

We have started working on a new web based editor software. It already has 132 unit test after 3 months but can‘t do shit. In has no functionality, yet.^^

Today marks literally the 4th time a recruiter has put me through to a technical test for a language/ framework i do not know. Even if you are tech illiterate just fucking ctrl f my cv to see if I know it. Absolute waste of time.

This guy looks very promising and has experience, let's let him make a test site...
WHAT DO YOU MEAN 4 JQUERY SCRIPTS IN THE SAME PAGE?

btw the versions are, in order of appearance:
3.5.1
2.1.3
1.11.2 (!!!)
And the last one within the body: 3.6.0

Such a professional.

Just let people who already know the things you are teaching miss the class entirely. Give them some test at the end, this is okay but do not force them to suffer the endless hours of something they are already good at just because you want them to attend.

I abhor timed code tests. Do you really want to test how fast I can write crappy code?

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

Let's get real serious for a second here guys... How do you unit test a unit testing framework?

Listened for about a half-hour yesterday to DevA ‘beat down’ DevB writing a console app for trying out a proof-of-concept idea he had.

DevB: “What’s the URL of the development server?”
DevA: “Why? What are you doing?”
DevB: “I’m needing to throw some messages to it so I can capture data for something I’m working on.”
DevA: “How are you calling the service?”
DevB: “I wrote a console app”
- you could almost hear the eye roll -
DevA: “A console app? Why in the world would you write a console app?”
DevB: “Oh..um..no reason. I just need log some test data for something I’m playing around with. How should I do it?”
DevA: “If it’s test data, you should have wrote a unit test. You see, unit tests …”
- yammer on and on for about 5 minutes about the virtues of unit tests…never really explaining anything -
DevB: “Yea, I’m not needing to test the result or anything. I just need to log some data.”
DevA: “Then you should use a unit test for that, not a console app. With a unit test, you’ll be able to validate the data. That’s what unit tests are for. Microsoft should have never put in console apps in Visual Studio. It just leads to bad coding practices.”
DevB: “Um…I don’t care. It’s a console app because I just need data…thanks anyway”

Today, DevC was talking to DevA

DevC: “Charlie is testing the order module, but there isn’t any test data. Do you still have the data generating script?”
DevA: “Oh yea, I’ll send him my console app that populates the database.”

It was all I could do from screaming “You stupid –bleep-er!! What the f–bleep-ck was all that yesterday?!”, but none of my business. Better to devrant about it than start a fight.

Opening up IE11 to test HTML in local development.
Entering local IP to URL bar and IE decides to look for that IP address in Bing... 🤬🔫
No that's not how you do it IE.

If only they allow us to write unit test at work, its not that It is forbidden but we are not given time to do so :\

Done my test on my side project and now I can happily move to the next step.

Though I'd be happy if someone answers this:
1. When I have to execute functions by order, do I write all their code in one single function and divide them into regions (speaking of C# #reagion)

OR

2. I keep them split and implement the order attribute for XUnit?

My test case is basically just to make sure CRUD methods inside my repositories are working as expected, noting complex

My boss: Write unit tests for this angular app
Also my boss: what do you mean it will take months to write the necessary mocks for our 177 specs
Also also my boss: why would you need to mock anything for a unit test
Also also also my boss: Just let each component import all the other real components, nevermind that that's an integration test and not a unit test

I was shortlisted for a job opening and they sent me a link to a coderbyte test on friday that is only valid till sunday.

Isnt making your applicant do a test on a weekend such a dick move?

The panic when I overhear my colleague in a meeting "sure I can test it in prod but we normally don't do that..."

Question: What do you mean that you have a bachelor in computer science from college? What do you mean college?
Answer by me: Are you fucking stupid or something???? Give a fucking code test and I will saw you what college means... Little piece of shit!!!! And next time when you are searching for PHP developer do not ask for site development with WordPress experience you fucking noob!!!!

How far off can you implement a feature?

Task: Update add one feature to this endpoint and add test(s) for the new feature

What happened
* Correct endpoint
* Add 2 wrong features
* Remove one important feature
* Do not the requested feature
* Write a test that doesn't actually test the feature for the wrong endpoint

Intern be like: looks fine to me. Pls review and merge

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

Ah good ol' refactoring summer.

*Me starts refactoring spaghetti bolognese*

- Hurrah everything can be generic and so much better. I'll just do this and this and this and this, oh and this also needs to be reworked cuz of this.

8 hours later.

- it wasn't that bad!

$ git status

- oh god

$ dotnet test

- welp.... I need something to do tomorrow.

It’s the second maths pre-final exam today. Next after that - the finals.

I feel more ready than usual, I practiced more than I usually do before this test.

Wish me luck!

Ever have a bug that *only* occurs in your production environment? How do you test potential fixes? 😜

I hate those morons who do QA by simply clicking around. You are a disgrace to people like me who like to code and still enjoy doing testing.
Get a life you fuckers. You are the sole reason why many people in industry thinks that QA is something anybody can do.

Yes, I agree you can test the application, but in no way you could ensure the quality of the product.

What browsers do front end devs here normally test on? I test on Firefox and Chrome because...that's all I use, but what about Edge/Safari or god forbid IE11?

I'm more familiar with backend dev ops so my testing consisted of checking Firefox a lot. :P

I built an expert system (what we used to think of as AI back then) that could read the circuit diagram of a complex electronic circuit, figure out what it was meant to do, and set up the test gear to test it and diagnose manufacturing errors.
In 1985, using Vax/VMS and OPS5.

More recently, I was on a project (can't claim to have done it all myself this time) that used a neural network to detect patients in a care home that fell over/fell out of bed and alert the nurses' station.

At my job we have these days where we have to BUG-BASH, meaning we do any stupid thing on the software to test it and find bugs.

I hate it.

I didn't sign to be a QA.

Due to coronovirus, my work asked everyone to login for 30mins (in a 2hr window) to test test max load/capacity...

1. how do you test max load if people can login at different times...

2. Isn't there software that can test that.... Isn't this load testing?

I don't always test, but when I do I test in prod!

So I wrote an algo in python3 for a challenge in codechef.com but it raised this exception !
If I put the input() built-in method in a try/catch , how do i know what the input was in order to pass the test case?

we had that one teacher in the apprenticeship in the first year who taught us C. There were some people who already knew the language but most of us didn't and we had this one horrible test where we had to do some for and while loops with stars... Like generating something like this:
********
*******
******
*****
****
***
**
*
so most of rhat stuff we never learnt and he couldn't explain to us why our code wasn't correct and we all ended up getting really bad grades in that subject for something really basic -_- just because he couldn't explain it to us and test things we never had

the CEO is trying to release a product that has had a total of 1 test user, himself!! 🤦‍♂️🤦‍♂️🤦‍♂️

Any ideas to convince him to do something like a slow launch instead of sinking a bunch of money on marketing!?!?
(I'm pretty sure dilbert or xkcd should have something related...)

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

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

Want to test your how noisy your PC can be?

Run Computta, Android Studio, Node.js (ionic/Cordova) simultaneously.

My Dell PC always sound like a tractor when I do this.

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

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

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

*Filling out unit test plan for tester which is an Excel Document*
*Excel keeps trying to correct capitalization on a word that I want capitalized over and over*

LISTEN YOU PIECE OF SHIT! If I didn't want to capitalize that word I wouldn't have capitalized it! Just do what I tell you to do! YOU ARE A PIECE OF SOFTWARE! YOU DON'T TELL ME WHAT TO DO!

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

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

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

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

Which moron at Google decided that a transparent status bar is useful and that the user should not be able to change it?
Do they test only with unicolored apps?

Which method do you guys prefer?
$("#test") or $('#test')

Me after Linux reinstall: "this is great, now let's get back to work. Let's install the packages, then let's run the test server. What do you mean postgres can't be found? Wait... Fuck. Fuck. Fuck." When you realise that you forgot to backup the test database 😂

When one of your tests breaks, do you rewrite the test, or the code?

Usually I rewrote the test.

A friend of mine is youtuber and he does a lot tests on phone ( call him X)
Another friend of mine hates Apple product. Partly because he can’t afford it (call him Y)

whenever X wants to do a WATER RESISTANCE TEST, Y would go: “Lets fuck Iphone”
whenever X wants to do a HEAT RESISTANCE TEST, Y would go: “Lets fuck Iphone”
whenever X wants to do a DROP TEST, Y would go: “Lets fuck Iphone”

One fine day, same happened and X got a bit red. X says: Y come here. Closer, a little more ( few centimeters away now). “Are you fucking mad or what?”

Best parte do being a dev?

Fix bugs in production! Because life is to short to test in UAT

Why the fuck do we have THIRTEEN environments dedicated to dev and test, all for the same items?

they say do TDD

but its often that my test is wrong while my implementation is correct lol.

Why do front end developers like to write their HTML/Component markup like this:

<div
id="test"
class="test"
>
Test
</div>

That lone > bracket absolutely irks me! Looks ugly! I prefer the Android style:

<div
id="test"
class="test">

<span>Test</span>
</div>

👌clean

Looking at an old Java project, running java 1.6, test folder doesn't even exist and the "old but gold" java.utils.Date class is used throughout the whole thing. How do I initialise a new date again...? I actually just googled that :D At least the constructor parameters are named nicely... wait.. what...

Assertequals("Fail","Fail") in the catch block.
Things developers do to bloat their test coverage at my organisation,
I am #stuckWithIdiots

Management sees green

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

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

Wanted to do a "quick" software update on a test device for our colleagues who test the system

Here I am looking up what led indicators blinking correlates to what hardware error

Embedded development <3

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 Korea

An iterative process of "plan, do, test, improve" shouldn't leave an engineer's head. If we outsource "plan" to a manager, "test" to another blabbering idiot with a corporately purchased donut hanging off his mouth, the cycle becomes too long to actually work. Multiplied by an engineer's despair because he's obviously clever enough to see the whole picture, this is a recipe for disaster.

Throwing man-hours in there won't solve anything.

Do you test your codes while coding or after completion?

I test while coding.
PS:- I'm web developer.

Our company fails the Joel test so badly, most strongly on the question 'Do you use the best tools money can buy?'

I've got the best laptop in the company, which is why I'm not allowed to complain (even though I do, see image), but some of my co-workers have dreadfully slow machines. I pity them so much, especially whenever I sit next to them to do some pair programming e.g.

I just migrated Test data into Production. If I start a new project, Murphy's law indicates that my phone will ring, and the migration will have been a total loss.

If I sit and do nothing, Murphy's corollary tells me the data migration will be a success?

When an interviewer asks, what are the steps that you take usually when given a task to do something, what do you guys say?

I said, I devote 10-20% of the time to understand the given problem - sit and explore all possible scenarios to handle, then develop a brute Force approach, improve the approach to make it more efficient, see if it handles all edge and corner cases, then write test cases for it.

( I'm thinking, the process doesn't vary a lot for most of the people?, Except in TDD - one'll write the test cases first)

How would you answer this question?

I have this feeling that I messed up something 🤔

"I don't think we should be playing with our privates {variables} like that" - framework designer

= context =
It was noticed that we have too many setter functions to change private variables just to do unit tests. So we had a small meeting to discuss what to do about this.
Options:
- don't do the test
- ignore till another time (ie: keep the functions till its a problem)
- put the variables into a provider
- use reflection (the above quote was a reaction to this option)

I'm sick of a toxic soup of ways to test frontend.

Throw in vitest, jest,jsdom, testing library, @testing-library/jest-dom, together and you are left with n^2 ways things can be configured.

Why on earth do I need to import anything to do with Jest when I am working with a vitest project.

I think such tools are made to get invite opportunities to speak at conferences.

Do you have those little success moments while coding? Like the feeling of avoiding a new bug because of a test failing 😍

I thought I had seen everything, but today a coworker tried to call one test case from another and asked me if that is an okay thing to do.

We are recruiting a front-end developer for 90k/year.
He refused to implement a simple ordering on our test, telling us “There are libraries to do that”. Apparently, TypeScript is not front-end.
Kindoff questioning our decision now.

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

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

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

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

Users have use cases, test cases, user manual etc documented material with them at the time of UAT.
But in the end users do only those things which they don't suppose to do..!! 😑😥

I'm a strong believer in the triple-A unit-test pattern: Arrange, Act and Assert

Anyone else that uses this for their tests? Do you see any cons to using this approach to writing tests? Are you using an alternative?

If you're reviewing someone's code, do you run/test the code before reviewing the logic? Or do you review logic before running the code?

Did you ever had to integrate a fucking "API" that is done via mail bodies?

Fuck this shit! Who need responses about success or failure?! Guess this will take a long time to test this fucking piece of garbage... We don't get a test system, we need to test this with the production system of the other company. I hope their retarded application crashes when receiving malicious mails.

Not speaking about security, I bet everyone can send a mail to their stupid mail address and modify their data 🙈

And inside of this crap mail you also have to send the name, street and email of their company. Why do you fucking need this information?!

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

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

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

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

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

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

Me: :3

Working on migrating my stuff from DigitalOcean to Contabo. Did a little test drive over the weekend and was very happy with the service. Most of all, I was very happy with the price: paying around a 4th of what I paid to DO to get the same specs ^^

I find dynamically typed language a lot easier to read and understand than statically typed language.

What's up with all these interfaces, types and abstractions, its just too much!

I do want structure when writing code, but also the flexibility to test things without the f*** interface/type errors!!!

We are devs, we do not test, we directly deploy to production...

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

I completed my driving test today. You're gonna want to read this whole thing about how it went.

I have attached a pic which highlights what you have to do in the car, to the pass the test.

And as if that wasn't easy enough already, my driving instructor sat beside me in the practice car where he had his own foot controls, handled it.

I swear I just sat in the driving seat with my foot doing nothing and my hands controlling the steering wheel. The test took a total of 45 seconds to complete.

I'm a little weirded out ngl.

Friday afternoon 5:00pm: everything works wonderfully fine, let's go home!!
Monday morning 9:30am: Let's do some more test on the latest code I have wr.... KABOOOOM!!!

!Rant

I will have you know that being part of the mobile solutions team is pretty sweet when you have nothing to do but keep a few databases clean and up to date, test which iPad is best suited for the sales people and buy 20 cases to test them for sturdiness.
Seriously without dumb idiots arguing about roaming costs and demanding help with the most basic shit this would be heaven.
I mean it's apple but still having every color of the 9.7 iPad and of the 12,9 pro stacked up on your desk is pretty cool.

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?

CATCH2 PLEASE DO YOU FUCKING WORK.

I HAD TO REWRITE MY FUCKING THING TWO TIMES BECAUSE YOU FUCKING RUN MY TEST CASES WEIRDLY THUS MAKING MY THINGY NOT WORK

Video conferencing apps:

Competition is great. It just sucks when you have to use all the competition.

Things I want to be able to do:

- Test Mic and Audio before joining the call, BOTH DAMN IT (some do do this, some just one or the other).

- No fiddling in settings to do test / change settings. I want to know / test every damn time before I join ...

- and it would be great if it forced everyone to test too ;) (obviously some complications there if folks are joining and don't intend to talk)

Things I to see all the time on the app, don't hide this shit, and GOD DAMN IT DON'T AUTO HIDE IT:

- Is my mic muted or not.
- Is my mic broadcasting sound or not.

I've been lucky enough to not have any terrible dork ups using these apps but man they seem to invite it by hiding stuff.

What tools/pluggins do you recommend for:

VSCode
Data management.
Test code
Organization and collaboration
APIs
Debugging

And other tools you like to use the most? ✌🏻☺️

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

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

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

Sometimes I think my boss is against coding :/

What the fuck is a "pre test"? And why the fuck do you call it if there are no other tests after it? Get your shit together pm!!!!

Going back to a project from a few months ago, a fellow dev has committed 'test this' comments with my name...
Hitting up git blame shows my tests were written 2 weeks before! If you're gonna be passive aggressive, at least do it right :/

Deciding to make the website I'm working on a one pager with calls to API.

Why did I decide to make such an extensive API. 😅

API functionality includes:
user endpoint:
- log in/out
admin endpoint:
- edit user
- create/delete user
- create (sub)menu categories
- create items (install/test/image)
image endpoint:
- create image (of machines in array)
- restore image (of machines in array)
install endpoint
- install machines (Windows/Linux)
test endpoint
- auto-test (array of machines)
- test (array of machines, test)

Then the machine endpoint:
- if action in table then do action

So to test my server code that do calculations on large numbers that get above 10 digits 90% of the time.

The end users found a custom web page with basic javascript doing the calculations.

Now I get to explain why that doesn't work.

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

The one place I get to have fun with my code is the tests. Who the fuck cares if I use the test string "Mr. Snuffleupagus"? Please stop ruinning the little fun I do have by changing my tests in the very next commit.

Trying to convince the class that test-driven development + DTSTTMPW ("do the simplest thing that might possibly work") + pair programming is the way to go, our software dev prof had us split in groups of two that would each get a turn to
1. add a unit test
2. edit the code so it passes the test
3. commit the change

The goal was to write a java class that converts integers to roman numerals.
Each group had only 2 minutes before the prof made them revert their changes.
After 45 minutes the code was just 10 lines of this:
if ( n == 1 )
return "I";
else if ( n == 2 )
return "II";
else if ( n == 3 ) ...

Do any of you guys know an android app which sets a "fake" location and goes along a path (and does not contain ads if possible)? Currently have a GPS based project I need to test

Thanks bros

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

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

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

Unclear feedback.

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

When applying the feedback introduces a bug.

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

Unactionable feedback.

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

"Verify this works"
Duh..

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

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

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

I rewrote the system. Please review it.

No need to review, just approve.

I will change this as part of the next ticket.

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

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

No need to test this.

There's no point to test this.

I'll test this on production.

Not sure why this is working..

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

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

Ignore this.

This will be meaningful in my next change.

I see that many junior level programmers are being given fairly large take home programming test/projects. I think that if you interview someone and check out their git hub or discuss some code together you should not need to also do a take home test. You don't have good interviewing skills and are making your company look bad. I also think it is an incinerate way to waste a candidates time.

Colleague wrote all his test cases after finishing his code and set expectedOutput to garbage. His tests failed, printing actualOutput. Then he just replaced the garbage expectedOutput with actualOutput. Bingo bango, all tests passed.

"How do you like me now TDD?"

Why do people have to have surnames like "Test" and "Sample"? We even have a contact record for an organisation called "Testing Circle", Circle being the name of one of our service providers, but this other organisation is unrelated and genuine.

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

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

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

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

Seeking a new school to continue studying..
Finally found a good one, with a programming planning, a rare things in programming school...

Ok let's go, here is a challenge to be accepted.
Friends : i bet you to fails the challenge and get accepted.
-me : .... well ok I'll only do the programming part and don't answer the rest of the test.

30% of the test was logic and programming, the rest were stupid culture questions.

- the school actually hired me.. thanks 😂😂😂

I don’t want to write paper/ run test to produce meaningful numbers

Anyone want an image like this?

Just tell point me to the image, a set of text and I will do it for you

Please I’m bored

This is the mandalorian using his lines from season 1

I just reviewed a pull request with a test case like (pseudo code):

# Test MyService

const mock = createMock(myService.myMethod)
.whenCalledWith("foo")
.returns("bar");
assert(mock.myMethod("foo") === "bar"));

Why though? Why are we testing the mock? What is happening here? This test has no reason of being there instead of a fuzzy feeling that we now have unit test to lure us into a false sense of security.

I asked why we don't do an integration test. Response was: "They are slow."

Well, duh, but at least they would actually test something.

What do you gain by asserting that the mock is working the way you set it up?

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

FUCK JEST. ITS ALL SHIT. I CANT HAVE A DIFFERENT MOCK RESULT FOR ONE TEST AND KEEP THE OTHERS THE SAME WITHOUT REWRITING THEM.

THIS IS THE REASON NOBODY REALLY WANTS TO DO TESTS, NOT BECAUSE THEYRE STUPID BUT BECAUSE THE FRAMEWORKS ARE THE PINNACLE OF CANCER THEMSELVES.

One of the founders of my startup does not write tests....

Me: we have to all write tests. I explain unit tests, integration, etc.

Him: I do... I have a test that checks if the app crashes or not.

Me: that is not what I meant (writes test because he won’t) 🙄

Test A succeeds when run solo. Test A fails when run in conjunction with Test B. Obviously, some kind of messy state that isn't isolated per test.

I realize what it is, so I add a new feature to address it.

Test still fails, it had nothing to do with that.

I finally realize what it was. One liner fix.

Yay for a new (useless?) feature that isn't getting backed out.

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.

As a developer, when learning a new language how do you know when your good enough to start making projects to test knowledge or skill?

Weblogic Server won't start, broken build was auto-deployed. How does a broken build even get deployed? 🙄

Told "till the server is fixed work on your next-release bugs". Sure, can investigate, maybe even code fixes, but with a broken dev environment how do we test anything?

" Hmm..Oh yeah, right" 🤔

Working on a selenium test suite for a large web app. Nightly tests currently take 3h to finish. At what point do nightly tests become weekly tests??

How about ' What tech/framework/language do you trust will truly stand the test of time' ? Sorry if someone has already suggested this but I would love to see opinions.

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?

Coding would be fun right now.
But seems like i gitta do a night shift to rock network technology test tomorrow. The most annoying thing about this test is, that we have to calculate ip addresses by hand. Not too hard, but damn.. We are not allowed to write it down in hex, only binary (while calculating). And he wants to see interim steps in our calculations.. Even with IPv4 addresses it will be a great amount of 0s and 1s to write.
I better look for a second pen to take with me..

How do you switch from testing while debugging (functional) to TDD unit tests?

Usually I test while coding by just running the use case and making sure while coding, bad inputs are caught/handled.

But most times I start with a general idea of the structure and what the about should be (which essentially would be the functional test case?)

I don't think about how you can break each part or the functions I need until I need them. Then usually start simple and then refactor. And until I'm sure each time I refactor would require changing the tests?

It's been a while since I first noticed that web development is becoming way too complicated. I'm not sure why people decided to overcomplicate everything. Is it to look smarter?

I just spent a few hours trying to understand why a unit test was failing. I decided to debug every statement of that unit test until I realized what was going on.

This project uses a library called ImmutableJS. I was calling for the "length" property of an array, like a regular human being would do, but that returned undefined because the correct property within this library is "size."

Good Monday, everyone.

After weeks of working on my esolang interpreter in Rust while learning the language at the same time I'm finally at a point where I'm able to do the first test...

Only to realize IntelliJ Rust doesn't support debugging 😴

I hate it when I want to implement a 3rd party API and their docs have no hint at how to create a test account.. Why do they make me call their sales team / bother their support for that?

Send good vibes because I'm going to do a 5-day test for a good job offer

Had my first ever final interview as a developer after passing the first ever coding assignment, now can't stop thinking if I should have answered the questions differently.

I was very honest to my answer when they asked "How do you test your application?" As I started building the app with 0 knowledge about software development and know nothing about software testing. So I just told them the truth that I did not do any proper test, I just used a checklist and manual test to test my app and the app that I created for the assignment was the first app that I write a proper test cases and implement an automated test. The same goes to other questions like automated deployment and OOP experience. I just told them the honest truth even though I know that they are not the best practice. Did I just f*cked up the interview??

Arghh can't stop thinking

Couple of weeks ago I received a negative response about a code test I did for a front and position. They only said I was not a good fit.

Today, I received another email from them, asking me to do a test. I asked for clarification, and they said they are giving me a chance to redo the test.

Sounds weird, but I'll redo the test anyway. The task is to code a responsive page that consume an api. I'm using vue, sass, git, modular and semantic code. What else should I focus?

The deadline is in 36h.

Damn, we seriously need a more professional system to test (the appearance of) our web apps in all browsers.

Also especially the resizing behaviour with flex items & Co.

What do you use for that? It can be a paid solution, if it is not too expensive.

Believe me or not but there are some companies that do test their software on prod and ignoring users complaining.

What you think of this?

i might not have ssh access to live instances but i can redirect live traffic to test instances and debug my shit there!

... no but i really do that

I like C++, but it is seriously easy to do fucked up things:

class Test{
public:
Test(){};
};

Test test;
Test* test2 = nullptr;
Test& test3 = *test2;
Test* test4 = (Test*)0x12345;
Test& test5 = *test4;
Test* test6;
Test& test7 = *test6;

No warnings at all. I wonder if there is a flag for this kind of stupidity. Here's your sign...