GET /congress/2025/event/dae23004-37c6-4dab-8ea8-cf4356d409c2/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept
{
"id": "dae23004-37c6-4dab-8ea8-cf4356d409c2",
"kind": "sos",
"name": "C Code Testing. Let's talk about it!",
"slug": "c-code-testing-pass-fail-or-segfault",
"url": "https://api.events.ccc.de/congress/2025/event/dae23004-37c6-4dab-8ea8-cf4356d409c2/?format=api",
"track": null,
"assembly": "sos",
"room": "ce20bae4-fc3a-46e2-8608-be3caa7fa20d",
"location": null,
"language": "en, de",
"description": "PASS, FAIL, or SEGFAULT?\r\nI am curious how other people test their software, particularly C software.\r\n\r\nDo you test at all?\r\nHow do you do it?\r\nDo you have any hacks to prevent you from shooting yourself in the foot?\r\nLet's share your experiences!\r\n\r\nTo break the ice and get the conversation started, I will give a short talk about my journey through the testing jungle.\r\nAnd then let's have an open discussion where you can talk about your testing approach. It would be awesome if you could show us a test you wrote.\r\n\r\nEveryone is welcome, especially if you're just curious. No testing or C experience is necessary. This is a great place to ask questions and learn from the workflows of others.\r\n\r\nYou can contact me (Dominik) via email: 39C3@dominikloidolt.at\r\n\r\nSee you.\r\n\r\nFind the slides here: https://github.com/dloidolt/39c3_c_code_testing",
"schedule_start": "2025-12-27T22:00:00+01:00",
"schedule_duration": "00:50:00",
"schedule_end": "2025-12-27T22:50:00+01:00"
}