[logseq-plugin-git:commit] 2025-06-23T09:00:32.907Z

This commit is contained in:
2025-06-23 11:00:34 +02:00
parent f33eb526db
commit 86f5d812e1
+3
View File
@@ -15,6 +15,7 @@ external-link:: [Program - FSE 2025](https://conf.researchr.org/program/fse-2025
- Instructions to upload / send the slides ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAgNERPBAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
- #### Day 1
- **FSE Keynote: Mark Harman, Peter OHearn, and Shubho Sengupta****[Harden and Catch for Just-in-Time Assured LLM-Based Software Testing: An Industrial Perspective and Open Research Challenge](https://conf.researchr.org/program/fse-2025/program-fse-2025/?date=Mon%2023%20Jun%202025%2BTue%2024%20Jun%202025%2BWed%2025%20Jun%202025%2BThu%2026%20Jun%202025%2BFri%2027%20Jun%202025&past=Show%20upcoming%20events%20only#)**
collapsed:: true
- Abstract:
collapsed:: true
- Despite decades of research and practice in automated software testing, several fundamental concepts remain ill-defined and under explored, despite their enormous potential real world impact. We show that these concepts raise exciting new challenges in the context of Large Language Models for software code and test generation. More specifically, we normally define and investigate the properties of hardening and catching tests. A hardening test is one that seeks to protect a code change against future regressions, while a catching test is one that catches such a regression, or a fault in new functionality introduced by a change. Hardening tests can be generated at any time, and may become catching tests when a future revision is caught. We also define and motivate the Catching “Just in Time” (JiTTest) Challenge, in which tests are generated “just in time” to catch new faults before they land into production, showing that it can also be repurposed to catch latent faults in legacy code. We set these challenges in the context of the work we have been doing on automated test generation at Meta, reviewing how we came to where we are now, and why we believe these open challenges represent such exciting opportunities for researchers, due to the enormous potential real world impact.
@@ -37,4 +38,6 @@ external-link:: [Program - FSE 2025](https://conf.researchr.org/program/fse-2025
- Testing vs Verification
- Grounds for optimism today! (oracle problem)
-
-
-
-