Change Details

wmfdata should have automated tests, particularly for the run functions, to ensure that we don't inadvertently break them when updating. This will require figuring out what form these tests should take (pre-commit? pre-merge?) and what framework we should use to run them. It would probably be best to do this after T245223, so we can ensure that whatever strategy we use works with Gerrit.

We should write a script that uses wmfdata as an analyst would (for example, writing data to MariaDB and Hive and querying it back) and checks that the results were correct and no errors were raised. Once checked into the repo, it can be used by developers as a smoke test before pushing changes.

wmfdataWe should have automated tests, particularly for the run functionswrite a script that uses wmfdata as an analyst would (for example, to ensure that we don't inadvertently break them when updating. This will require figuring out what form these tests should take (pre-commit?writing data to MariaDB and Hive and querying it back) and checks that the results were correct and no errors were raised. pre-merge?) and what framework we should use to run them.Once checked into the repo, It would probablyit can be best to do this after T245223, so we can ensure that whatever strategy we use works with Gerrit.used by developers as a smoke test before pushing changes.