Trip itinerary generator engine testing
A few days ago, we found a bug in our trip itinerary generation engine. We wrote a test suit to reproduce that bug, but then we decided to go deeper. As plnnr.com generates trips according to trip preferences, why not generate the trip preferences with a fuzzer, and then check if the planning algorithm chokes on them? While fuzzing is usually used to generate invalid input with the goal of causing the program to crash, in this case we’ll be generating valid input with the goal of causing the planning algorithm to fail. This way our planning algorithm will only get better with more testing.
Read more about the technical details at algorithm.co.il