Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
My girlfriend doesn't talk to me anymore after I said I helped the new girl to do some penetration testing.27
-
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 .
9 -
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.3
-
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... 😂13 -
To tell someone that you’re wrong is called CRITICISM
To do it officially is called TESTING
🤣🤣🤣🤪🤪🤪
- Anonymous3 -
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.. 😊5 -
Didnt expect a reputable bank to do testing in this manner. Damn you Axis Bank, your system is supposed to be the best. Smh. 😩
1 -
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.5 -
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.5 -
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.2 -
my boss bought iphone 7 for testing...inserted his sim card and takes phone with him self all time...2
-
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?🙀”1 -
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?
7 -
STOP. TESTING. IN. PRODUCTION.
STOP. TESTING. IN. PRODUCTION.
STOP. TESTING. IN. PRODUCTION.
STOP. TESTING. IN. PRODUCTION.18 -
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.4 -
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
1 -
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!4 -
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.9 -
"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."2 -
Somebody at Samsung is testing something in production 🤭
It's "Find my mobile" which is preinstalled by default on Samsung devices
8 -
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 😱🤭3 -
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...
-
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.1 -
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.7 -
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?6 -
Deadline : Friday evening
Testing : There is only prod
Deploy : Friday evening
Why : Boss says customer wants it
Me : . . .11 -
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.9 -
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. :D7 -
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.o2 -
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 in a production environment is like closing a door in a to kill a snake and electricity goes off 📴
-
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. !!!4 -
Writing a Unit test to test the Unit test that's testing your application, because you can never be sure about anything.
6 -
When your product owner tells you to forget about architecture and unit testing, "just push it out"...
2 -
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?4 -
Jest? It's the perfect name for a testing library, because I certainly feel like a clown! 🤡
#clowndrivendevelopment4 -
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'm surprised management allows us to write false positive tests just to have high coverage instead of refactoring it first. Time to abandon ship.
-
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.9 -
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)
5 -
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*7 -
Been a long ass day, then some later afternoon prepush testing that went long and wrong which led into night - and after all was said and done we had to throw our hands up and say...
https://youtu.be/Qy-Y3HJNU_s
-
This is the most impressive testing document I have ever read. Props to the SQLite devs for doing things so thoroughly.
https://www.sqlite.org/testing.html -
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.1 -
I'm using my devrant avatar for some UI testing :P , thanks @trogus and @dfox
(no production and plagiarism intended)1 -
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"!!?1 -
Departure: 13.00 Train: test Destination: A1 Delay 18888min
Now it is 15:43 and it is still on...
Finaly poland joins the testing in the prod club!
Station is Wroclaw if anybody is interested.
2 -
lol, I just got an email from HBO Max that said, "this email template is for integration testing only."3
-
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
6 -
Tonight was the regionals of CPTC, a relatively new competition about penetration testing. Here's our master plan, dont tell anyone ;)
5 -
This week at work I spent 20 hours debugging automated tests to avoid manual testing that would've taken a few hours.5
-
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?14 -
"Manual testing is often quick and easy and satisfying – you can directly test your application, one can see the results immediately on your screen, and one can interact with the application “for real”, instead of in the sometimes-awkward scripted/mocked mode of unit tests. It’s a very natural instinct.
However, it’s also largely-wasted effort! A manual test only verifies the current state of the code base. As soon as you make a change, you’ve started to invalidate the results. If, however, you take the effort to encode the test in code as an automated test, it continues to be valid indefinitely into the future."
https://blog.nelhage.com/2016/12/... -
Testing had some issues with system integration. I asked them what their setup was.
Answer: "Almost similar to the real hardware."
LMAO!2 -
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! -
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
-
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...4 -
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..4 -
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. -
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! :)1 -
Nothing destroys an ego quite like the cold, ruthless testing of your software by the QA team. I humble once more.
-
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. -
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....fml1
-
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. 🙃4
-
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.
8 -
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.7 -
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
-
Full round of QA, full round of internal testing, and the client still finds a bug nobody can reproduce.
🤷🏻♀️🤷🏻♀️🤷🏻♀️1 -
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 -
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???1 -
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. -
I would really like to know the backstory on why Boeing just completely skipped integration testing on a craft designed to carry humans to the ISS. This seems particularly egregious and is an indicator of just how comfortable companies get when they’ve entrenched themselves with government largesse. https://orlandosentinel.com/space/...5
-
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.9
-
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)10 -
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.2 -
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)8 -
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*2 -
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%7 -
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?1
-
How many people do unit testing?. Am always caught my deadline. I just fix errors in production. The client timeline are not feasible2
-
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.3 -
Google search dark mode is available in some of my browser profiles but not others. A/B testing time again, I guess.4
-
When explaining unit testing:
"We tried but every time someone changes something in the database all the tests fail."
*facepalm*5 -
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. -
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 ? 😞3
-
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 ;)"2 -
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!1 -
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.1
-
When testing things..
Product Description: Expensive Imported Turkish Pen
Product Image: A bag of Snickers
The "asdfghsjgllhdk" text doesn't look very appealing. -
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. -
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.10 -
I read: "Don't change your implementation to do tests"
Then I read: "If it's too hard to test, your implementation is too complex"
Then we can get into test terminology itself, which is its own mess:
http://xunitpatterns.com/Mocks,%20F...
sheesh, if you thought the whole javascript / framework / web ecosystem always feels immature and behind other areas of software, i'm about to argue that testing patterns are even further behind8 -
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. -
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.
-
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
-
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.2
-
continuation of "testing is not needed" series
https://devrant.com/rants/4407958
a second former colleague (which works as backend dev) was seeking frontender, and remembered about the React frontender we both worked with.
I decided to warn him:
> *Giggles* According to his words, front is not like back. Git and testing aren't required there.
I received next replies:
> actually I don't need tests as well
> I did not write them all this time
> I have testers in a team for that, which do the testing for me
> I think I'll need it in cv though.
My comments:
I am trying to imagine their code... architecture, and I am a bit scarried to see how it looks like, are you?3 -
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?3
-
!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!3 -
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"2
-
Wrote another post on medium.
This one helps in automating the security token required for testing an API.
https://medium.com/@gvnix/... -
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.7
-
I hate it when you put a project into testing and the feedback tells you you've missed a reallybasic but important feature...
-
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 ever4 -
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.5 -
Guess I'm getting old (school) outputting foo, bar and baz for testing purpose. Does anyone still using those too?5
-
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.4 -
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.2 -
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.2 -
When you have a deadline to reach by EOD and your coworker spends the last hour of said day working on a side project instead of oh, I don’t know, TESTING. Sheesh.
-
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.3 -
The job description of my internship:
You must be able to understand the complexities of receiving a unit test that you are told needs only mock data in the test database, but has never worked since it was written by a contractor a year ago. No one knows how the unit test works and requires testing a complex algorithm involving graph theory that you have not learned about yet. The task starts at 1 complexity and turns into a 13. -
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?1
-
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.1 -
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...5 -
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
-
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?
-
Question for you web devs out there.
I'm curious as to what your workflow involves for building and multi device testing? Whether it be grunt/gulp / something else?25 -
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.5 -
Recently we've checked /sprint in HipChat to test batching of sprint status messages. For testing we wrote what first poped into our minds.
One Dev wrote /sprint We're on schedule
Another wrote /sprint Everything is broken, help
How different tests and first thoughts about progress sometimes can be?1 -
While hand-testing comment-posting functionality messed up the migrations and damaged local db. Had to recreate the whole set up (users, posts, etc) in order to resume the testing by hand.
Should've written the tests ;( -
Looking at jest errors and loads of GitHub and StackOverflow issues, it's no surprise that people claim they don't like testing.
Maybe they would if we got our tooling right.
import { foo } from 'bar';
Nah, that's an unexpected token, jest does not like this syntax.
Using require, like in jest's getting started tutorial isn't compatible with my existing JS libraries exports.
Adding type: "module" in package.json just makes another error message appear instead.
Fucking developer experience!
Why bother with unit tests at all?
How come PHP is 10 years superior to JS when it comes to code quality, unit tests, and static code analysis?
I don't even care about "ES modules". I don't want to "mock" anything either. All I want to do is import a handful of JavaScript functions into another file.
Overengineered web dev stack sucks!3 -
I swear I touched some weird and complex programming shit in over a decade of programming.
I interfaced myself through C# to C++ Firmware, I wrote Rfid antennas calibration and reading software with a crappy framework called OctaneSDK (seems easy until you have to know how radio signal math and ins and outs work to configure antennas for good performance), I wrote full blown, full stack enterprise web portals and applications.with most weird ass dbs since the era of JDBC, ODBC up to managed data access and entity framework, cloud documental databases and everything.
Please, please, please, PLEASE I BEG YOU, anyone, I don't even have the enough life force to pour into this, explain me why the hell Jest is still a thing in javascript testing.
I read on the site:
"Jest is a delightful JavaScript Testing Framework with a focus on simplicity."
Using jest doesn't feel any delightful and I can't see any spark of focus and simplicity in it.
I tried to configure it in an angular project and it's a clustefuck of your worst nightmares put togheter.
The amount of errors and problems and configurations I had to put up felt like setting up a clunky version of a rube goldberg's machine.
I had to uninstall karma/jasmine, creating config files floating around, configure project files and tell trough them to jest that he has to do path transformations because he can't read his own test files by itself and can't even read file dependencies and now it has a ton of errors importing dependencies.
Sure, it's focused on simplicity.
Moreover, the test are utter trash.
Hey launch this method and verify it's been launched 1 time.
Hey check if the page title is "x"
God, I hate js with passion since years, but every shit for js I put my hands on I always hope it will rehab its reputation to me, instead every fucking time it's worse than before. -
I'm currently working as a technical product manager. We lost a QE a while ago and I stepped into the ticket testing, happy path, and some exploratory testing for our tickets.
I had a friend from another company tell me to apply for a QE position. It's a combo product and QE position and I'm about 80% qualified.
Can anyone give me any places I can quickly and efficiently learn about setting up automated testing? I have some background in css, js, and html but basically no c# or other languages. -
Where should i go to get started with some sort of testing for my expressjs apps ?
I'm a complete testing noob1 -
Can someone explain tests to me? Maybe I'm a little behind but like, don't you test your code when you run it? Why do you have to write tests instead of just running the code you wrote and testing that?5
-
I want to run a theory by you regarding unit tests.
They make up for the time they cost to implement in the long run, no doubt, because when you're refactoring you can easily check whether you broke something.
But: what if you've got integration tests covering almost the entire codebase? For those to succeed the unit tests must succeed as well. So therefore imho the unit tests are redundant.
The only advantage of also having unit tests seems that they can pinpoint the issue more accurately.
Any other advantages? What am I missing? Any thoughts/comments?9 -
What are you suggestion/ advice for a newbie to TDD and testing in general?
Node.js developer if that matters.2 -
Hey
I m looking for a tool to record every click I make within chrome for short periods of time. Just so I can be sure I have clicked on the right elements while manually running complex scenarios.
Any recommendations ?4 -
TLDR: Wrote a custom class for writing apibtest cases for a project with zero code test coverage.
We have a project with zero test coverage. Recently, i was tasked with writing api test cases for said project, it might have taken me months to write tests for all endpoint, plus the main issue was that each endpoint needed to tested for all available user roles and permissions.
I tried the main stream approach of writing api tests, but ended up running into a lot of issues directly linked to our projects roles/permissions architecture (cherry on top some endpoint are apikey specific). Don't get me wrong in my opinion this is by far one of the best user roles architecture out there, but writing test cases keeping it in mind is pain in ***.
After trying out different testing methods and frameworks, i decided to write my own class by extending django test framework (which uses unitest)
- It has generator and validators for request and response.
- Supports testing for user roles and permissions.
- We won't have to make any changes to code after user role or permissions changes
- I just have to copy and past request and responses from postman api collection.😂
1 -
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?! -
Have some questions to testing.
Right now we are at the production end for first version. So far it was said to use Selenium IDE for Browser side testing, which was barely possible for the size of the website...
Is there other software or are there concepts I can read and inform myself to get into that point to teach myself properly?
The project is a business Website with Work flow system. Php backend and Database with a few procedures and zend framework for browser side.7 -
!rant
Finally managed to implement a proper E2E testing solution for our app with Protractor and Jasmine. Some basic tests (login and dashboard) are already working.
I'm just so happy to automate everything, going to cut down our manual testing time from 2h to about 20 to 30min if I'm estimating this correctly.
That's all. Just wanted to say I'm very happy with the results 😊5 -
So I'm testing a co-workers code and doing regression scenarios when suddenly it "loses" data in two fields after I save the data and go out/come back into the form. That's weird says I, lets have a look....
And I find the following conditional::
if (field empty) then failValidation("hey stoopid user")
else blank field value
Say what???
Happy Friyay everyone.... -
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. -
Haven't done much work on my game since December. Ok so I havent done anything on my game since December. Learned Mockito and JUnit formally (finally) because that's what we'll be using at work.
Never really learnt unit testing prior, just knew it's power. I just need to find the right unit testing and mocking frameworks that work well with .net, C# and Unity3D and I'll be great.
I'll finally attempt to properly test that (those) annoying part(s) of my game. So many vectors to work out and often the object is moved to or along the wrong vector.
I'd always only imagined having to use stubs which is why I've never understood how unit testing would really help in such a dynamic environment as video game development. Especially as a one man team. Mocking is about to be my lifesaver.
Anyone able to suggest a good testing and/or mocking framework for C#, .Net, Unity3D? -
Deploying a full test strategy across the company's range of php products because you haven't been scheduled to do anything else and the company has no automated testing after 10 years of functioning.
-
Hey, can someone point me to a sample project (if it exists) on the best way(s) to stucture code for Serverless architecture that includes GraphQL and unit testing?
Preferably in NodeJS. I'm more interested in the code structure than anything else. -
So after 8 months of stopping the development of a web app, the client decided to start pushing it for usage.
8 months ago I was almost begging him to do some testing, so I could gather some feedback and fix any issues. That, of course, never happened.
Yesterday just before leaving work I received a meeting invitation and an e-mail. Apparently the app wasn't at the "expected level given its development time". I also got another e-mail with change requests.
Someone will be getting some virtual middle fingers during the meeting... -
Twice now I've high leveled automated software testing to people not in tech and they actually get the benefits quicker than some tech managers.....
-
This is brilliant example of why integration testing is so much better than unit testing https://twitter.com/withzombies/...4
-
I start my new internship in a week. Its Java (springboot), angular, and the most popular testing tech for each. I know some of each, and no testing. PLS HALP. Want to impress.11
-
How the fuck do i make you this testing environment when I've been talking for three months that we don't have the hardware for it !!!
-
When PO lashes you to complete the project so they can begin testing as soon as possible, and you don't hear a word on the progress or get a single bug report because noone has the time to test it...
-
I am working on an event driven system that uses a message bus and has a few services that talk to each other asynchronously via the bus.
I'm writing in memory integration tests for one of those services, but I just realised the fundamental flaw here with such tests. I only have 1 application running, but I need several. This is quite a serious flaw I should have seen before.
Anyone else tried integration testing event driven distributed services? I imagine all I can do is stub the message broker...8 -
Anyone using nose2 as their primary unit testing framework?
If so, why do you prefer it over pytest? The nose2 homepage effective recommends pytest, so wondering about the future of nose2.2 -
Online resources that discuss testing recommend the following pattern when writing your unit test method names:
given[ExplainYourInput]When[WhatIsDone]Then[ExpectedResult]()
This makes developers write extremely long test method names.. and this is somehow the acceptable standard? There must be something better.. I think I've seen annotations being used instead of this.5 -
The heck is wrong with the testing framework. I can obviously see that it a correct value why doesn't the test case pass.
FAILED:
REQUIRE( positive==static_cast<double>(0.7352941176) )
with expansion:
0.7352941176 == 0.7352941176
===============================================================================
test cases: 1 | 1 failed
assertions: 1 | 1 failed10 -
Does anyone have experience with unit testing AutoCAD plugin applications? And || or UI testing?
Because you need a running AutoCAD application to test commands and functions it's very difficult to test the AutoCAD related methods.
I would like to know how you do it. -
I really don't know what to do when I can't get the help that we need.
We use the initial version of Jasmine for unit testing and AngularJS (not 2, 3, 4+, but 1), so it's hard to find any good examples online to create my tests. My coworkers help, but since testing isn't something we do at all (or at least very often), they are unsure on how to help me.
I don't know what to do. I feel very unproductive and not valuable to the company at this time.2 -
Today I've been summoned to work for the first time in weeks to help with the startup of a machine, and testing the HMI software that goes with it.
Me and a junior colleague go to the machine. We try to get everything ready for testing. Machine was left stuck in some intermediate state by someone else. I have no idea on how to control the machine's individual components. My colleague received a crash course a while ago, but was unable to reinitialize the damn thing, and the senior machine builder was too busy on another project.
In other words, me coming over had no purpose at all, and we accomplished nothing.
I really don't understand companies. On one end there's an endless bitching about how everything is too expensive, and on the flip-side you see 'em toss buckets of money through the window.
Oh well, as long as it goes from the window to my bank account, there's no problem for me I guess.2 -
When your 'responsive - multiples mta' email looks just fine while testing and just like sh**t once in the customer inbox, just like some nasty evil creaturr was smashing his face down all along the delivery.
-
I am starting a testing project at work and we have nothing in place.
Should I use a tool like browserstack and try to hold my selenium tests there or bite the bullet and use something like spec flow to write the selenium tests by hand? The advantage being full control, easy way to integrate with CI and easier to integrate to existing workflows (no need for visual studio and a browser open to work on in parallel).
If I do that I will also need some way to do cross browser testing which I guess will require me to export the tests somehow to a cross browser treating service like browserstack. -
What's a good way to learn proper testing? I'll be starting in a position before long that uses JUnit, karma, mocha, etc.1
-
Has anyone ever used Robolectric for testing their app?
I am unable to import Robolectric classes even after adding robopectric dependency.
Don't know what I'm missing.
Can someone help me out regarding this issue.2 -
When you change three lines in a PR with 100 changes that breaks the whole functionality, and it starts working flawlessly 😕 seems like testing PR before merge could have solved the doomsday
-
So well... 2 monitors are not enough for testing an server ha application with teaming/bounding interface with 3 nic.
-
Scammers are finally testing other content.
I don't recommend testing that QR code. Idk what it does.
3 -
I have to mock an API for my tests. The mocks got so complicated, I basically have cloned the API at this point. Now I'm testing my mocks to make sure they work. I'm essentially writing tests for my tests. There's gotta be a better way to do this.2
-
When you're working with a QA/test engineer that insists on manually testing code that have automated tests. Can any test engineera chime in here?
-
I just want to say that although LLMs are great and are truly moving tech forward, testing anything related to them has become a hassle. And that makes me fear the amount of ‘you are testing llms wrong’ articles in Medium that will come up in the upcoming months.1
-
Jest/enzym unit testing: My lead developer says using shallowWithStore instead of shallow on one incidence would introduce CPU overhead thus I MUST stop whatever I'm doing and fix the pull request. Is that normal?
-
What stack are you using to test your angular app and why?
We’re using Karma + Jasmine for writing unit tests, because it’s the default, and run them on GitLab CI in a Docker container. For UI testing we don’t use the default Protractor but Selenium, because we haven’t found a way to run Protractor tests with a dedicated webserver.1 -
Why is it acceptable for dev think it's ok to skip testing? WHY?
Today i was told that a co-worker had good enough judgment when it comes to CSS if it will break in other browsers other than chrome. I'd accept that if they knew the browsers inside out and read all the release docs but no, not them. Even more so when it's not their field of expertise.
After working for 2+ years at the some company, with a QA team, it's become evident no one does any proper testing, even the friking QA team!
I'm close to define the supported browsers as "What ever the developer used at the time of build".
Am I really the only Dev to test in at least 2 other browsers? -
I know it's an age old question, but how does everyone do their cross browser testing? Im looking for a way to automate this (ie. Browserstack)2
-
How would you create a mock for an Aggregator Microservice (stateless) which makes requests to other services for each request, transforms the data and then responds to the user?
I want to create a mock service where I don't t have to run the other services but it should create kinda realistic responses.
Have you had to create something like this?
I'd use it for testing another microservice that uses the aggregator.3 -
ISTQB tutorial (testing) with cold dead syntetic voice.... brain liquifying under unreleting bordom! KILL ME NOW!!!1
-
Hey Folks,
Does anyone use React Testing Library for Unit testing React components?
If yes, how do you imitate the user event "CTRL + B"? -
testing a form and having to fill in the info every single time I change the code - gross
Does anyone know of a way to refresh a form (ctrl+F5 in chrome) while keeping the data?6 -
For the old school gamers out there, today I realized that the method by which the Temporal Security Annex detects temporal disturbances in the game The Journeyman Project is, effectively, unit testing time itself.
-
I am integrating with different third-party payment provider via their API. Just wondering what is the good approach of testing these third party service/API?
Consumer/Producer contract testing?
end-to-end test?1 -
I got some problem. I work on some company maintaining web application. Every time I add some feature I often accidentally break other features. I read about testing (unit test, integration testing, etc) and ask my project manager and CTO to implement test on our web application but they refused it. The reason is because the web application is already large and it will take a long time to implement. Actually maintain this application is very stressful because it takes along time to add new feature and every time I break something either CEO or Client will scold me. Do you guys have idea/solution to solve this problem?1
-
Calling QA/ Test managers for help !
Im a junior dev at a company where im slowly transitioning into also being our test lead. I just got my ISTQB foundation and im starting to write out the test strategy for our company.
Currently we’r doing alot of reactice testing, and to implement more proactive testing i wanted to implement a risk strategy as well.
Problem is that i feel this strategy takes too much time for our organization (doing risk analysis for each story we’r implementing just isnt possivle) , and we don’t have time for me actinh as a full time Test manager while also doing software dev tasks.
Question is: what good proactive strategies can we implement that doesnt require too much time investment - or could we use risk strategy only for specific stories implemented / custom orders / etc and stick with a reactive strategy solely ?
Later this yesr ill be sent on ISTQB test manager course to better qualify my position but until then id really want to get a test strategy somewhat implemented
Any help is MUCH appriciated!10 -
Arrgh...
I need to do a lot of refactoring and testing (%80 percent of which is integration) and ITS SO TEDIOUS!!!
Now, for anyone who says "oh, you write spaghetti code, your code shouldn't be so tedious to refactor". No. It's only tedious because it's a few thousand lines that I've been too lazy to refactor till now, and I need to go through it all.
Anybody have any advice for refactoring or testing in Go?17 -
Mocha or Tape (both with supertest)? For Backend testing. Api, graphql, that shit.
What would you prefer and why?4 -
QA (Quality Assurance) software testing https://aimprosoft.com/services/... is a process of verifying and validating software products to ensure that they meet certain standards of quality. This process involves testing software applications for defects, bugs, and errors to ensure that they function as intended and meet the needs of end-users.
There are different types of QA software testing, including:
Functional Testing: This type of testing involves checking the functionality of the software to ensure that it performs as intended.
Performance Testing: This type of testing involves checking the performance of the software under various conditions to ensure that it meets performance requirements.
Security Testing: This type of testing involves checking the security of the software to ensure that it is free from vulnerabilities that could be exploited by attackers.
Usability Testing: This type of testing involves checking the user interface and user experience of the software to ensure that it is easy to use and meets the needs of end-users.
Compatibility Testing: This type of testing involves checking the compatibility of the software with different devices, operating systems, and browsers to ensure that it works as intended on different platforms.
Overall, QA software testing is an essential part of the software development process, as it helps to ensure that the software is of high quality and meets the needs of end-users.2
Top Tags
Weekly Rant
View