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.

Testing

Someone is testing on production...

Got this notification. Someone is testing on production environment.

Unit testing be like "all tests passed"

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

Meanwhile live:

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 .

Finally, a good use for Unit Testing :D

Alpha testing be like...

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

Just in bank testing app in production

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!!😂😥

Testing:

Unit testing?

To tell someone that you’re wrong is called CRITICISM

To do it officially is called TESTING

🤣🤣🤣🤪🤪🤪

- Anonymous

Unit testing, unit testing, 1-2-3. Is this thing on...?

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

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.

Testing in prod.
On Friday evening.
Before long holiday.

Because why not.

I am backend + a bit devops
8 months I worked with front-end person in react.

8 months he was telling me.. git usage is not needed for front. There is no need for that, it is not like back.
Recently he made refactorization in a week time, this idiot did not do even single commit in the process.

4 months he was telling me, testing is not needed in front. Even if the work is complete, there is no point to cover with testing.

Today I heard from him, adaptive web design is impossible to do in css only, it needs having javascript to control right height and width size for elements.

At last. I got freed from him. He got fired.

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.

my boss bought iphone 7 for testing...inserted his sim card and takes phone with him self all time...

Testing the code

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

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?🙀”

My bank testing in production environment 😂🤣😂🤣

Someone is caught while testing on prod.

Practical testing knowledge :P

Testing done right! 😂😂

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?

STOP. TESTING. IN. PRODUCTION.
STOP. TESTING. IN. PRODUCTION.
STOP. TESTING. IN. PRODUCTION.
STOP. TESTING. IN. PRODUCTION.

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.

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

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

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

Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.
Vulnerability scanning is not penetration testing.

Testing for equality
😀😁

Who won 😉

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!

Me: Hey boss, if you ever need someone to get into doing DevOps related tasks for the team, I'd be more than happy to take that on.

Boss: We don't really need any dedicated person to work on that, but if we do in the future, I'll let you know.

Fast forward a few days: I am now unable to deploy bug fixes to our testing environment, now in the cloud, because all access has been blocked for everyone except the two numbskulls who thought it'd be a great idea to move EVERYTHING over (apps, configuration manager, proxies, etc) first.

Oh, and this bug is affecting production.

Somebody at Samsung is testing something in production 🤭

It's "Find my mobile" which is preinstalled by default on Samsung devices

Fact:

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

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 😱🤭

Another case of testing in production, who knew EA actually did testing?

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.

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

Caught someone testing in production on my way home the other day....

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?

Deadline : Friday evening
Testing : There is only prod
Deploy : Friday evening
Why : Boss says customer wants it
Me : . . .

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

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

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

interview today

me: and can you tell me a little bit more about your development process? e.g. an example dev cycle from reqs to testing and review...?

senior dev interviewing me:
*gives frustrated/annoyed "why tf are you asking these?" look*
So, uh, we don't really use testing for these projects cuz it would make it harder to refactor later.
(and responded nothing else on the topic)

I left shortly after that.

Preaching about unit testing but never doing it myself

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

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.

Testing..

Yet another dev team testing in a production environment

You're not testing properly!

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

Nobody Unit Tests.

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

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

Nobody unit tests.!!

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

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

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

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

Google runs A/B testing by having 11 messaging apps

Writing a Unit test to test the Unit test that's testing your application, because you can never be sure about anything.

If client started testing my app :D

Jest? It's the perfect name for a testing library, because I certainly feel like a clown! 🤡

#clowndrivendevelopment

Don't worry dear customer. I will mount it for you. I I'm an engineer

I don't care how bad your testing suite is, it can't possibly be worse than this

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.

I know politics is not allowed here, but I have to share this gem with you.

One day before the election for the European parliament the website of the German city Bochum showed a wrong bar diagram with false results of the election for a few seconds.

Everyone was loling. But I was like WTF? They were testing in production. And also they included data were the party AFD had about 50% of the votes. Are they retarded or so?

Unit testing is cool and all, but FFS...

If you want unit test - cool. But its not drop-in replacement for functional testing!

I believe each release should be manually tested.

I seriously cannot stress how important it is to build good reliable tests. Especially regression testing.

I am crying inside over the amount of time I've lost in my integration hell.

Seriously stupid shit that should have been tested but never did because I was too fucking lazy. Don't be me. Don't put yourself in the hell I'm in. Be better.

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!

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)

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*

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"!!?

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

lol, I just got an email from HBO Max that said, "this email template is for integration testing only."

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

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

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

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

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

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

Departure: 13.00 Train: test Destination: A1 Delay 18888min

Now it is 15:43 and it is still on...
Finaly poland joins the testing in the prod club!
Station is Wroclaw if anybody is interested.

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

Answer: "Almost similar to the real hardware."

LMAO!

My brain: Testing is a good practice

Me testing my project:

Testing in production eh?

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! :)

I'm genuinely shocked at the number of people I see on here bashing automated testing as a waste of time, simply because my entire career has taught me the opposite (and it's usually only non-technical managers I see who don't want to see "time wasted" writing tests.)

I'm also just as genuinely curious - what do you guys do instead? Just don't test and deal with production issues as they occur? Pass it off to a separate UAT / human-based testing department and let them sign it off? Assume that because you're using Haskell / some other discipline it'll work if it compiles?

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

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

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.

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

Holy. Shit. Tests. I am testing. All week. Nothing but tests. I am one with the spec. You know what I realised today? Tests are a bit like life. Life is just one big spec suite that takes 75 years to run. Except there's no prod environment at the end of the DMT tunnel waiting for our green pass docket to say 'take me Lucifer, you absolute visionary: I'm ready'. We're all just a spec with no application. We're doomed. Nothing matters. I need to lie down

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

If I had a nickel every time the unit tests failed not because something was wrong in the code, but because someone had messed up the unit test I'd be able to retire early.

I just spent the better part of 10 hours hunting down a bug in some production code only for the test to be wrong because the person who wrote it had mocked the http response incorrectly.

Nothing I did to "fix" the code worked, because nothing was wrong with it...

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!

Not testing.

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

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 :(

Testing in production? Stupidity?
Yes.

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

Testing

And when I have improved Testing, the next one will be…

Testing

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.

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

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.

TFW the mock class has way more code than the real one.
Testing big infrastructures can be a pain...
Or maybe my team is just not so good at it.

My time spent:
Adding new feature to the real class 15%
Extending the mock with the same feature 55%
Writing tests 30%

me, testing my software:

"ok, well it works for this case.. let me make a spreadsheet of all cases and test them one by one"

*doesn't create spreadsheet

*3 use cases later..

"Ah, you know what, this seems fine, I didn't change too much...............................
...........................................................
..........................
...............
.... it should be ok"

*cough*

you know what happens from here.

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

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

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

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

Find who said it.

Doing GUI agile testing with the QA before passing my code to test server. I do this 'cause the QA marked in the past a lot of bugs that aren't bugs because he didn't liked the wording (in spanish there's A LOT of ways to say the same thing), the color of a button or an icon, and this delayed the release of the code a lot of times. So, this way I can change things to avoid unnecessary bugs... if the QA is not so busy XD

I've deployed an instance of OWASP Juice Shop on Heroku, if anyone wants to practice and/or learn pen testing or just web based vulnerabilities in general it's an amazing application to learn from and practice on.

Your progress is dependant on the cookie, so it won't affect one another.

owaspshop.herokuapp.com

It's free, so if you want to deploy your own instance you can.

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

When explaining unit testing:

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

*facepalm*

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

Ok ok ok, I will preface this by saying I am still a student so you can assume my complete and utter lack of experience.

There is all this fuss about unit testing and TDD but i still have my doubts about it. How is it that if your code works for certain inputs you can be sure that it will work for whatever can happen after deployment?

I mean, to my understanding testing can assure that some business requirements are cared for but as far as actual code correctness goes I don't see how that is achieved.

As far as i am concerned the closest it comes to complete code correctness is a mathematical type of proof but that should be impossible to be done effectively in an OO language.

How can you be sure that your code is what you think?

(If i have this all wrong please correct me)

God I'm getting tired of the whole TDD culture. I get it, testing is good, but we're getting to the point where several major OSS projects fail on common real-world use cases because instead of worrying about the main purpose of a software, devs only worry about satisfying their artificial tests. And when someone opens an issue, it just stays there for months or even years simply because setup & teardown logic for the required tests would be several times more complex than the actual fix.

Has hacking become a hobby for script-kiddies?

I have been thinking about this for a while know, I went to a class at Stanford last summer to learn penetration-testing. Keep in mind that the class was supposed to be advanced as we all knew the basics already. When I got there I was aggravated by the course as the whole course was using kali linux and the applications that come with it.

After the course was done and I washed off the gross feeling of using other peoples tools, I went online to try to learn some tricks about pen-testing outside of kali-linux tools. To my chagrin, I found that almost 90% of documentation from senior pen-testers were discussing tools like "aircrack-ng" or "burp-suite".

Now I know that the really good pen-testers use their own code and tools but my question is has hacking become a script kiddie hobby or am I thinking about the tools the wrong way?

It sounds very interesting to learn https and network exploits but it takes the fun out of it if the only documentation tells me to use tools.

When you join a project that has no testing, no component policy, a lot of css mixins, that has to work simultaneously as a pwa, android and ios app.

Oh, yes, obviously no documentation at all *flips table*

Google search dark mode is available in some of my browser profiles but not others. A/B testing time again, I guess.

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

Testing every little class and stateless function is a brilliant way to spend a lot of time doing nothing.

At the same time, if I didn't have to test it, I probably wouldn't have turned it into tiny classes and mostly stateless functions.

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?

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)

!rant
Anyone interested in testing a password manager?

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.

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

"Testing one user early in the project is better than testing fifty near the end." - Steve Krug

Anyone have much success with Kali/WiFi penetration testing?

I've been tasked with trying to break WPA security within a couple of hours without a dictionary attack - is that even possible?

I have an Alfa AWUS036NHA capable of monitoring mode if that makes any difference. It's my first time trying anything like this.

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

The scope for this project was absolute horse shit, and now they are mad because the end product is still horse shit...

I want to feel guilty for the outcome, but I just can't. This is something they should have had foresight for. Validation and testing is absolutely atrocious here. No official real scenario testing, and now the whole thing has been blown wide open for all the shit it can't do.

A customer asks for a change request or a bug fix and it results in creating a ticket for that.
It's the process and how it works in most places but after you finish with the task and fix the same customer who provided you with the requirements will request that you share the steps on how to test the fix or the feature.
I'm not speaking about the data preparation or required configuration. I mean a step-by-step instruction on how the tester/QA will test it.
It's driving me mad!! So a way to counterplay this stupid requests, I provide the happy path and what to expect. And in case, they stumbled on a bug later in production, I can easily say "It was approved by your testing team and that's a new requirement ;)"

After years of back-end development there's a thing which keeps bugging me: how little "interactive" the development process can be.
When I did front-end I took for granted that the application I was developing was easy to run so I could immediately test any little change I do on code but on back-end this is rare to see: you develop with tons of external dependencies (authentications, VPNs, databases...) so getting your application up and running can be an huge hassle and testing API controllers can be slow and frustrating since I have to continuously juggle multiple development environments, manually regenerate tokens, do guesswork to find which parameters you have to use for your API request, maintain my Postman/Insomnia HTTP calls collection to prevent it from turning into an unusable spaghetti mess... lots of repetitive tasks which kills my focus and makes me struggle in getting into a decent flow.

Automated testing has lot of potential in helping with that but its hard to introduce when you're rewriting a legacy sistem and you're already exceeded your budget.

I wonder if I'll keep doing back-end once I'm done with this project.

Testing in production 😂

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.

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 ? 😞

When you have only done unit testing and not integration testing.

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.

So I'm working on some communications app which bridges the main server/database with some equipment on the field. Now this equipment works in a redundancy pair: two cpus, A and B, both connected via ethernet, one active, the other standby/replicating and no comms on it. One obvious requirement is that when this equipment swaps the active cpus the comms app should switch as well. Fair enough, going with this into testing phase.

This guy, from qa, got some instructions from someone else:
1. Trigger the soft switch from equipment so that cpus got swapped.
2. Remove the ethernet cable from the standby unit.
3. Observe the communications.

And the test goes like: cpu A is active, B is standby. Switch is triggered, B becomes active, A goes into standby. The cable is pulled out from cpu B.

Test result: failed, no comms ever

When testing things..

Product Description: Expensive Imported Turkish Pen

Product Image: A bag of Snickers

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

!rant

It's Friday. Today I'll be soldering and testing (I really should come up with some tests now) my new hardware all the way to the weekend. Woooo!

I hate it when you put a project into testing and the feedback​ tells you you've missed a really​basic but important feature...

Anyone know how to go about unit testing an application that is made up of:
- Electron
- Node
- React
- Typescript

(React using Typescript of course).

Electron has its own framework (Spectron), people seem to use Mocha with Node, React has its own tools like React testing library (and testing UI components will probably end me) and Typescript seems to play best with Jest - but a special Typescript flavour of Jest called ts-jest is preferable because the only other option is having Babel and its Typescript support that doesn't type check.

I want to beg for the sweet release of death.

For my viva today my teacher asked " do you know white box testing, black box testing, stress testing"
Me: sir, I know stress testing the best and I know little about the others.
Teacher: Explain white box testing.
Mind blown!

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"

My brain hurts from trying to figure out this unit testing crap. Is it just me or is it really a struggle to test your front-end code? I'm using jest and enzyme to test our React app but complicated parts of code with multiple state changes or calling props is making my life a living hell. I mean I usually just debug by console logging everything and it works lol...but my fucking boss has forced me into writing this unit testing crap. FML.

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

Testing during development. -_-

I know you can start a build process in the visual Studio dev console. Is there a way to start this process from a PowerShell sript? And if yes, how do I do this?
I want to/ need to learn automated testing.

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

Life would be so much better with real-time testing

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

Hennies I need your assistance!
My boss has put me in charge (wow yes I was surprised too) of figuring out what a good solution to our current testing nightmare would be. Therefore my questions for you are:

What kind of testing strategy do you work with at your job? Do you use any tools for it? How's the division of unit tests/service tests and/or UI tests?

I'd really appreciate you guys' input on what works (and what doesn't, in case you're living a nightmare with testing daily)

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.

What are your thoughts on documenting developer (local/dev) functional testing? Should we be trusted that we've tested our shit and it works? Or should we provide proof? Are we better to provide proof to protect ourselves?

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.

Why are there so many testing framworks for JavaScript? Jasmine, mocha, buster ... and for spies, stubs and mocks, there is sinon and for assertions, there is chai. And oh you can record entire external api calls with nock and whatever else I forgot. I am a bit overwhelmed by this overambundancy of libraries. Writing tests is supposed to be easy.

Coworker: "Hey, so I discovered this library that automatically brings up and tears down local containers to perform unit tests on data sources"

Me: "Sounds neat"

Coworker: "Yeah, I've been messing with it locally, and it means we don't need to have the data sources installed on our machines or rely on the ones in the testing environment."

Me: "That's good"

Coworker: "Just a shame I had to roll back our testing framework to a previous version and refactor the code in all our other tests as a result."

Me: "Wait what? *looks at documentation* It says they support the newer framework"

Coworker: "Yeah, but I couldn't get it to work. So I'm just gonna make a PR for it, okay?" *Proceeds to make a PR, approve and merge the code before I can comment further on the changes*

Welp, there goes all my motivation to get anything done for the rest of the day.

When you roll out a new system is disaster recovery testing on your roadmap? For example, do you do failover and have users work through a comprehensive test script and have them sign off before going into production?

Should I be even be testing if no one cares.

I keep asking Devs regarding the functionalities of their system for testing and then, realize it's already on Prod even before I test in beta or enable to test in beta.

Do I exist!!!

Now, for the nth time, I have started to test when things are almost there or already there in Prod.

I should keep myself in adrenaline mode always on from now on.

Need to do something worthy.

The worst way to start a new job.

Testing builds remotely with pushes before testing them locally because I'm too lazy to bring up the local CI server.
Ending up with over 9000 "Testing build" commits.

I've been trying to push good practices at work, which includes migrating testing environment to vagrant.
Been trying to push it forward for months, and this week, a "genius"co-worker just started complaining we shouldn't overcomplicate and just provision a vm for testing for everyone to use, and boss agrees immediately!
Guess who'll have to maintain it whenever someone remembers to destroy it...

Testing on production !

Testing in prod? Really AliExpress......

I fucking hate manual testing, specially if a DB is related

I almost completed the transaction on prod instead of dev. Testing is dangerous.

Trying to learn JavaScript unit testing with Vue.js and it's not going well. Took long enough just to get everything installed and now it errors as it doesn't understand <template> tags. Why is it so difficult?

When do you think that testing is overdone?

Ionic be like: Testing? Fuck that lets just bring out ionic 3.0 beta and let our testing example repo die with a few pull requests from one dude who actually tries to keep it updated

When testing means finding all the stuff the customer will bitch about rather than creating patch requests.

Coding the new functionality, 2 hours.
Writing and testing the unit test and e2e test, 2 weeks.

This is a test rant for future testing, please ignore!

Is it actually required to write unit tests in microservices?
every time i write them it feels like im just redundantly copying a method...
Dont get me wrong, im not against testing, I am using test environments, integration tests and mocks, but unit test seem kinda redundant to me.

After finishing my last lab for the semester, in testing, I really get a sense of respect towards testers!
How do you manage to have the patience?!

Did this interview with a tester for internship. Started to get the feeling that this person maybe should have chosen another education.
On the question: "What do you like with testing?", the answer was "Designing templates for bug reports".
Guess it's gonna be a quite boring career.
And no, we didn't hire.