Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-12-15 | fix integration & playwright tests | Daniel Schadt | |
2022-12-14 | add test for track browsing | Daniel Schadt | |
2022-12-13 | add a test for editing tracks | Daniel Schadt | |
2022-12-10 | start with playwright tests | Daniel Schadt | |
2022-12-06 | add some tests for the registration form | Daniel Schadt | |
2022-08-13 | fix tests | Daniel Schadt | |
Now that the filtering is done via SQL, it is not enough for the user and the objects to be in the session - they need to be in the database, similar to the added tracks. Note that it was not entirely necessary in this case, since the tracks are public, but it provides the proper functionality in the future. | |||
2022-07-24 | add first basic tests for synthetic tracks | Daniel Schadt | |
2022-07-18 | give tests a temporary data dir | Daniel Schadt | |
2022-07-17 | run pylint on the test files as well | Daniel Schadt | |
2022-07-17 | Merge branch 'multi-download' | Daniel Schadt | |
2022-07-17 | add tests for archive download | Daniel Schadt | |
2022-07-16 | remove MyTourbook timezone guessing | Daniel Schadt | |
It turns out that the mt:TourStartTime is also given in UTC, and therefore cannot be used to get the timezone offset. The problem was that my local computer's timezone was the same as the tour timezone, so by the magic of Python's datetime.datetime.fromtimestamp (and the date CLI util), I did not notice that the timestamp actually represents UTC. Sadly, it currently looks like there is no way to extract the time zone from a MyTourbook export. | |||
2022-07-11 | add integration tests for uploading | Daniel Schadt | |
2022-07-09 | add tests for the login form | Daniel Schadt | |
2022-07-07 | add tests for util.guess_gpx_timezone | Daniel Schadt | |
2022-07-07 | start adding some unit tests | Daniel Schadt | |
2022-06-28 | Initial commit | Daniel Schadt | |