Mijung Kim
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
Research Interests
Mijung Kim has a total of 48 co-authors. Here are the top co-authors by number of shared publications:
Mary Jean Harrold
College of Computing, Georgia Institute of Technology, Atlanta, GA
3 shared publicationsCarsten Görg
2 shared publicationsHina Shah
2 shared publicationsSaurabh Sinha
2 shared publications- Yuseok Jeon
Korea University, Seoul, Republic of Korea
2 shared publications Alessandro Orso
College of Computing, Georgia Institute of Technology, Atlanta, GA
1 shared publication
Latest Publications
- Open Access
- 14 November 2026
- Published by Association for Computing Machinery (ACM)
- p. 1522-1536
RustGo: Fairly Directed Greybox Fuzzing for Enforcing Rust Memory Safety
- 14 November 2026
- Published by Association for Computing Machinery (ACM)
- p. 1522-1536
Open AccessRustGo: Fairly Directed Greybox Fuzzing for Enforcing Rust Memory Safety
- Open Access
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 1093-1105
Testing IFrame Rendering in Web Browsers
Iframes are widely used in modern web development, but their separation from the parent page can lead to iframe-specific rendering bugs, which occur only when content is embedded within an iframe. These bugs may degrade user experience and, in some cases, lead to serious security vulnerabilities. However, existing rendering bug detection techniques are largely ineffective since their oracles compare rendering outputs only within the same context and fail to capture discrepancies across different rendering contexts. This paper presents ICheck, an automated testing technique for iframe rendering in web browsers. Specifically, given an HTML document, ICheck introduces a cross-context oracle that detects inconsistencies by comparing the same HTML content in both top-level and iframe contexts. To further assist debugging, ICheck performs layout-aware input reduction by redefining the effective search space of bug-inducing elements. As a result, ICheck helps developers more effectively and efficiently identify and diagnose iframe-specific rendering bugs. Evaluated on the most popular browsers, Chrome and Firefox, ICheck detected 21 previously unknown bugs, all of which were confirmed. On average, ICheck uncovered 3.8× more bugs than state-of-the-art rendering bug detection work. In addition, ICheck effectively reduced HTML inputs by 93% in DOM nodes while achieving up to 10.1× faster reduction time compared with state-of-the-art delta debugging approaches.
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 1093-1105
Open AccessTesting IFrame Rendering in Web Browsers
Iframes are widely used in modern web development, but their separation from the parent page can lead to iframe-specific rendering bugs, which occur only when content is embedded within an iframe. These bugs may degrade user experience and, in some cases, lead to serious security vulnerabilities. However, existing rendering bug detection techniques are largely ineffective since their oracles compare rendering outputs only within the same context and fail to capture discrepancies across different rendering contexts. This paper presents ICheck, an automated testing technique for iframe rendering in web browsers. Specifically, given an HTML document, ICheck introduces a cross-context oracle that detects inconsistencies by comparing the same HTML content in both top-level and iframe contexts. To further assist debugging, ICheck performs layout-aware input reduction by redefining the effective search space of bug-inducing elements. As a result, ICheck helps developers more effectively and efficiently identify and diagnose iframe-specific rendering bugs. Evaluated on the most popular browsers, Chrome and Firefox, ICheck detected 21 previously unknown bugs, all of which were confirmed. On average, ICheck uncovered 3.8× more bugs than state-of-the-art rendering bug detection work. In addition, ICheck effectively reduced HTML inputs by 93% in DOM nodes while achieving up to 10.1× faster reduction time compared with state-of-the-art delta debugging approaches.
- Open Access
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 184-196
CIPIHunter: Detecting Configuration-Induced Prediction Instability in Deep Learning Frameworks
Deep learning (DL) frameworks support diverse execution configurations, including precision modes and model optimizations. Even with a fixed model, input, and framework version, changing these configurations can change model predictions, causing Configuration-Induced Prediction Instability (CIPI). It arises when configuration-dependent numerical perturbations propagate and cause potentially harmful model-level behavior. Existing API-level and model-level testing approaches are not well suited to detecting CIPI, as these approaches lack configuration-conditioned exploration and propagation-aware diagnosis. Therefore, we present CIPIHunter, which combines controlled configuration-pair testing, sensitivity-oriented mutation, feedback-guided search, and intermediate tracing to localize suspicious operators or operator groups. On 13 PyTorch models under a 100-round budget, CIPIHunter reports the highest raw CIPI count and 22 deduplicated Type I manifestations, 83.3% more than the strongest baseline, while remaining competitive in overall deduplicated manifestation coverage. In total, we submit 29 PyTorch issue reports. Developers have acknowledged eight, rejected five, and marked four as duplicates; nine remain pending, and three have been closed without an explicit determination. Separately, three reports are labeled “high-priority”. These results demonstrate the practical utility of CIPI testing for framework quality assurance.
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 184-196
Open AccessCIPIHunter: Detecting Configuration-Induced Prediction Instability in Deep Learning Frameworks
Deep learning (DL) frameworks support diverse execution configurations, including precision modes and model optimizations. Even with a fixed model, input, and framework version, changing these configurations can change model predictions, causing Configuration-Induced Prediction Instability (CIPI). It arises when configuration-dependent numerical perturbations propagate and cause potentially harmful model-level behavior. Existing API-level and model-level testing approaches are not well suited to detecting CIPI, as these approaches lack configuration-conditioned exploration and propagation-aware diagnosis. Therefore, we present CIPIHunter, which combines controlled configuration-pair testing, sensitivity-oriented mutation, feedback-guided search, and intermediate tracing to localize suspicious operators or operator groups. On 13 PyTorch models under a 100-round budget, CIPIHunter reports the highest raw CIPI count and 22 deduplicated Type I manifestations, 83.3% more than the strongest baseline, while remaining competitive in overall deduplicated manifestation coverage. In total, we submit 29 PyTorch issue reports. Developers have acknowledged eight, rejected five, and marked four as duplicates; nine remain pending, and three have been closed without an explicit determination. Separately, three reports are labeled “high-priority”. These results demonstrate the practical utility of CIPI testing for framework quality assurance.
- Open Access
- 27 October 2024
- Published by Association for Computing Machinery (ACM)
- p. 2456-2457
Studying Versioning in Stack Overflow
In Stack Overflow (SO), a post consists of multiple components: title, question, answers, question tags, and comments. Developers can create any of these components and make changes, which we call 'edits'. Edits are an important aspect of QA websites to ensure the quality and correctness of the texts. We performed multiple analyses on the revision history of 23 million SO posts from 2008 to 2023, and we gain a more comprehensive understanding of developers' content maintenance behaviors which lay the foundation for further research. We observed several interesting phenomena. Developers are making multiple edits on different SO post components. A majority of the edits are made by a single developer. Edits on questions and answers (Q&A) have the highest frequency and intensity annually. The rates of edits for Q&A are also exhibiting an increasing trend each year. By manually analyzing 1,000 SO post edits spanning 14 years, we observed 10 categories of reasons for editing an SO post. For Q&A, the majority of the edits are on including additional details and improving the clarity, while for question tags, the majority of the edits are on adding more tags about the question. These observations highlight the potential for developing tools that could assist in creating high-quality posts from the outset, thereby reducing the need for future edits.
- 27 October 2024
- Published by Association for Computing Machinery (ACM)
- p. 2456-2457
Open AccessStudying Versioning in Stack Overflow
In Stack Overflow (SO), a post consists of multiple components: title, question, answers, question tags, and comments. Developers can create any of these components and make changes, which we call 'edits'. Edits are an important aspect of QA websites to ensure the quality and correctness of the texts. We performed multiple analyses on the revision history of 23 million SO posts from 2008 to 2023, and we gain a more comprehensive understanding of developers' content maintenance behaviors which lay the foundation for further research. We observed several interesting phenomena. Developers are making multiple edits on different SO post components. A majority of the edits are made by a single developer. Edits on questions and answers (Q&A) have the highest frequency and intensity annually. The rates of edits for Q&A are also exhibiting an increasing trend each year. By manually analyzing 1,000 SO post edits spanning 14 years, we observed 10 categories of reasons for editing an SO post. For Q&A, the majority of the edits are on including additional details and improving the clarity, while for question tags, the majority of the edits are on adding more tags about the question. These observations highlight the potential for developing tools that could assist in creating high-quality posts from the outset, thereby reducing the need for future edits.
- 30 June 2022
- Published by Korean Association For Learner-Centered Curriculum And Instruction in Korean Association For Learner-Centered Curriculum And Instruction
- Vol. 22 (12) , 571-588
The effects of Self-regulation and Attention concentration on Computational Thinking according to Coding Play experience of children
코딩놀이 경험에 따라 유아의 자기조절력과 주의집중력이 컴퓨팅 사고력에 미치는 영향 의 이용 수, 등재여부, 발행기관, 저자, 초록, 목차, 참고문헌 등 논문에 관한 다양한 정보 및 관련논문 목록과 논문의 분야별 BEST, NEW 논문 목록을 확인 하실 수 있습니다.
- 30 June 2022
- Published by Korean Association For Learner-Centered Curriculum And Instruction in Korean Association For Learner-Centered Curriculum And Instruction
- Vol. 22 (12) , 571-588
The effects of Self-regulation and Attention concentration on Computational Thinking according to Coding Play experience of children
코딩놀이 경험에 따라 유아의 자기조절력과 주의집중력이 컴퓨팅 사고력에 미치는 영향 의 이용 수, 등재여부, 발행기관, 저자, 초록, 목차, 참고문헌 등 논문에 관한 다양한 정보 및 관련논문 목록과 논문의 분야별 BEST, NEW 논문 목록을 확인 하실 수 있습니다.
- Open Access
- 30 June 2019
- Published by Yonsei University College of Medicine in Korean Medical Education Review
- Vol. 21 (2) , 112-122
Survey on the Education System for New Graduate Nurses in Hospitals: Focusing on the Preceptorship
Values are presented as number (%) or min– max.
- 30 June 2019
- Published by Yonsei University College of Medicine in Korean Medical Education Review
- Vol. 21 (2) , 112-122
Open AccessSurvey on the Education System for New Graduate Nurses in Hospitals: Focusing on the Preceptorship
Values are presented as number (%) or min– max.
- Open Access
- 1 January 2019
- Published by XMLink in Journal of Gynecologic Oncology
- Vol. 30 (4) , e65
Prediction of survival outcomes in patients with epithelial ovarian cancer using machine learning methods
Paik ES, et al. J Gynecol Oncol. 2018 Aug;30:e65. https://doi.org/10.3802/jgo.2019.30.e65
- 1 January 2019
- Published by XMLink in Journal of Gynecologic Oncology
- Vol. 30 (4) , e65
Open AccessPrediction of survival outcomes in patients with epithelial ovarian cancer using machine learning methods
Paik ES, et al. J Gynecol Oncol. 2018 Aug;30:e65. https://doi.org/10.3802/jgo.2019.30.e65
- Open Access
- 30 August 2015
- Published by Association for Computing Machinery (ACM)
- p. 990-993
REMI: defect prediction for efficient API testing
Quality assurance for common APIs is important since the the reliability of APIs affects the quality of other systems using the APIs. Testing is a common practice to ensure the quality of APIs, but it is a challenging and laborious task especially for industrial projects. Due to a large number of APIs with tight time constraints and limited resources, it is hard to write enough test cases for all APIs. To address these challenges, we present a novel technique, REMI that predicts high risk APIs in terms of producing potential bugs. REMI allows developers to write more test cases for the high risk APIs. We evaluate REMI on a real-world industrial project, Tizen-wearable, and apply REMI to the API development process at Samsung Electronics. Our evaluation results show that REMI predicts the bug-prone APIs with reasonable accuracy (0.681 f-measure on average). The results also show that applying REMI to the Tizen-wearable development process increases the number of bugs detected, and reduces the resources required for executing test cases.
- 30 August 2015
- Published by Association for Computing Machinery (ACM)
- p. 990-993
Open AccessREMI: defect prediction for efficient API testing
Quality assurance for common APIs is important since the the reliability of APIs affects the quality of other systems using the APIs. Testing is a common practice to ensure the quality of APIs, but it is a challenging and laborious task especially for industrial projects. Due to a large number of APIs with tight time constraints and limited resources, it is hard to write enough test cases for all APIs. To address these challenges, we present a novel technique, REMI that predicts high risk APIs in terms of producing potential bugs. REMI allows developers to write more test cases for the high risk APIs. We evaluate REMI on a real-world industrial project, Tizen-wearable, and apply REMI to the API development process at Samsung Electronics. Our evaluation results show that REMI predicts the bug-prone APIs with reasonable accuracy (0.681 f-measure on average). The results also show that applying REMI to the Tizen-wearable development process increases the number of bugs detected, and reduces the resources required for executing test cases.
- 7 March 2011
- Vol. 2011, 22-26
An Informatics Framework for Testing Data Integrity and Correctness of Federated Biomedical Databases
Clinical research is increasingly relying on information gathered and managed in different database systems and institutions. Distributed data collection and management processes in such settings can be extremely complex and lead to a range of issues involving the integrity and accuracy of the distributed data. To address this challenge, we propose a middleware framework for assessing the data integrity and correctness in federated environments. The framework has two main elements: (1) a test model describing the dependencies between and constraints on data sources and datasets, and (2) a family of testing techniques that create and execute test cases based on the model.
- 7 March 2011
- Vol. 2011, 22-26
An Informatics Framework for Testing Data Integrity and Correctness of Federated Biomedical Databases
Clinical research is increasingly relying on information gathered and managed in different database systems and institutions. Distributed data collection and management processes in such settings can be extremely complex and lead to a range of issues involving the integrity and accuracy of the distributed data. To address this challenge, we propose a middleware framework for assessing the data integrity and correctness in federated environments. The framework has two main elements: (1) a test model describing the dependencies between and constraints on data sources and datasets, and (2) a family of testing techniques that create and execute test cases based on the model.
- 1 January 2010
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 383-392
Automated Bug Neighborhood Analysis for Identifying Incomplete Bug Fixes
Although many static-analysis techniques have been developed for automatically detecting bugs, such as null dereferences, fewer automated approaches have been presented for analyzing whether and how such bugs are fixed. Attempted bug fixes may be incomplete in that a related manifestation of the bug remains unfixed. In this paper, we characterize the “completeness” of attempted bug fixes that involve the flow of invalid values from one program point to another, such as null dereferences, in Java programs. Our characterization is based on the definition of a bug neighborhood, which is a scope of flows of invalid values. We present an automated analysis that, given two versions P and P' of a program, identifies the bugs in P that have been fixed in P', and classifies each fix as complete or incomplete. We implemented our technique for null-dereference bugs and conducted empirical studies using open-source projects. Our results indicate that, for the projects we studied, many bug fixes are not complete, and thus, may cause failures in subsequent executions of the program.
- 1 January 2010
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 383-392
Automated Bug Neighborhood Analysis for Identifying Incomplete Bug Fixes
Although many static-analysis techniques have been developed for automatically detecting bugs, such as null dereferences, fewer automated approaches have been presented for analyzing whether and how such bugs are fixed. Attempted bug fixes may be incomplete in that a related manifestation of the bug remains unfixed. In this paper, we characterize the “completeness” of attempted bug fixes that involve the flow of invalid values from one program point to another, such as null dereferences, in Java programs. Our characterization is based on the definition of a bug neighborhood, which is a scope of flows of invalid values. We present an automated analysis that, given two versions P and P' of a program, identifies the bugs in P that have been fixed in P', and classifies each fix as complete or incomplete. We implemented our technique for null-dereference bugs and conducted empirical studies using open-source projects. Our results indicate that, for the projects we studied, many bug fixes are not complete, and thus, may cause failures in subsequent executions of the program.