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
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuck
Buy Now
-
My girlfriend doesn't talk to me anymore after I said I helped the new girl to do some penetration testing.27
-
You think your job sucks?
Well, I spend more than six hours everyday testing a million dollar super ugly product on Internet Explorer on Windows.
And when I raise bugs, the devs just bash me up for fucking their code.
Who is the real culprit here, eh?
Now beat that bitch.28 -
Testivus On Test Coverage
Early one morning, a programmer asked the great master:
“I am ready to write some unit tests. What code coverage should I aim for?”
The great master replied:
“Don’t worry about coverage, just write some good tests.”
The programmer smiled, bowed, and left.
...
Later that day, a second programmer asked the same question.
The great master pointed at a pot of boiling water and said:
“How many grains of rice should I put in that pot?”
The programmer, looking puzzled, replied:
“How can I possibly tell you? It depends on how many people you need to feed, how hungry they are, what other food you are serving, how much rice you have available, and so on.”
“Exactly,” said the great master.
The second programmer smiled, bowed, and left.
...
Toward the end of the day, a third programmer came and asked the same question about code coverage.
“Eighty percent and no less!” Replied the master in a stern voice, pounding his fist on the table.
The third programmer smiled, bowed, and left.
...
After this last reply, a young apprentice approached the great master:
“Great master, today I overheard you answer the same question about code coverage with three different answers. Why?”
The great master stood up from his chair:
“Come get some fresh tea with me and let’s talk about it.”
After they filled their cups with smoking hot green tea, the great master began to answer:
“The first programmer is new and just getting started with testing. Right now he has a lot of code and no tests. He has a long way to go; focusing on code coverage at this time would be depressing and quite useless. He’s better off just getting used to writing and running some tests. He can worry about coverage later.”
“The second programmer, on the other hand, is quite experience both at programming and testing. When I replied by asking her how many grains of rice I should put in a pot, I helped her realize that the amount of testing necessary depends on a number of factors, and she knows those factors better than I do – it’s her code after all. There is no single, simple, answer, and she’s smart enough to handle the truth and work with that.”
“I see,” said the young apprentice, “but if there is no single simple answer, then why did you answer the third programmer ‘Eighty percent and no less’?”
The great master laughed so hard and loud that his belly, evidence that he drank more than just green tea, flopped up and down.
“The third programmer wants only simple answers – even when there are no simple answers … and then does not follow them anyway.”
The young apprentice and the grizzled great master finished drinking their tea in contemplative silence.
Found on stack overflow https://stackoverflow.com/questions...8 -
A more experienced friend told me
"don't be a pussy, test in production"
I'm the one fixing the bugs, not him
8 -
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 .
8 -
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... 😂15 -
Dev manager: great news guys. We’ve built a new tool to do automated testing on apps. We’ve gotten rid of the old Appium solution we were using and built this new one.
Me: why not just use the inbuilt native stuff? Click to record works really well.
Manager: nah we thought it would be more flexible to build it ourself.
Me: ... ok ... moving on ... how does it work?
Manager: well this new .jar, you download it, pass in a config file, setup up your simulator and appium and the jar will do everything for you.
Me: ... wait you said you hate Appium? Now you’ve built a wrapper around it? And it doesn’t even set everything up, you’ve to do it all by hand?
Manager: oh we had too, would be too much effort to replace it. Don’t worry we can now write all our tests in .yaml config files instead of using Appium.
Me: so we’ve lost the ability of auto-complete and type ahead, everyone has to upskill on a new tool, it offers no new features over what’s available out of the box and we’ll have to deal with new bugs and maintenance and stuff our self ... because we need more flexibility?
Manager: oh don’t worry. The guy who built it is staying here. He’s going to deal with bug fixes and add features. He’s only one guy, but he’s really sharp, it’ll be great for us and the team.
Me: ... ... ...
*audible noise of soul breaking*
Me: ... ok thank you. I’ll look into this new tool3 -
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.7 -
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 -
So just about to head to the pub and I got the dreaded call from my boss.
The support team had developed some fixes. They "tested" and deployed without letting us know... And you guessed it there was failures all over the shop!
So it turned out their testing was running on a local base install with no integration compared to the live system with 15 years of customisation and complex integration. My they thought this was acceptable I don't know...
And the best part was the developers who made the changes didn't understand their own code (I found the tutorial they copied online) they just blindly copied it without understanding how it worked!
So 4 hours later we found the bug, nothing like having a query and s SQL connection but not executing the query....
There goes my Saturday evening. Now we're was my beer!7 -
A few days after deploying a big important Website into production, I wanted to copy the whole thing including DB back onto our test server for future testing/bug fixing if something comes up. (Last changes were done on production server before going live)
So I opened SSH, removed everything on the test sever aaaaand then I realized I was connected to production...
Took about an hour to get everything up and running again. We didn't tell the client and hoped it would not be noticed.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 -
You know why I post such screenshot demeaning companies with respect to their application or service or functionality?
Because, as a tester, it pisses me off how these assholes undermine us, our ability and our work towards building a better product.
Fuck such people who think testing is stupid in software world and isn't important at all.
#TesterLivesMatters
#PostedOneDayAgo, #Applied48YearsAgo
5 -
As you all know, I test a multi-million dollar product on Internet Explorer running on Windows 7.
Today, I have been assigned a performance testing task.
There are 20+ tabs open on Internet Explorer which takes eternity to load and if a tab is switched the entire page loads all over again.
You talk about having a hard day, eh?
I have been struggling since morning to complete one vanilla flow. SHIT JUST DOESN'T WORK.
FUCK MY FUCKING LIFE.4 -
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 -
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 -
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.
4 -
"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 -
After 10 years of development, and 7 years of being happily married, I'm in love again... With Unit Testing.
-
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 -
Me currently listing to the dev team what the fuck is going wrong with their website after testing it
1 -
"I'm almost done, I'll just need to add tests!"
Booom! You did it, that was a nuke going off in my head.
No, you shouldn't just need to add tests. The tests should have been written from the get go! You most likely won't cover all the cases. You won't know if adding the tests will break your feature, as you had none, as you refactor your untested mess in order to make your code testable.
When reading your mess of a test case and the painful mocking process you went through, I silently cry out into the void: "Why oh why!? All of this suffering could have been avoided!"
Since most of the time, your mocking pain boils down to not understanding what your "unit" in your "unit test" should be.
So let it be said:
- If you want to build a parser for an XML file, then just write a function / class whose *only* purpose is: parse the XML file, return a value object. That's it. Nothing more, nothing less.
- If you want to build a parser for an XML file, it MUST NOT: download a zip, extract that zip, merge all those files to one big file, parse that big file, talk to some other random APIs as a side-effect, and then return a value object.
Because then you suddenly have to mock away a http service and deal with zip files in your test cases.
The http util of your programming language will most likely work. Your unzip library will most likely work. So just assume it working. There are valid use cases where you want to make sure you acutally send a request and get a response, yet I am talking unit test here only.
In the scope of a class, keep the public methods to a reasonable minimum. As for each public method you shall at least create one test case. If you ever have the feeling "I want to test that private method" replace that statement in your head with: "I should extract that functionality to a new class where that method public. I then can create a unit test case a for that." That new service then becomes a dependency in your current service. Problem solved.
Also, mocking away dependencies should a simple process. If your mocking process fills half the screen, your test setup is overly complicated and your class is doing too much.
That's why I currently dig functional programming so much. When you build pure functions without side effects, unit tests are easy to write. Yet you can apply pure functions to OOP as well (to a degree). Embrace immutability.
Sidenote:
It's really not helpful that a lot of developers don't understand the difference between unit, functional acceptance, integration testing. Then they wonder why they can't test something easily, write overly complex test cases, until someone points out to them: No, in the scope of unit tests, we don't need to test our persistance layer. We just assume that it works. We should only test our businsess logic. You know: "Assuming that I get that response from the database, I expect that to happen." You don't need a test db, make a real query against that, in order to test that. (That still is a valid thing to do. Yet not in the scope of unit tests.)9 -
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 -
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 -
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 -
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...
-
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. :D9 -
Greatest dev sin.... oh god there’s been a few over the years.
Hmm 🤔
I guess one of the top 5 would be making an ecommerce platform without unit testing or documentation for the front or backend. 🤫
Mind you it runs smoothly to this day so I was doing something right 😦1 -
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 -
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. -
Not sure if it was 2016 or late 2015, but it's a fun story anyway (and if it's not you'll at least learn something from it).
Back at the time I was quite new to unit testing (weird how it has become second nature in a years time). I was writing some software that was supposed to send out some SMS to customers. Of course this had to be tested. However, it was a bit difficult to test (or so I thought) without actually receiving an SMS to know if it was sent. So I decided to use the live API key to make sure the sending of SMS was actually working correctly. I tried it a few times but didn't receive an SMS. So I kept working on it and running tests.
The testing setup I had at the time was just a continues loop that went through all tests to make sure it all still worked (I've moved to only checking on file changes now, but that is besides the point). Keep in mind I was still running these tests, in a loop, with the _live_ API key.
So the end of the working day arrives and I go home and sit in the train. All of the sudden I receive some test SMS. I was thinking "hey nice, it did work". Then I started receiving more. It soon turned out to be an alarmingly big amount of SMS. It stopped around 100, but don't think that was the end of it. Oh no. I had changed the number to send the SMS to from my own number to a different number (+31612345678 to be exact, which I found out later isn't an actual phone number. I really hope I was right about that). I was beginning to become nervous, but there wasn't much I could do.
The next day I returned to work and checked the API for sent SMS. Turns out I had sent a couple of thousand (I think between two and three thousand) SMS in a couple of hours. Most of them to the test number I had supplied.
This probably cost the company a couple of hundred euros. Luckily my colleagues and team leader all thought it was pretty funny, but did tell me not to do it again. And I haven't of course.
Lesson learned: don't use live API keys during testing (among other things :)).
So yeah that was probably my worst dev experience.1 -
I assigned a new task to an intern who has been with us for a month. He was supposed to prepare the testing environment and test the Geolocation API. When it works, then he can start integrating it with our platform and everything.
After a week, he emails me to say that he thinks the Geolocation API doesn't work. I was weirded out by that because a lot of people use it. We scheduled a meeting and asked him for a demo of his code to see what the error message is.
Him: *no Visual Studio, no code, nothing at all* So here it goes.
Me: ????
Him: *Goes to the API documentation, copies the base URL, pastes it to the browser and hits Enter* See? It says 404 not found.
Me: *literally facepalmed*
Now, he is working on sales management. We totally took him off every software developing projects.8 -
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. !!!7 -
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?6 -
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. -
When your product owner tells you to forget about architecture and unit testing, "just push it out"...
2 -
Fucking first rant here:
So we tried to teach Two new colleagues to typescript and git and testing and stuff and we have a SPOC “which claimed to be very technical”. The SPOC’s task is to keep an eye on the work, and today we have had a review...
After two weeks, the created multiple branches into our git, all with one commit of 400 LOC changed, no merge requestet, issue in Redmine set to “closed”.
Well, by the way they were supposed to write Unit tests for our app.
But I thought, ok, we’ll check their branches.
Their tests all passed (cz) but man, the app didn’t and on compilation there were errors, the app is broken. Damn.
Is it really so far off, that even of They wrote tests, that the app should still work?
AND I THOUGHT IT IS COMMON SENSE. Damn!
Guess how needs to fix it6 -
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 -
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 -
Time for one of those eye-rolling super vague general question threads 🙃 How do you find edge cases when you're testing your code?
Reason I'm asking is I'll spend AGES testing something I've built, then it goes in for review and IMMEDIATELY the person reviewing it finds some daft edge case I would have never thought to look for.
Current theory is that I'm testing it too much from a developer's perspective (does this request get issued, does localStorage get updated, etc etc) and not enough from a user's perspective (what does this button do) but even then these edge cases keep popping up and it's really annoying 🙃
Who's got some insights?6 -
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
-
Tonight was the regionals of CPTC, a relatively new competition about penetration testing. Here's our master plan, dont tell anyone ;)
5 -
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 -
Fuck you, code coverage tests, for failing on two input fields in an array, while recognizing the other two in the same array. Fuck you, I fetched all of the fields.
-
Dear CTO who approved his own code changes without testing or review,
Why do you hate my master branch? What has my master branch done to you? Did you have to break it?3 -
Testing had some issues with system integration. I asked them what their setup was.
Answer: "Almost similar to the real hardware."
LMAO!2 -
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 -
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 -
It's a twisted feeling when your team decides to fix up their unit tests and not just mock everything. Yay, because it's now done correctly. "Are you fucking kidding me?!" when you realize that that means you now have to add tons of new instances of classes that the main one now needs, now that it's no longer mocked. 😑😐🙃2
-
I would describe the test project i inherited as a watermelon test suite,
Green on the outside..............................
Red on the inside -
This week at work I spent 20 hours debugging automated tests to avoid manual testing that would've taken a few hours.5
-
I just wrote unit tests for like the first time in my life (didn't find it useful in university, someone else handing in the project always did that). It cut my coding time by a factor of 3! You should try this one if haven't already, it really saved me a lot of headache right now.3
-
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 -
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 -
"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/... -
TLDR: fuck this plugin.
Longer version: I recently had to implement an external Vue plugin to upload files. That gave me a good headache already, mostly due to the half Chinese, half Google Translate English documentation. I now found out that testing the implemented component may be impossible. Turns out it overwrites the $route and $router variables and makes them read-only. Which won't even let me create a shallow mount of my implementation. Fuck this shit, I'm getting a drink!4 -
Quick question:
Anyone here has any apps that they want to get tested for vulnerabilities and stuff?
I am training for job in it-security field but it's hard to find a starting point for testing a real app/site/whatever
So I would like to test some stuff you guys make, just for fun8 -
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. -
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
-
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! -
Since my ISP doesn't allow port forwards on that port, does anyone want to open their port 445 (if not otherwise occupied by Microsoft-DS) and have netcat reply an empty string or so any request (such as an empty string) sent over TCP (or has anyone already done so)? It would help me out a lot with testing out some networks full port range (since portquiz.net's hoster blocks that port) and would take close to no bandwidth for you.6
-
So I'm trying out docker and see how I can make use of it, current setup:
1. Ubuntu on VM and Mac for Asp.Net core development
2. Windiws for MS only stuff like SQL Server
3. Ubuntu Server on VM and is running docker images: MS image for SQL and Ms image for dinner core.
What I did so far one script which will handle updating SQL Server database on windows with the changes done on docker SQL image
Then publish website from Mac or Ubuntu to docker image. I have yet to find a way to execute scripts remotely on a docker image using bash script from a remote
What should I do next? And for home setup go for Ubuntu server or CentOS? Any recommended packages for server administration? Workflow ..etc.?
2 -
Nothing destroys an ego quite like the cold, ruthless testing of your software by the QA team. I humble once more.
-
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
-
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 -
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 :(5 -
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 -
Full round of QA, full round of internal testing, and the client still finds a bug nobody can reproduce.
🤷🏻♀️🤷🏻♀️🤷🏻♀️1 -
Do you test your codes while coding or after completion?
I test while coding.
PS:- I'm web developer.17 -
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'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 -
How many people do unit testing?. Am always caught my deadline. I just fix errors in production. The client timeline are not feasible3
-
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
-
Are there people here who actually unit/integration/end-to-end/stress test (almost) everything? Or is it a common fact that nobody has time/budget and/or needs to do so?
I like to think I test all the code I write, but to be honest, I think it's closer to 1 to 5%5 -
The moment when client test team rejects a fix as it "doesn't work" when it's clear they haven't read the documentation 😂2
-
Last year for company I work I made OAuth server + SSO discriminated by business unit in php. Well it was quite complex project and security sensitive, so I wrote tests for every piece of code. Then I made client for it with abstractions to be easily extendable, but was too lazy write tests for it.
Anyway, today needed to add new grant auth strategy. Thought, I could also write tests for the client this time. That was the mistake...
I installed codeception (testing framework), tested every class, and then left the main client class for the end where all http communication and other magic happens.
So turns out, I can’t capture function parameters with codeception (at least its not documented), so I can’t assert if data in the end is correct. I mean it’s fucking abstraction on top of phpunit, which can do that, so what the fuck? But ok I probably could just use phpunit, but anyway why the fuck you would create mock abstraction with only 20% of functionality from original implementation? It doesn’t make fucking sense...
In addition, I was testing code written with guzzle http (http client), and that is some pile of shit. Just why the fuck I need to write 20 lines of code just to get a fucking json response...
Fuck this shit, I am not going to test it anymore, it just makes me hate php, I barely can deal with all that angryness inside me. -
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 -
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.11
-
When testing things..
Product Description: Expensive Imported Turkish Pen
Product Image: A bag of Snickers
The "asdfghsjgllhdk" text doesn't look very appealing. -
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. -
One of the founders of my startup does not write tests....
Me: we have to all write tests. I explain unit tests, integration, etc.
Him: I do... I have a test that checks if the app crashes or not.
Me: that is not what I meant (writes test because he won’t) 🙄1 -
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. -
When explaining unit testing:
"We tried but every time someone changes something in the database all the tests fail."
*facepalm*5 -
My company never used unit tests. And i would love to educate but i do not know how to unit test properly. I always en up with: if i want to properly test all ins and outs of this class's + operator. I need to add checks for positive number, negative numbers, nan, infinites, nulls etc. Etc. It needs so many tests for something so stupidly simple, that i don't see a way to motivate people to use it.
Am i missing something? Is there a guideline for "ok coverage"? Is testing just that much work and is that why nobody cares until it is too late?
I have been reading a book about working with legacy code. But still i got no answers. Halp!7 -
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)7 -
Wrote another post on medium.
This one helps in automating the security token required for testing an API.
https://medium.com/@gvnix/... -
Has anyone else actually *used* mutation testing at all?
Heard a lot about it recently - it seems all the rage amongst the bloggers, but I'm generally always very sceptical of things touted as the "latest hotness" (my thoughts on blockchain for instance are well known.)
So I went ahead and whacked http://pitest.org/ into one of my more recent pet projects to see if it offered anything decent. Surprisingly, it did - in particular it caught a number of places where switching "<" for "<=" and similar had no affect on the pass / fail rate (indicating the tests should be better.) There were a *few* false positives, and some which were borderline useful, but as a whole I'd say it was a worthwhile addition.
Curious as to if anyone else has had the same experience?1 -
This week the QA is on vacation, so we, the developers, are testing our own code (I test my partner's code and he tests mine).
For those who are QA, I have a question: If our boss omitted something on the description of how the code has to be made, for example, filtering data from database, and one of those filters are needed but the boss forgot to tell us and, at the time of making the tests, the QA and de dev team notice this... the change that has to be made should be marked as a bug? or how would you mark it?1 -
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 ? 😞3
-
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.
-
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
-
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 -
Guess I'm getting old (school) outputting foo, bar and baz for testing purpose. Does anyone still using those too?5
-
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 -
!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 -
!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 -
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
-
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
-
After three months of development, my first contribution to the client is going live on their servers in less than 12 hours. And let me say, I shall never again be doing that much programming in one go, because the last week and a half has been a nightmare... Where to begin...
So last Monday, my code passed to our testing servers, for QA to review and give its seal of approval. But the server was acting up and wouldn't let us do much, giving us tons of timeouts and other errors, so we reported it to the sysadmin and had to put off the testing.
Now that's all fine and dandy, but last Wednesday we had to prepare the release for 4 days of regression testing on our staging servers, which meant that by Wednesday night the code had to be greenlight by QA. Tuesday the sysadmin was unable to check the problem on our testing servers, so we had to wait to Wednesday.
Wednesday comes along, I'm patching a couple things I saw, and around lunch time we deploy to the testing servers. I launch our fancy new Postman tests which pass in local, and I get a bunch of errors. Partially my codes fault, partially the testing env manipulating server responses and systems failing.
Fifteen minutes before I leave work on the day we have to leave everything ready to pass to staging, I find another bug, which is not really something I can ignore. My typing skills go to work as I'm hammering line after line of code out, trying to get it finished so we can deploy and test when I get home. Done just in time to catch the bus home...
So I get home. Run the tests. Still a couple failures due to the bug I tried to resolve. We ask for an extension till the following morning, thus delaying our deployment to staging. Eight hours later, at 1AM, after working a full 8 hours before, I push my code and leave it ready for deployment the following morning. Finally, everything works and we can get our code up to staging. Tests had to be modified to accommodate the shitty testing environment, but I'm happy that we're finally done there.
Staging server shits itself for half a day, so we end up doing regression tests a full day late, without a change in date for our upload to production (yay...).
We get to staging, I run my tests, all green, all working, so happy. I keep on working on other stuff, and the day that we were slated to upload to production, my coworkers find that throughout the development (which included a huge migration), code was removed which should not have. Team panics. Everyone is reviewing my commits (over a hundred commits) trying to see what we're missing that is required (especially legal requirements). Upload to production is delayed one day because of this. Ended up being one class missing, and a couple lines of code, which is my bad (but seriously, not bad considering I'm a Junior who was handed this project as his first task at his first job).
I swear to God, from here on out, one feature per branch and merge request. Never again shall I let this happen. I don't even know why it was allowed to happen, it breaks our branch policies. But ohel... I will now personally oppose crap like this too...
Now if you'll excuse me... I'm going to be highly unproductive and rest, because I might start balding otherwise after these weeks... -
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 -
Is there an alternative to katoolin? Aka a tool for installing all Kali pen-testing tools on other distros.
Katoolin hasn't been updated in a year or so and I can't get it to work. If you want to know why I'm not just using Kali/Parrot/any other pen testing OS, read my last post and please take my advice.
5 -
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 -
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
-
I hate it when you put a project into testing and the feedback tells you you've missed a reallybasic but important feature...
-
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
-
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 -
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 -
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.... -
Sometimes, certain features don't work in my app if it's uploaded to the production track in Google Play.
It works in debug mode.
It works in release mode.
It works in the internal testing track.
...but it won't work in the production track? Y'know, the one that actually matters? Theoretically, there shouldn't really be a difference if the same exact APK was uploaded to the internal testing and production track, but... idk dude.
As a result, I implemented a secret way to test a feature in the production build (it's an app to remotely control OBS Studio): if the first connection you added is named "yayeet_" and you open the disclaimer, it tests the feature. Luckily, I got some of the stuff figured out, but I just thought the way I had to test it in production was dumb.1 -
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
-
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 -
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
-
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 -
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. -
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?! -
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.
-
Where should i go to get started with some sort of testing for my expressjs apps ?
I'm a complete testing noob1 -
In a sprint planning meeting. Getting frustrated. I guess it's my fault. I guess I assumed that attending the same schedule meeting each week meant that we all knew when everything was due. My bad.
Seriously, I fucking hate systems people sometimes. We have 4 major tasks coming down the pipe, but they are scheduled in such a way in which they are staggered. But they want to punt the 1 of the 4 that is fucking done because it is going to cause a lot of testing, but the other three aren't coming til end of next month AT LEAST. So they want to stick their thumbs up their ass holes and wait to test the other three before testing the one that, again, IS FUCKING DONE!!! Are they worried that a super massive black hole will spontaneously form in earth's orbit and cause time to run backwards and somehow cause December to happen in October!?!?
No wonder systems is so fucking far behind. They can't see the forest for the trees. They're so big picture that months and years are at the same level of granularity. Fucking hell how is scrum better than our current agile process again? Besides the fact that it makes me attend more useless meetings and get more angry.
They are punishing the left hand for the actions of the right. Systems wasn't doing their job so now software has to slow down and miss schedule.2 -
Personal Challenge of the day:
Write an entire complex react component (think a form with internal dialogs and cross component functionality) without testing once. Attempt to build the entire piece with all functionality without looking at the screen.
Ive been doing these little personal challenges with front end and backend assignments.
Ive noticed the difference its made in my daily work as I grow less dependent on the time consuming habit of checking browser/terminal feedback in order to determine what to do next.
With that I know people enjoy test driven development now days and thats a different story entirely. Not something I enjoy at all but I have no faults with the concept. -
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?
-
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 -
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 -
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. -
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. -
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 ;( -
Unit testing with NSubstitute and Autofac
For the most part, I find it a lot simpler than SimpleInject (hmm) and Moq, which I have used previously.
But there are still some of those 'Oh, for fucks sake!'-gotchas.
I was trying to test a class today where I wanted to substitute all other methods in the class than the one I wanted to test == an actual unit test.
I had previously found out how to do this:
1. Make sure the methods that should be substituted are internal to allow substitution.
2. Substitute class with Substitute.ForPartsOf<T>(args)
3. Set up methods that should not be called with instance.When(a => a.Method()).DoNotCallBase()
This way, you can unit test a class properly and only call the method that you want to test, and also control the return values of the other methods if needed.
So as I said, I have used this before to great effect. But today I just could NOT get it to work! I checked and rechecked everything but the test code kept calling the implementations of the substituted methods!
I even called over another dev for help, but he couldn't see the problem either.
Aargh!
I scoured the internet, but everyone just told me what I already knew: follow the 3 steps, and all is well. Not so!
I ALMOST considered doing the test improperly, as in, increasing the scope beyond that of the method I wanted to test.
But then it hit me... My project was missing this line in AssemblyInfo.cs:
[assembly: InternalsVisibleTo("DynamicProxyGenAssembly2")]
I always add a line to make internals visible to the test project, but I had forgotten that NSubstitute needs this line as well to work properly.
Sometimes when a test fails it will tell you that you are missing this line. And sometimes it just doesn't work.
Maybe I will remember this in the future now. Maybe 😅 -
Junior developer says TTDI is tedious and a waste of time. One day he fixed a bug and produced 5 new bugs in the system.1
-
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? -
Some programmer or QA person somewhere in the world is having a moment of great reflection on the subject of thoroughly testing their code. If not that, then on the subject of a super crappy manager who knew better and pushed to production anyway.
“Then in September this year, nearly three years later, he got a letter from Wells Fargo. "Dear Jose Aguilar," it read, "We made a mistake… we're sorry." It said the decision on his loan modification was based "on a faulty calculation" and his loan "should have been" approved.
"It's just like, 'Are you serious? Are you kidding me?' Like they destroyed my kids' life and my life, and now you want me to – 'We're sorry?'"
https://cbsnews.com/news/... -
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.
-
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...
-
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... -
What are you suggestion/ advice for a newbie to TDD and testing in general?
Node.js developer if that matters.3 -
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 -
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 -
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 -
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 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. -
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
-
Alright, I'm gonna need some help from more experienced devs.
tldr: how does my sister test my website if she can't run it?
I'm making a site (for myself, I've talked about this in other rants, most likely won't go online so I don't want to spend money on this), and my sister is helping me with the sales part of the project. It's basicaly a web store.
In a couple of months, she is going to have a baby, and will stay at home for 5 months. Since she helped me with it, and I don't really know all of the steps that go into online purchasing (she kind of works with this, and makes a lot of online purchases, from everyone I know she was the best person to go to), we want her to test it while she's at home with the baby, just in case I missed or didn't understand something.
The problem is: she doesn't understant anything about programing and probably never seen a command line, and since this is laravel, I will need to install a lot of things in her computer, which will be useless for her after she is done, and teach her some commands to run the site.
Also, like I said, i don't want to spend money on this, since she will only make a few tests and that's it, it would go offline after.
She is smart, she could probably do this, so if there is no way of doing this is ok, but if there is it would save her a lot of time while testing and with the baby, and save me my time at work.
I would want something like git, but where I could run the site without a lot of steps.
Does anyone know how she can test it? Is there even a way?
Thank you in advance 😁6 -
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.....
-
Why the hell you write test¿ if you can write 8h a day perfect working code, everyday, without a mistake?
You just waste time doing that...
</irony> -
Anyone with Q/A or Testing background who want to share his history or give some recommendation to start with that?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
-
I'll do the tests later on it'll be fine. 3 releases on, There are bugs everywhere - I cannot handle the regressions. Why'd this happen..Yeah.. Really need to do some proper TDD at some point.
-
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
-
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 !!!
-
Me, week 2 at new job, meeting with a separate team of fellow Python users: "Hey what software tests do you have for this? I am interested to learn your testing structure."
Dev1: "We don't really have any."
Dev2: "I have a Ruby script that tests this one thing."
Dev3: "why did you do it in Ruby? Why not Python?"
Dev2: "oh well Dev4 started in Ruby."
Me: 😅
Me: *this is going to blow up but I am too new to tell them what to do*
Last week, these guys messed up 500 files in production with "undefined" in the filenames. 😣 I think it's time to introduce them to tests...1 -
This is brilliant example of why integration testing is so much better than unit testing https://twitter.com/withzombies/...4
-
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.
-
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?
-
!rant, question
Hi, as a developer turned tester I was wondering if anyone here would hear a talk about what on earth testers actually do in a project and how they contribute to the product? I mean besides writing automation scripts or checking if all the requirements are met (the latter is really the most boring part of testing).
I am thinking of doing a talk on this but don't know if Devs might be interested and which conferences I should target.2 -
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. -
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? -
Management wants me to write e2e tests instead of unit tests. The problem is there are e2e but not a single unit test... I plan on refusing.
-
ISTQB tutorial (testing) with cold dead syntetic voice.... brain liquifying under unreleting bordom! KILL ME NOW!!!1
-
So well... 2 monitors are not enough for testing an server ha application with teaming/bounding interface with 3 nic.
-
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
-
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 -
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?
-
It's time to see what I can do
To test the limits and break through
No right, no wrong, no rules for me,
I'm free!
Test-Driven Frozen -
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.
Top Tags
Weekly Rant
View