UnitTests
-
Kevin had to change some code: the information for an object had to be formatted differently. So he changed its ToString() method, replacing the previous implementation. That looks like the correct way.
After he check in his code, some UnitTests failed. "Those tests are not my tests" he said, and did not care.
Well, in his code, he does some calculations on properties of the object which may not be set at all, i.e. null. And that causes a NullReferenceException in such cases...
No, those UnitTests are not my tests...
And Bernie thinks: I am that bad guy who wrote the tests. I know that the ToString method gets called in a log statement somewhere in the system under test. Those tests worked with my codez, by the way...
-
@BernieTheBernie You could perhaps write a hook for test failure, which checks the commit logs and triggers an effect on the originating user, via some sort of software or hardware effector?
-
@Gribnit like a clue-by-four?
-
@AlexMedia said in UnitTests:
@Gribnit like a clue-by-four?
Idea for a product: every time a build fails, the system determines who caused the build to fail and pushes their chair slightly further from their desk. Once someone has caused enough build failures, they are unable to reach their computer anymore and must therefore stop breaking the build.
-
@ben_lubar said in UnitTests:
@AlexMedia said in UnitTests:
@Gribnit like a clue-by-four?
Idea for a product: every time a build fails, the system determines who caused the build to fail and pushes their chair slightly further from their desk. Once someone has caused enough build failures, they are unable to reach their computer anymore and must therefore stop breaking the build.
Already defeated by standing desks. However, slightly moving the chair while they are trying to sit down, increasing that delta each time, could eventually have a useful effect. Probably wouldn't want to do it every time, though, need to trigger a reverse-gambler's-reward and all.
-
@ben_lubar said in UnitTests:
@AlexMedia said in UnitTests:
@Gribnit like a clue-by-four?
Idea for a product: every time a build fails, the system determines who caused the build to fail and pushes their chair slightly further from their desk. Once someone has caused enough build failures, they are unable to reach their computer anymore and must therefore stop breaking the build.
Already defeated by standing desks. However, slightly moving the chair while they are trying to sit down, increasing that delta each time, could eventually have a useful effect. Probably wouldn't want to do it every time, though, need to trigger a reverse-gambler's-reward and all.
I was imagining a big wall that comes out from under the desk preventing the person from getting too close.
-
Already defeated by standing desks.
I dunno. The motorized ones could be easily integrated and could give everything on the desk a good hard drop.
-
@heterodox This thread is making me imagine how you could incorporate robotics and sensors into everything to create some sort of dystopic house where everything is machine-controlled and plotting against you.
You could charge sci-fi enthusiasts to live there for a while.
-
@anonymous234 said in UnitTests:
@heterodox This thread is making me imagine how you could incorporate robotics and sensors into everything to create some sort of dystopic house where everything is machine-controlled and plotting against you.
-
Already defeated by standing desks.
Then just raise the desk by a millimetre or so every time a punishment is due.
-
IT_BUILD_BROKEN_MON
-
@anonymous234 said in UnitTests:
@heterodox This thread is making me imagine how you could incorporate robotics and sensors into everything to create some sort of dystopic house where everything is machine-controlled and plotting against you.
You could charge sci-fi enthusiasts to live there for a while.
We already have a thread about that
https://what.thedailywtf.com/topic/21150/internet-of-shit/1057
