Determining whether a test execution should pass or fail remains a core obstacle to end-to-end test automation. Recent work has focused mainly on generating assertions from source context, leav- ing open how much pass/fail signal can be recovered directly from runtime behavior, especially under subject transfer. We present a cross-subject boundary study of this question on Python unit tests from the Tests4Py benchmark. Our pipeline collects execution traces via runtime instrumentation, compresses them through redundancy pruning and two minimization strategies (holistic filtering and key- point amplification), splits long traces into chunks whose partial predictions are aggregated per test, and fine-tunes open-weight large language models (LLMs) to classify tests from previously un- seen subjects as passing or failing. We evaluate CodeT5-small, Phi- 3.5-mini-instruct, and Llama-3.1-8B under varying context budgets and overlap settings. The best completed configuration, CodeT5- small with keypoint amplification and no overlap, reaches a macro- averaged failing-class F1 score of 𝐹 1fail = 0.365 across the three held-out subjects of our fixed protocol, compared with 𝐹 1fail = 0.025 for an empirical-distribution reference; since the released traces contain no exception events, this signal cannot stem from spotting recorded exceptions. Larger context windows improve the holistic filtering configurations, whereas overlap has mixed effects. Within this single-protocol setting, runtime traces contain a non- trivial cross-subject signal. However, performance remains too low and too unstable across subjects for stand-alone deployment. In this setting, progress appears to depend more on representation, aggregation, and robustness to subject shift than on model scale alone.
Supporting data, adapters, predictions and code for the article *Low-Cost LoRA Fine-Tuning of Small Language Models for Multi-Step Arithmetic Reasoning* by Jake O'Grady, Asena Isik Gürhan, Chee Fong Ting and Effirul Ramlan (University of Galway). We generated 20,000 GSM8K-derived arithmetic problems with step-by-step s...
O'Grady, Jake, Gürhan, Asena Isik, Chee, Fong Ting et al.· Zenodo (CERN European Organi...· 465 citations
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors, and shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context.
Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al.· Journal of Systems and Softw...· 78 citations· ⚡6