My girlfriend doesn't talk to me anymore after I said I helped the new girl to do some penetration testing.

Two unit tests, no integration tests.

Oops!

I don't know who, or where you are. But want to let you know the test was successful.

I applied for a Softwaretester position. Guess who broke their job application website?!😀
I sent my cv and a screenshot, stating in the email, that I will tell them how I triggered it if they invite me.

Motivational quote!!!!

Someone is testing on production...

Testing

Got this notification. Someone is testing on production environment.

Unit testing be like "all tests passed"

You think your job sucks?

Well, I spend more than six hours everyday testing a million dollar super ugly product on Internet Explorer on Windows.

And when I raise bugs, the devs just bash me up for fucking their code.

Who is the real culprit here, eh?

Now beat that bitch.

F🤬k!! why doesn’t this work on the testing server!l! I swear it worked local.

Meanwhile live:

testing

Stolen from Reddit

Another day at work...

A more experienced friend told me
"don't be a pussy, test in production"

I'm the one fixing the bugs, not him

My little brother (still in school , learning security and pen testing): i found a bug in a website , it returns an xml file instead of the web page , i reported it to them and i think i'm gonna get rewarded like 2k $ for it .
Me : cool ! Show me .
Him : shows me his phone ...
Me : wait , gotta rant this .

Alpha testing be like...

Finally, a good use for Unit Testing :D

Looks like someone is testing in production

When you catch Facebook Devs testing in prod (beta app though)

"Pics or it didn't happen."

-- Me to testers

When you write 2 unit tests and no integration tests.

Holy fucking shit!
I am not a google fanboy but I just witnessed what is called a pre-launch report on my playstore app!

The app is installed on a dozen of different dummy devices and tested by crawlers automatically! And that's not it : You also get a screen recording of your app being tested on all these devices! Oh my fucking dawg!!
That is cool and useful as hell!

The moment I dared ask a colleague about unit testing, and instead of giving me a book or a look, he stashed his work, pulled over a second chair and we coded some, for an hour.

I just sent an automated email titled "Gary is a Dinosaur!" to a lot of humourless clients because the ancient application I was testing assumed I was in the production environment. 🙃

Lesson to self: stop using bogus names in testing.

Still, it could've been a lot worse... 😂

Testing CSS with caching turned on be like...

Testing in production??

Don't know whether to laugh or cry!!😂😥

When the Tester is not at his Desk 😂

Testing:

Just in bank testing app in production

Unit testing?

To tell someone that you’re wrong is called CRITICISM

To do it officially is called TESTING

🤣🤣🤣🤪🤪🤪

- Anonymous

Unit testers be like: "looks like it's working"

Worst bad practice..

Manager: I need code today
Developer (thinking) : let me give it without unit test. Anyways tester will test it.

Manager to tester: complete testing fast.

Tester(thinking): developer must have unit tested it. Let me skip it.
Enjoy testing completed.

God help clients.. 😊

Didnt expect a reputable bank to do testing in this manner. Damn you Axis Bank, your system is supposed to be the best. Smh. 😩

That feeling when one line of code fixed all your errors.

How can testing and debugging 10000 lines of uncommented, obfuscated code get worse?

Testing and debugging 10000 lines of uncommented, obfuscated code in visual studio.

Couldn't resist sharing this photograph I found on internet.

Another example of failed testing.

So today, our "senior tester" logged a bug because he "Viewed Page Source" on the web based report he's testing and the Year values are hard coded! So 2017 will have to added manually!
I burst out laughing so hard, all my colleagues think I'm having a mental breakdown.

So just about to head to the pub and I got the dreaded call from my boss.

The support team had developed some fixes. They "tested" and deployed without letting us know... And you guessed it there was failures all over the shop!

So it turned out their testing was running on a local base install with no integration compared to the live system with 15 years of customisation and complex integration. My they thought this was acceptable I don't know...

And the best part was the developers who made the changes didn't understand their own code (I found the tutorial they copied online) they just blindly copied it without understanding how it worked!

So 4 hours later we found the bug, nothing like having a query and s SQL connection but not executing the query....

There goes my Saturday evening. Now we're was my beer!

Testing the code

A few days after deploying a big important Website into production, I wanted to copy the whole thing including DB back onto our test server for future testing/bug fixing if something comes up. (Last changes were done on production server before going live)
So I opened SSH, removed everything on the test sever aaaaand then I realized I was connected to production...
Took about an hour to get everything up and running again. We didn't tell the client and hoped it would not be noticed.

Sometimes the testers do a good job, sometimes.. 😂😂

You know why I post such screenshot demeaning companies with respect to their application or service or functionality?

Because, as a tester, it pisses me off how these assholes undermine us, our ability and our work towards building a better product.

Fuck such people who think testing is stupid in software world and isn't important at all.

#TesterLivesMatters

#PostedOneDayAgo, #Applied48YearsAgo

test@test.com must have a huge amount of spam! From me alone anyway

As you all know, I test a multi-million dollar product on Internet Explorer running on Windows 7.

Today, I have been assigned a performance testing task.

There are 20+ tabs open on Internet Explorer which takes eternity to load and if a tab is switched the entire page loads all over again.

You talk about having a hard day, eh?

I have been struggling since morning to complete one vanilla flow. SHIT JUST DOESN'T WORK.

FUCK MY FUCKING LIFE.

When debugging and testing programs with huge databases, i acidentally start breaking Records in this company.
Had my biggest curl command with 5000 UUIDs (which just made my terminal crash, never happened before), my longest curl request (over an hour) and now Github ... what were your most ridiculous proportions in coding?

Testing done right! 😂😂

User: “I’ve tried hundreds of different names. How come all the usernames are registered?!😤”
Developer: ”I’m quite confident about my code. Can’t find any issue in this login form.🤔”
QA: “It passed all unit tests. We did a comprehensive testing on live server by registering all the possible names. What can go wrong?🙀”

Me and my team are working on a system where we depend on a component that was built by a different dev team and hasn't been integration tested yet, because it's that new. This is how it's going..

Apple iPhone testing without being on the app store is so annoying, I had to sign up some people to test the app I've been working on and had issues on my end, it really is this whole security bullshit, really it isn't needed.

I couldn't get the team provisional certificate thing to show up because when I clicked the account the team certificate settings would disappear, only after right clicking and hitting help then clicking the team while it was selected could I go to the right window.

I don't see why it's so damn hard to do this crap.

Yet with Android, it's so easy.

I really have issues with the testing for this iPhone app, I went through so many different ways to try and get it to work.

Anyways all done, crashlytics is an awesome testing tool if you can get around that small issue I had.

Practical testing knowledge :P

Speaking of pushing test notifications in prod...

After 10 years of development, and 7 years of being happily married, I'm in love again... With Unit Testing.

"Why does my app have so many bugs!?"
"Why does literally nothing work!?"
"How come you cant fix these problems soon enough?"
...
Me: "remember how you didnt account for testing in the budget or development plan?"
"No"
Me: "thats why."

Testing for equality
😀😁

Who won 😉

Me currently listing to the dev team what the fuck is going wrong with their website after testing it

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

Why you should always test your batch jobs

My worst devSin was testing in production once because I was too lazy to set up the dev environment locally.
Never will I do that mistake again!

Got moved to testing last week, (due to lack of testers) being a developer it requires a whole different mind set to test !!!

But running selenium scripts and again verifying manually sucks.

But what hurts the most is rejecting something that you approved during peer review 😱🤭

Fact:

"Testing can show the presence of errors, but not their absence.."

Someone testing in production?🤔😂

After working 3 years in my current job and my boss hating anything to do with unit testing etc, I used my spare time to refactor our Makefiles to allow for the creation of unit and integration tests. I technically didn't tell my boss about it, so my heart was in my throat when he Skyped me with 'what did you change in ...'?

After having bashed any workflow with testing in it, I showed him the new workflow and automatic testing in Jenkins and he was actually enthousiastic, just like all other employees! I was hailed a hero in the R&D department, after all this time we can finally write universal tests. :D

Me: Are you sure you want this in the acceptance test procedure?
Lead: Yes.
Me: I'm just saying, we don't have any requirements for this feature so it doesn't really belong there.
Lead: Just put it in.
Me: Are you sure? It's a lot of work for something that isn't even required to be there.
Lead: Go do it.
Me: Okay.
*I do the work and it goes to peer review*
High ranking person from another team: I don't see any requirements traceability. Why is this in here if there are no requirements?
Me: WELL AIN'T THAT A GOOD GODDAMN QUESTION!?

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?

Today I started work on a new project that contains a lot of legacy. I asked the developers about unit testing javascript and was told that not only is there none in place, but it's not worth adding any in.

At first, I grimaced and thought fair enough. This is their codebase, it's their choice. I've now been thinking about this for a few hours and have instead decided that screw those guys, I'm adding in a testing framework, a module pattern that's compatible with the existing code, and unit testing the crap out of it. If they don't want it they can refactoring it out, but I can't bring myself to intentionally deliver code I know is crap.

I WILL FORCE CODE QUALITY ON THEM.

Best thing about being a mobile developer:
Whenever your elders give you shit for being on the phone too much, tell them that you are testing your app and get away with it.

Looking for parking in copenhagen airport...

So I asked my company's tools team to fix a bug in their tools related to testing a major feature of our project. They downgraded it to "low priority" because it's "user-specific". I asked how can this be user-specific when it's a major feature. They came back with "well, you're the only one testing it"... Right...

just saw a contract job "Write tests for existing codebase"....

Testing in a production environment is like closing a door in a to kill a snake and electricity goes off 📴

Preaching about unit testing but never doing it myself

Greatest dev sin.... oh god there’s been a few over the years.

Hmm 🤔

I guess one of the top 5 would be making an ecommerce platform without unit testing or documentation for the front or backend. 🤫

Mind you it runs smoothly to this day so I was doing something right 😦

You're not testing properly!

There. I fixed the bug. Tested every way possible 10 times and it won’t break. I’m awesome.

Tells a tester I have a phone with the new app-version installed for testing on my desk when he has time.

He just... came to my room. I gave him the phone. He looks at it, does SOMETHING and just ”Ya man, I broke it”.... whaaaat O.o

Going to talk to my boss about adding testing and git to our project, wish my luck!

Nobody Unit Tests.

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

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

Nobody unit tests.!!

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

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

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

So yesterday I was testing my friend's app which as said by him is 100% okay.
I found 48 major bugs and reported him. His reaction was "Dude these are just minor issues and client don't even know about it. See there is some real bugs?"

RIP to the app developer and the client.

Just spent 30 minutes confused as hell because an API call I wrote just randomly stopped working.

Forgot that I hardcoded an ID for testing purposes and then ended up creating a new object with a new ID.

Needless to say... they didn't match. Explains why my query retrieved zero results.

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.

Testing..

"My code is good, I'm senior and don't make silly mistakes anymore. Tests are for mediocre developers"

This is what a guy who I considered a mentor for long enough time said to me when I was at a junior level. He wouldn't listen to my arguments because I was just a junior obviously and knew nothing about development. Needless to say I kinda dropped the mentor thing after this and a few other things he said or did.
He was quite surprised that I don't want to learn when I have an opportunity to learn from an experienced person. Sorry bud, trust but verify. You failed.

I stayed at work till 8:30 last night writing tests. It was awesome!

Got home and told Mom: "sorry, got carried away".

Fucking first rant here:

So we tried to teach Two new colleagues to typescript and git and testing and stuff and we have a SPOC “which claimed to be very technical”. The SPOC’s task is to keep an eye on the work, and today we have had a review...

After two weeks, the created multiple branches into our git, all with one commit of 400 LOC changed, no merge requestet, issue in Redmine set to “closed”.
Well, by the way they were supposed to write Unit tests for our app.
But I thought, ok, we’ll check their branches.

Their tests all passed (cz) but man, the app didn’t and on compilation there were errors, the app is broken. Damn.

Is it really so far off, that even of They wrote tests, that the app should still work?
AND I THOUGHT IT IS COMMON SENSE. Damn!
Guess how needs to fix it

Time for one of those eye-rolling super vague general question threads 🙃 How do you find edge cases when you're testing your code?

Reason I'm asking is I'll spend AGES testing something I've built, then it goes in for review and IMMEDIATELY the person reviewing it finds some daft edge case I would have never thought to look for.

Current theory is that I'm testing it too much from a developer's perspective (does this request get issued, does localStorage get updated, etc etc) and not enough from a user's perspective (what does this button do) but even then these edge cases keep popping up and it's really annoying 🙃

Who's got some insights?

what do we say to testers? not today

When your product owner tells you to forget about architecture and unit testing, "just push it out"...

I'm surprised management allows us to write false positive tests just to have high coverage instead of refactoring it first. Time to abandon ship.

Uhhhh 👌👌

There is always that one guy.. who doesn't give a fuck about testing and thinks he's not responsible for them...
Le Guy: lemme just push ma new code maan
Jenkins: Unit Tests failed - pls fix
Le Guy to the one who cares about testing: hey fuck uu, ur stupid tests are failing... fix them its ur problem.
*sigh*

"Yeah that test is meant to fail"

I once made a pull request fully aware that 3 tests were failing. The PR was approved and merged.

In my defense, they were very complicated tests and I fixed them a few days after.

When testing and deployment are not two different things for the computer centre department of my college(This is the website to authenticate college students to let them use the internet)

I just wrote unit tests for like the first time in my life (didn't find it useful in university, someone else handing in the project always did that). It cut my coding time by a factor of 3! You should try this one if haven't already, it really saved me a lot of headache right now.

I'm running a very slow test. Watching some numbers flicker on the outputscreen. After a minute I realise that those numbers are timemarks and I'm literally watching time go by. Gonna go do something more usefull.

After 3 years of college, I have finally discovered the magical wonder of unit testing. All it took was me building my own application on the side to motivate myself to actually do it!

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

If you don't want to fix the same issue 10 times, NEVER make fun of a tester.

Dear CTO who approved his own code changes without testing or review,

Why do you hate my master branch? What has my master branch done to you? Did you have to break it?

Especially if not well paid, welcome to India!

I'm using my devrant avatar for some UI testing :P , thanks @trogus and @dfox
(no production and plagiarism intended)

Before i found out about unit tests i'd create a console application where i'd test the functions

Good times

Tonight was the regionals of CPTC, a relatively new competition about penetration testing. Here's our master plan, dont tell anyone ;)

I would describe the test project i inherited as a watermelon test suite,

Green on the outside..............................

Red on the inside

All my tasks was development, last week our boss gave me a testing task, and I completed it.
He said that the developers will hate me if I keep reporting every expected/unexpected, small/big, normal/critical bugs , so that he sent me back to the development team.
I just wondering if I misunderstand the word "testing"!!?

This week at work I spent 20 hours debugging automated tests to avoid manual testing that would've taken a few hours.

Fuck you, code coverage tests, for failing on two input fields in an array, while recognizing the other two in the same array. Fuck you, I fetched all of the fields.

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

That moment when unit tests twice bigger than code itself ...

Quick question:
Anyone here has any apps that they want to get tested for vulnerabilities and stuff?
I am training for job in it-security field but it's hard to find a starting point for testing a real app/site/whatever
So I would like to test some stuff you guys make, just for fun

Do you guys enjoy writing unit/ integration tests?

God save me, I have to write UI unit testing tomorrow

A better way to software testing - 'Test your assumptions first'

Get a ticket for a low priority bug, reported internally. Fix the issue mentioned in the bug.

Moves to QA environment, the original bug reporter tests and *passes* the ticket.

Moves to Staging environment, same exact individual then *fails* the testing. Cites totally new/unrelated changes that need to be made.

Apparently our the workflow is -

Code->QA->Staging->Requirements

Makes sense! :)

Hate it when the beta tester always laughs when he finds a notorious bug, but loves it when I fix it in mere seconds and his laugh slowly fades...

The feeling when your scrum master or lead ask you run the automated tests against the application though they know the application is down or not working.

I just heard someone quote this
"To complain about a problem without proposing a solution is called nagging."

I know the perfect name for QA team now. 😁😁😂

coworker : hey can you test this? doc should be up to date.
me : ya, sure. *looks at vague test case* ... what's the jar/doc name?
(15 later)
coworker : oh it's ___
me : ok i found the doc, where's the jar? do you have it?
(15 later)
coworker : oh i'm building it in jenkins now
(30 later)
coworker : ok it builds (link to jenkins)

how did you not know i'd need these things to do what you're asking? >_>

Too much technical debt
Write more unit tests
Unit tests failing, the code will be right so change the tests to pass
Too many unit tests to maintain, they look a lot like technical debt
Remove unit tests to reduce maintenance overhead

Testing in production? Stupidity?
Yes.

If I'm writing an app which has the sole purpose of receiving some data from a server, then sending some other data back (so nothing is stored locally) - what sort of stuff do I write tests for?

Client wants lots of testing to occur, but all of the tests I can think of wouldn't add any value

Tester says that selection to is dark when they selected a dark color.. 😑

Company started automated testing recently, and the devs need to review the test scripts.

The tester assigned to my component writes script to trigger button click and nothing else to verify the result.

I couldn't​ even. I just left work for the day.

So I'm trying out docker and see how I can make use of it, current setup:
1. Ubuntu on VM and Mac for Asp.Net core development
2. Windiws for MS only stuff like SQL Server
3. Ubuntu Server on VM and is running docker images: MS image for SQL and Ms image for dinner core.

What I did so far one script which will handle updating SQL Server database on windows with the changes done on docker SQL image
Then publish website from Mac or Ubuntu to docker image. I have yet to find a way to execute scripts remotely on a docker image using bash script from a remote

What should I do next? And for home setup go for Ubuntu server or CentOS? Any recommended packages for server administration? Workflow ..etc.?

rant?
When you want to write the unit test that demonstrates a subtle bug, but before recreating the same preconditions you end up writing 15 other tests, testing a lot of other stuff too, that in turn show other bugs, and skyrocketing the coverage (that was sitting at 0% actually).
Like I wanted to repair a hole in my umbrella to not get wet, and built a house instead.

Testing in production eh?

A bunch of testers got laid off at my company and we're facing a release. So our PM put all developers on testing with a total of 6k test cases (!).

The overall mood at the office is not good..

Testing had some issues with system integration. I asked them what their setup was.

Answer: "Almost similar to the real hardware."

LMAO!

If you are not living om the edge you are taking up too much room.

#imgur

Bug detected!

Not testing for ~ 2 years but I already have been punished. Please forgive me.

Trying to unit test legacy code with lots of static methods suuccks!

lets just wait till the day before deploy to finally authorize api testing for users outside of the network - and then get super upset when we aren't adjusted, prepared, and tested in time for next-day deployment

Not testing.

All the repos I have pulled for work have not had any unit tests. (well they have one test that does assert(True))

Until I found 1. One singular repo with unit tests. I get happy. I run said tests against the code in master. Tests fail

Haha, got this flipped?

I've been writing tests all week.
I quite like writing tests in some respects, but I absolutely detest it if the thing I'm testing is a moving target! Stop changing your mind! Either we support the feature in it's entirety or we don't support it at all!

TLDR: fuck this plugin.
Longer version: I recently had to implement an external Vue plugin to upload files. That gave me a good headache already, mostly due to the half Chinese, half Google Translate English documentation. I now found out that testing the implemented component may be impossible. Turns out it overwrites the $route and $router variables and makes them read-only. Which won't even let me create a shallow mount of my implementation. Fuck this shit, I'm getting a drink!

Since my ISP doesn't allow port forwards on that port, does anyone want to open their port 445 (if not otherwise occupied by Microsoft-DS) and have netcat reply an empty string or so any request (such as an empty string) sent over TCP (or has anyone already done so)? It would help me out a lot with testing out some networks full port range (since portquiz.net's hoster blocks that port) and would take close to no bandwidth for you.

So i'm working with people from another team to bring about a feature. I was wondering, "how come they're churning out so much shit in so little time!?"

Apparently, they make code, merge request to the release branch, and then do unit tests later.

How do people, in good conscience, think that they can skip unit testing for extremely vital components???

Nothing destroys an ego quite like the cold, ruthless testing of your software by the QA team. I humble once more.

When you need to do load testing and the boss just tells you to refresh the page multiple times. Yep that covers it.

Dev: *completes tasks, pushes to UAT and assigns to PM in Jira for testing*

PM: *receives notifications and immediately bulk change on all taks and assigns to client without testing*

So what is it you do here...?

Yet another ticket comes in about a feature not working after we push another update. So in my meeting I bring up adding testing would reduce this. Yeah boss just wants me to fix this issue and just do manual tests....fml

when your boss says "we are bringing in testers but the dev team is not allowed to talk to them" O.o !

Do you test your codes while coding or after completion?

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

When your last test is finally over and everything works.

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

There's a special place in the very bottom corners of hell for whoever programmed the current Debian installer. There's an even special-er place there for people who actually ship their distros with that fucking disability of an installer, Kali Linux and Parrot Security specifically. I'm not booting from USB either because I don't have much space and it's buggy anyway.

Because of it, I can't install any pen testing distro to my PC. There's backbox but it's garbage with very little tools. I can't get wifi to work in blackarch, and there's NOTHING else even worth looking into.

Stop trying to make gold out of shit. Re-spin your distros with Ubuntu instead, which is a Debian derivative by people who actually use their brain. Let Debian die a painful death because it's maintainers do not give a fuck about their work. I can't be in the minority here. Even Linus Torvalds said he hated Debian and that was a long time ago but my point still stands, maybe.

After writing ~200 lines of code and then unit testing it

THE TESTS ALL PASS!!!

then I run them again just to be sure and they all pass but mocha is saying I am getting 40ms lag on some of my tests...

Noooo!!!

This is meant to be an async message passing system; I cannot have an input lag of 40ms :(

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%

Last year for company I work I made OAuth server + SSO discriminated by business unit in php. Well it was quite complex project and security sensitive, so I wrote tests for every piece of code. Then I made client for it with abstractions to be easily extendable, but was too lazy write tests for it.

Anyway, today needed to add new grant auth strategy. Thought, I could also write tests for the client this time. That was the mistake...

I installed codeception (testing framework), tested every class, and then left the main client class for the end where all http communication and other magic happens.

So turns out, I can’t capture function parameters with codeception (at least its not documented), so I can’t assert if data in the end is correct. I mean it’s fucking abstraction on top of phpunit, which can do that, so what the fuck? But ok I probably could just use phpunit, but anyway why the fuck you would create mock abstraction with only 20% of functionality from original implementation? It doesn’t make fucking sense...

In addition, I was testing code written with guzzle http (http client), and that is some pile of shit. Just why the fuck I need to write 20 lines of code just to get a fucking json response...

Fuck this shit, I am not going to test it anymore, it just makes me hate php, I barely can deal with all that angryness inside me.

When explaining unit testing:

"We tried but every time someone changes something in the database all the tests fail."

*facepalm*

Full round of QA, full round of internal testing, and the client still finds a bug nobody can reproduce.
🤷🏻‍♀️🤷🏻‍♀️🤷🏻‍♀️

So, I recently added a new feature to our app which allows the user to rotate/crop the image before being uploaded to our server, and we have an option to upload pdfs as well, so when I gave this feature (rotate/crop image) out for testing, the tester in our organization tells me where's the option to rotate the pdf? And I'm like where have you seen someone rotating a pdf? He's like that's the reason why we need to have it. And now the PM wants me to add that in the next release, after explaining them for 30 mins that pdfs don't rotate, they tell me to do a proper research on it and then revert. 🙃

How many people do unit testing?. Am always caught my deadline. I just fix errors in production. The client timeline are not feasible

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

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

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

So now I'm writing automated automated tests 😁😅

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

If you merge PRs without testing...
Just.
Stop.

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) 🙄

I know its a serious business - but there is a lot of talk re: testing (nuclear) at the moment.

It kinda puts things into perspective when we talk of programming tests. Makes me wonder how military engineers think of testing given that nuclear tests are ultimately illegal (I think) under international law.

!rant
Anyone interested in testing a password manager?

Been wanting to get into OOP and unit testing, haven't found a single semi big project that I can use to study these techniques...

Wrote myself a class when asked to do an API call last week, and I think it looks pretty decent...

Does anyone have a ressource to just see how to do it "properly" on medium sized projects? (100k loc)

Testing crap on production in the middle of the day.. flm

When you leave tests running overnight and one falls in the middle of the night

When testing things..

Product Description: Expensive Imported Turkish Pen

Product Image: A bag of Snickers

The "asdfghsjgllhdk" text doesn't look very appealing.

I promised to blow off unit tests, so here we go. Let’s talk about unit tests.

Why use them? So, unit testing connoisseurs outline two big purposes:
1. To keep application integrity,
2. To catch bugs.

Keeping app integrity is when your freshly hired developer implement something that potentially leads to the whole app failure, but unit test fails and tell you that newly added code is breaking the app.

Catching bugs is pretty much self explanatory. Just think about it – you have to actually write code that describes how to check up another code to catch bugs in it.

I personally hate unit tests. I can’t explain, but every time I forced myself to write them, I got vertigo and terrible headache to the end of the day. Trying to write some tests? Here you go, wooosh and you can’t work anymore. Go get some sleep if you can.

But I still needed my job to be done and it should have been done really well. So I started my research.

Recalling Steve McConnell’s and many other classy developers’ experience, there is only one decent solution that prevents bugs and inconsistencies at large scale – the specs. Developing the specs should be considered the task number one. With decent, robust specs, app is almost guaranteed to contain no bugs.

Let’s take a look at the piece of great spec. For example, imagine you have to implement validation logic. So you state that validation should be implemented with special validation functions and then you define what validation function is: a pure function that accepts a value and returns boolean: true if value is good, false otherwise.

With that in mind, it’s obvious that potentially present bugs can only be inside that pure functions. Our spec made implementing validation very easy and idiomatic, isolating potential bugs. As soon as validators are pure and simple, unit tests aren’t needed at all.

You know what? As your app scales, you’ll definitely need a spec, sooner or later. Growing up without spec leads to irreversible failure, your app will grow like cancerous cell does and it’ll be easier to just put it into trash and start up from scratch.

But specs have one major downside – it requires at least one enlightened developer with really great experience to create it. It can’t be done quickly, it’s a very costly and difficult process. That’s why making great software costs that much.

But what if you need an MVP right now?

Speaking of MVPs, you’ll have to go with simplest instruments possible. Throw away Jenkins, use your Plesk autodeploy from Git repo. Throw away complex frontend setups, go with $30-$40 glittery ui kit or even an open source thing right from CDN, without less, sass, gulp and all that jazz. Make use of create-react-app if you can’t avoid using React because you’re making a web application.

Throw away AWS, Azure, Docker, Kubernetes and everything like that. Buy a cheap PHP7 hosting with pre-installed MySQL and do everything as simple as possible. If you have to use NoSQL, go with free Heroku with git autodeploy, NodeJS Express and free Mongo addon.

MVP should be ready in two weeks. As soon as your infrastructure is that simple, you don’t need unit tests. They’ll slow you down. Once you MVP is ready, go get funding, throw away first MVP, hire a decent CTO and let him create the spec.

Right there, it may be noticeable that unit tests are probably the biggest and baddest workaround imaginable. It gives you false sense of controlling your bugs, while you don’t have any control at all. Obvious bugs that unit tests can catch are easily noticeable at concise system, while quirky bugs couldn’t be caught by them because you can’t even imagine them while writing your unit tests. At this point, unit tests are just waste of time.

So, the whole picture is clear: at a small scale, you don’t have time to write unit tests and don’t have many bugs because of simple tools and standard patterns. At large scale, you need a spec to prevent bugs, unit tests become redundant as long as your spec is good.

In conclusion, I can tell that I’ve been developing a Clojurescript + CouchDB app for some startup, and in 8 month coding by spec I made myself I encountered only two or three bugs, all related to external JS tools and its quirks.

Have a good time!

Optimism is the occupational hazard of programming; testing is the treatment.

Find who said it.

Ya know, automated testing was supposed to save me time and trouble... Seems like it's just a different place for bugs to crop up

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

Guess I'm getting old (school) outputting foo, bar and baz for testing purpose. Does anyone still using those too?

What unit testing tools/frameworks do you use?

Testing during development. -_-

I feel like that most +1's are given during the work hours when the devs are twiddling their thumbs or waiting for the codes to compile. So here is a rant testing this hypothesis.

My company never used unit tests. And i would love to educate but i do not know how to unit test properly. I always en up with: if i want to properly test all ins and outs of this class's + operator. I need to add checks for positive number, negative numbers, nan, infinites, nulls etc. Etc. It needs so many tests for something so stupidly simple, that i don't see a way to motivate people to use it.

Am i missing something? Is there a guideline for "ok coverage"? Is testing just that much work and is that why nobody cares until it is too late?

I have been reading a book about working with legacy code. But still i got no answers. Halp!

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.

Just spent 3 fucking hours trying to find out why my tests are failing. I'm mocking ef with an in memory sqlite dB as THE FUCKING. Net docs say to.

My code does a simple decimal comparison in a linq statement and returns bullshit. Why? Sqlite does not have a decimal type, it does some sort of BULLSHIT to convert it into some sort of text value.

I change all my models to use doubles instead of decimals and all my tests turn green.

WTF IS THIS SHIT. If it doesn't work don't tell me to use it. I expect better of the. Net docs. Wtf are they doing.

When nobody acknowledges testing as a proper and important task: My boss gives my three week to develop a small app - I remind him that testing has to be done and he replies: "OK, you get three weeks and two days for testing"

Always a good idea to test :)

Every. Single. Time. I've tried to learn and implement proper Unit/Instrumentation testing, the main Android devs decide to go for something else or introduce some feature or Gradle plugin that breaks every tutorial out there. I find it way easier to just test everything manually than learning the new yearly trend. Am I the only one?

Hey. Question.
How many people have testers as part of their dev cycle?
How are they used in your organisation? And whats your opinion of hacing them?
Do they give you confidence in your work? Or do they slow your delivery down too much?

Why on Earth would a Performance Testing application such as JMeter have such a low Java heap space by default.. i mean wouldnt it make sence to set this as high as possible for a Performance Testing tool ? 😞

Stupidly tested some sql on development to return results for an admin (see the whole results) and stupidly didn't test the where clause for generic users (only see a subset of data)

To find out on production the where clause was being run because it wasn't a where, it was an 'and' and 'where' was not being used before so made the whole users get the entire results.

My own fault for not testing all use cases. Horrible though.

Today is day two of User Acceptance Testing for one of our biggest and most complicated developments.

Today is also the day the requirements were agreed.

Somebody, somewhere is taking the piss.

How do you even get started on React Native testing sldjflsdfhl sfsakdhfsak fhkls