BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//FBQ8L
 L
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-europython-2026-GCWCEU-0@programme.europython.eu
DTSTART;TZID=CET:20260713T093000
DTEND;TZID=CET:20260713T110000
DESCRIPTION:We know we should write automated tests. But too often\, it is 
 a real chore: they may be slow\, unreliable\, difficult to run\, to mainta
 in\, even to write! Why is it so hard? How to take back control?\n\nFor th
 at\, you will work on a realistic project: a Python app with FastAPI backe
 nd\, a PostgreSQL database\, configuration files\, third-party APIs\, ... 
 and tests that are awful.\n\nYou will review:\n- the quality culture of th
 e project\n- how it is architectured\n- the existing tests\n- and the code
  quality\n\nThen you will prepare the plan:\n- your own test pyramid / str
 ategy\n- testing tools needed\n- essential scenarios\n- the CI to have you
 r back\n\nAnd start coding:\n- updating the existing tests\n- adding new t
 ests using powerful tooling\n- minimal refactoring to enable testing\n- cr
 eating fakes/mocks/simulators to enable testing\n\nYou'll leave able to:\n
 * diagnose what makes tests slow or convoluted\n* design a pragmatic test 
 strategy for your codebase\n* implement reliable tests\, with fakes and te
 stcontainers\n* refactor just enough to make code testable\n\nIt will be a
 round 65% hands-on\, and 35% guided analysis. The first two parts will tak
 e the first half of the session\, so that you have plenty of time to actua
 lly implement the strategy during the second half.\nThe code repository wi
 ll stay available to you after the workshop\, along with an example of the
  end-result.\n\nSetup :\n* [`uv`](https://docs.astral.sh/uv/)\n* (optional
 ) docker or podman\, to run TestContainers\n* (optional) a GitHub or GitLa
 b account\, to run CI
DTSTAMP:20260524T121903Z
LOCATION:Conference Hall Complex B (S4B)
SUMMARY:Getting out of the testing hell - Julien Lenormand\, GAFFIOT Jonath
 an
URL:https://programme.europython.eu/europython-2026/talk/GCWCEU/
END:VEVENT
BEGIN:VEVENT
UID:pretalx-europython-2026-GCWCEU-1@programme.europython.eu
DTSTART;TZID=CET:20260713T111500
DTEND;TZID=CET:20260713T124500
DESCRIPTION:We know we should write automated tests. But too often\, it is 
 a real chore: they may be slow\, unreliable\, difficult to run\, to mainta
 in\, even to write! Why is it so hard? How to take back control?\n\nFor th
 at\, you will work on a realistic project: a Python app with FastAPI backe
 nd\, a PostgreSQL database\, configuration files\, third-party APIs\, ... 
 and tests that are awful.\n\nYou will review:\n- the quality culture of th
 e project\n- how it is architectured\n- the existing tests\n- and the code
  quality\n\nThen you will prepare the plan:\n- your own test pyramid / str
 ategy\n- testing tools needed\n- essential scenarios\n- the CI to have you
 r back\n\nAnd start coding:\n- updating the existing tests\n- adding new t
 ests using powerful tooling\n- minimal refactoring to enable testing\n- cr
 eating fakes/mocks/simulators to enable testing\n\nYou'll leave able to:\n
 * diagnose what makes tests slow or convoluted\n* design a pragmatic test 
 strategy for your codebase\n* implement reliable tests\, with fakes and te
 stcontainers\n* refactor just enough to make code testable\n\nIt will be a
 round 65% hands-on\, and 35% guided analysis. The first two parts will tak
 e the first half of the session\, so that you have plenty of time to actua
 lly implement the strategy during the second half.\nThe code repository wi
 ll stay available to you after the workshop\, along with an example of the
  end-result.\n\nSetup :\n* [`uv`](https://docs.astral.sh/uv/)\n* (optional
 ) docker or podman\, to run TestContainers\n* (optional) a GitHub or GitLa
 b account\, to run CI
DTSTAMP:20260524T121903Z
LOCATION:Conference Hall Complex B (S4B)
SUMMARY:Getting out of the testing hell - Julien Lenormand\, GAFFIOT Jonath
 an
URL:https://programme.europython.eu/europython-2026/talk/GCWCEU/
END:VEVENT
END:VCALENDAR
