BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.osgeo.org//qgis-uc2026//talk//UQQ8LA
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-qgis-uc2026-UQQ8LA@talks.osgeo.org
DTSTART;TZID=CET:20261006T110000
DTEND;TZID=CET:20261006T113000
DESCRIPTION:Ideally\, any bug fix\, feature or refactoring in a QGIS plugin
  can be made safely\, knowing that the quality checks of the testing frame
 work of the plugin will catch any regressions introduced by the new or cha
 nged code.\n\nIn reality\, getting there can be quite hard: How does one e
 ven start to write tests? How many tests does my plugin need? How can the 
 interactive parts of the QGIS GUI be tested? And then\, once tests are in 
 place\, how do I make sure that all PRs are tested? And what makes certain
  that the code commited to `main` actually passes all tests?\n\nIn this ta
 lk\, we will showcase how to write tests for a QGIS plugin using pytest an
 d how to automate running tests using the GitHub and GitLab CI.\n\nAll thi
 s is not done using a toy project\, where often everything seems to neatly
  fall into place.\nInstead\, we will have a look at a real-world example: 
 the ORSTools QGIS Plugin\, showcased at QGIS UC 2025.
DTSTAMP:20260724T234929Z
LOCATION:Bridge 2
SUMMARY:QGIS plugin testing - Introduction and Automation - Jakob Schnell
URL:https://talks.osgeo.org/qgis-uc2026/talk/UQQ8LA/
END:VEVENT
END:VCALENDAR