You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of the analytics suite testing is done by a single, almost 1000 line test that is completely unwieldy and impossible to maintain in the long term. This needs to be split up into the essential parts that are of utmost importance, and other parts, that are not so much. In general, the more project-specific analytics code should move to ridepy-extras, along with the corresponding test code.
The text was updated successfully, but these errors were encountered:
Not to mention that part of the get_vehicle_quantities functionality is actually broken (or was, I don't remember), which was "checked" by the test. This proves that the current testing scheme does not work.
* some analytics things, graph distance cache size increased
* added external cost, renamed class to cls/lower cased some things
* fixed some bugs
* more analytics stuff
* formatting
* fixed analytics bug where the avg stoplist length was computed incorrectly, and cython continuous space bug, where the coord_range was not pickled
* seat capacity and idling duration
* non-analytics tests fixed
* fixed the analytics test for now, still needs heavy refactoring, see #204
* comment removed
* added old file from other branch
Most of the analytics suite testing is done by a single, almost 1000 line test that is completely unwieldy and impossible to maintain in the long term. This needs to be split up into the essential parts that are of utmost importance, and other parts, that are not so much. In general, the more project-specific analytics code should move to ridepy-extras, along with the corresponding test code.
The text was updated successfully, but these errors were encountered: