BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Software Center - ECPv6.16.2//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:Software Center
X-ORIGINAL-URL:https://www.software-center.se
X-WR-CALDESC:Events for Software Center
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-Robots-Tag:noindex
X-PUBLISHED-TTL:PT1H
BEGIN:VTIMEZONE
TZID:Europe/Stockholm
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:20190331T010000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:20191027T010000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:20200329T010000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:20201025T010000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:20210328T010000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:20211031T010000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Europe/Stockholm:20201109T120000
DTEND;TZID=Europe/Stockholm:20201109T123000
DTSTAMP:20260527T003018
CREATED:20201012T072050Z
LAST-MODIFIED:20201109T103002Z
UID:2218-1604923200-1604925000@www.software-center.se
SUMMARY:Lunch seminar: Continuous Delivery
DESCRIPTION:Title: Multi-factor Approach for Flaky Test Detection and Automated Root Cause Analysis \nSpeaker: Azeem Ahmad\, Linköping University \nAbstract:  Re-running test cases is the most popular and adopted approach to detect flaky test in large scale industries. Re-running is costly because it consumes a lot of computing power. Google uses 2-16% of its testing budget just to re-run flaky tests. Re-running is unreliable because it is hard to determine the number of re-runs to find discrepancy in output. We developed\, implemented and evaluated multi-factor approach to detect flaky test without re-running. The contributed factors are (1) number of test smells in the test cases\, (2) whether test case failed after executing on the corresponding change in production code\, (3) test case history\, and (4) test case size. The machine learning algorithm is implemented to find relationships between the contributed factors and the possibility of test flakiness. Once the build is failed\, our tool can determine whether the failed test case is a real failure or flaky.
URL:https://www.software-center.se/event/continuous_delivery/
LOCATION:Virtual event\, Sweden
ORGANIZER;CN="Kristian Sandahl":MAILTO:kristian.sandahl@liu.se
END:VEVENT
END:VCALENDAR