Description
Apps written with GTK in a traditional fashion often suffer from a
code structure for which it is impossible to write tests.
It is easy to find learning material about Functional Reactive
Programming, the Elm architecture, and such things, which are great if
you are writing new code in a high-level language with facilities for
actually doing declarative GUIs. You can even do this in with
GTK... if you are writing 100% new code.
What is not easy to find, is material on how to refactor a
callback-hell, traditionally-structured, years-old, legacy codebase
that has no tests so that it is actually testable.
This is not a talk about "GUI testing" where you simulate mouse clicks
or compare screenshots. This talk is about refactoring — about making
it possible to add tests to an existing codebase that was not designed
for testability.
Author(s) Bio
Federico is the maintainer of librsvg, and one of the founders of GNOME. Through the sheer power of old age, he has seen toolkits come and go, and apps struggle to keep on living while toolkits go happily out of maintenance as they complete their life cycle. He would like to show you a way out of this cycle.
| Presentation Type | In Person |
|---|---|
| Pronouns | he/him |
