7 ms·
Many eons ago...Around 10 to 15 years ago...Seen a similar serialization and date processing bug with a Java based Enterprise Integration Platform used by some
by belter 5y ago
Many eons ago...Around 10 to 15 years ago...Seen a similar serialization and date processing bug with a Java based Enterprise Integration Platform used by some of the largest companies in the world.
Several European Central Banks were unable to process transactions ;-). Can't provide more details, to protect the innocent. Since then, it has been a standard within the Testing group of that vendor to always have a running platform setup with a date 6 months ahead ( clock sync from a different source ). Something I added to my own Software Engineering and Testing standard practices.
- karmakaze 5y agoI came to ask if anyone was aware of systems that automate tests of dates in the future to find it already answered. > Something I added to my own Software Engineering and Testing standard practices. Noted.
- trembonator 5y agoCmon, it’s Microsoft! You shouldn’t need to do that!
- jrootabega 5y agoAgreed. Microsoft should be doing that already.
- hughrr 5y agoIsn’t this basically fuzzing? Making sure it works at the business domain level is another thing entirely.
- matsemann 5y agoNot exactly fuzzing, no. Most tests are written with a fixed date, or now(). Instead, using now()+delta can help discover future bugs and give you some time to remedy the issue. Often annoying to write tests like that, though, without them breaking for unrelated/timing issues compared to a fixed value.
- fragmede 5y agonot especially. Fuzzing would be running the software with an API to test all of the possible dates.
- jacquesm 5y agoNo, that's exhaustive testing. This is fuzzing: https://en.wikipedia.org/wiki/Fuzzing https://en.wikipedia.org/wiki/Fuzzing
- azernik 5y agoA date 6 months in the future is not invalid or off; it is a normal input that the program is expected to receive in the future. Fuzzing would be testing the date parser by passing it '25-44-2021' to see what breaks.
- jacquesm 5y agoIndeed. But you probably meant to address the parent, rather than my comment.
- azernik 5y agoBlerp
- pimlottc 5y agoFuzzing inputs don’t necessarily have to be invalid, just dynamically generated in order to probe program states not normally exercised by manually generated test data. Per Wikipedia: “providing invalid, unexpected or random data as inputs”
- hughrr 5y agoExactly my original point. Invalid input is invalid input
- 5y ago
- chmod600 5y agoIf you expect your software to exist in 6 months, then the input is entirely expected, and therefore not fuzzing. It's a nice early-warning system for Y2K or Y2038-like problems.
- game_the0ry 5y agoA couple of years ago, I did work for a major airline where the test suites that would test date processing would fail on every leap year (Feb 29). So they decided not to run tests or deploy on Feb 29th.
- jlkuester7 5y agoLol, reminds me of of the large EMR platform I used to work on that (until very recently) could not handle the "fall back" DST event (thanks to local date encoding in very parts of the system).... So the recommended 'fix' for hospitals was to just turn it off (their entire electronic health record) for the duration of the DST changeover... I personally believe that a non-trivial amount of people die due to DST and similar time related bugs...
- mark-r 5y agoDST has long overstayed its usefulness. I wonder why it's so hard to get rid of?
- curiousllama 5y agoOh, EMR systems kill patients all the time. Like, I’m not convinced “turn it off” isn’t an improvement.
- mr_toad 5y agoPoor record keeping practices in general have been linked to killing patients. Especially ones involving medication errors. It’s not like paper systems were perfect or even demonstrably better.
- game_the0ry 5y agoI hesitate to find it amusing that healthcare software is so busted that we laugh off the negative, fatal consequences.
- tata71 5y ago
- unbanned 5y agoIs it someone's responsibility to periodically use the environment as real users? Without this, there's no value in running a duplicate environment like this. Automated tests won't capture human interaction perfectly...
- rbanffy 5y agoYou can automate at the UI level and run that set of interactions (as well as screen captures and image matching if needed)
- nurettin 5y agoReminds me how Homakov forward-tested github issues by sending a message from 3012 (it worked) Here's the original link https://github.com/rails/rails/issues/5239 https://github.com/rails/rails/issues/5239 Unfortunately, they fixed the date and his bender account got renamed.