Kristian Wiklund
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Research Interests
Kristian Wiklund has a total of 13 co-authors. Here are the top co-authors by number of shared publications:
Sigrid Eldh
Ericsson AB Stockholm SE‐164 80 Sweden
6 shared publicationsDaniel Sundmark
4 shared publicationsKristina Lundqvist
Mälardalen University Box 883, Västerås SE‐721 23 Sweden
4 shared publicationsAndreas Ermedahl
1 shared publication- Andreas Ermedahl
Ericsson AB, Stockholm, Sweden and KTH Royal Institute of Technology, Stockholm, Sweden
1 shared publication - Cyrille Artho
KTH Royal Institute of Technology
1 shared publication
Latest Publications
- Open Access
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 145-157
PhantomRun: Auto Repair of Compilation Errors in Embedded Open Source Software
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 145-157
Open AccessPhantomRun: Auto Repair of Compilation Errors in Embedded Open Source Software
- 1 April 2018
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 159-162
The Next Level of Test Automation: What About the Users?
Test automation is an enabler for effective and efficient software development and is widely embraced thanks to agile practices such as continuous integration. Based on our own experience and observations, we conjecture that the majority of test automation today is script based and focused on execution, where testers explicitly implement "how" to do the test. This is a labor-intensive and potentially error-prone endeavor that have the potential to be a significant bottleneck for even productivity and speed in software development. Hence, we consider it clear that "the next level of test automation" to a greater extent will be about "what" to test and not "how" to test it, which will require more advanced test tools and test systems compared to today's relatively simple mechanisms. We propose that this will result in an increased dependency to tools developed outside the user organizations, partially due to the cost and complexity of development of advanced tools, and partially due to the competence needed to understand and implement the necessary algorithms which simply will not be available in most development projects. In this paper, we draw on our experience from using and developing test automation tools to propose a number of challenges that we believe need to be considered when introducing new approaches to test automation in industry.
- 1 April 2018
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 159-162
The Next Level of Test Automation: What About the Users?
Test automation is an enabler for effective and efficient software development and is widely embraced thanks to agile practices such as continuous integration. Based on our own experience and observations, we conjecture that the majority of test automation today is script based and focused on execution, where testers explicitly implement "how" to do the test. This is a labor-intensive and potentially error-prone endeavor that have the potential to be a significant bottleneck for even productivity and speed in software development. Hence, we consider it clear that "the next level of test automation" to a greater extent will be about "what" to test and not "how" to test it, which will require more advanced test tools and test systems compared to today's relatively simple mechanisms. We propose that this will result in an increased dependency to tools developed outside the user organizations, partially due to the cost and complexity of development of advanced tools, and partially due to the competence needed to understand and implement the necessary algorithms which simply will not be available in most development projects. In this paper, we draw on our experience from using and developing test automation tools to propose a number of challenges that we believe need to be considered when introducing new approaches to test automation in industry.
- Open Access
- 5 September 2017
- Published by Wiley in Software Testing, Verification and Reliability
- Vol. 27 (8)
Impediments for software test automation: A systematic literature review
Summary: Automated software testing is a critical enabler for modern software development, where rapid feedback on the product quality is expected. To make the testing work well, it is of high importance that impediments related to test automation are prevented and removed quickly. An enabling factor for all types of improvement is to understand the nature of what is to be improved. We have performed a systematic literature review of reported impediments related to software test automation to contribute to this understanding. In this paper, we present the results from the systematic literature review: The list of identified publications, a categorization of identified impediments, and a qualitative discussion of the impediments proposing a socio‐technical system model of the use and implementation of test automation.
- 5 September 2017
- Published by Wiley in Software Testing, Verification and Reliability
- Vol. 27 (8)
Open AccessImpediments for software test automation: A systematic literature review
Summary: Automated software testing is a critical enabler for modern software development, where rapid feedback on the product quality is expected. To make the testing work well, it is of high importance that impediments related to test automation are prevented and removed quickly. An enabling factor for all types of improvement is to understand the nature of what is to be improved. We have performed a systematic literature review of reported impediments related to software test automation to contribute to this understanding. In this paper, we present the results from the systematic literature review: The list of identified publications, a categorization of identified impediments, and a qualitative discussion of the impediments proposing a socio‐technical system model of the use and implementation of test automation.
- 1 March 2014
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 337-342
Towards a Test Automation Improvement Model (TAIM)
In agile software development, industries are becoming more dependent on automated test suites. Thus, the test code quality is an important factor for the overall system quality and maintainability. We propose a Test Automation Improvement Model (TAIM) defining ten key areas and one general area. Each area should be based on measurements, to fill the gap of existing assessments models. The main contribution of this paper is to provide the outline of TAIM and present our intermediate results and some initial metrics to support our model. Our initial target has been the key area targeting implementation and structure of test code. We have used common static measurements to compare the test code and the source code of a unit test automation suite being part of a large complex telecom subsystem. Our intermediate results show that it is possible to outline such an improvement model and our metrics approach seems promising. However, to get a generic useful model to aid test automation evolution and provide for comparable measurements, many problems still remain to be solved. TAIM can as such be viewed as a framework to guide the research on metrics for test automation artifacts.
- 1 March 2014
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 337-342
Towards a Test Automation Improvement Model (TAIM)
In agile software development, industries are becoming more dependent on automated test suites. Thus, the test code quality is an important factor for the overall system quality and maintainability. We propose a Test Automation Improvement Model (TAIM) defining ten key areas and one general area. Each area should be based on measurements, to fill the gap of existing assessments models. The main contribution of this paper is to provide the outline of TAIM and present our intermediate results and some initial metrics to support our model. Our initial target has been the key area targeting implementation and structure of test code. We have used common static measurements to compare the test code and the source code of a unit test automation suite being part of a large complex telecom subsystem. Our intermediate results show that it is possible to outline such an improvement model and our metrics approach seems promising. However, to get a generic useful model to aid test automation evolution and provide for comparable measurements, many problems still remain to be solved. TAIM can as such be viewed as a framework to guide the research on metrics for test automation artifacts.
- 1 March 2014
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 113-122
Impediments for Automated Testing -- An Empirical Analysis of a User Support Discussion Board
To better understand the challenges encountered by users and developers of automatic software testing, we have performed an empirical investigation of a discussion board used for support of a test automation framework having several hundred users. The messages on the discussion board were stratified into problem reports, help requests, development information, and feature requests. The messages in the problem report and help request strata were then sampled and analyzed using thematic analysis, searching for common patterns. Our analysis indicate that a large part of the impediments discussed on the board are related to issues related to the centralized IT environment, and to erroneous behaviour connected to the use of the framework and related components. We also observed a large amount of impediments related to the use of software development tools. Turning to the help requests, we found that the majority of the help requests were about designing test scripts and not about the areas that appear to be most problematic. From our results and previous publications, we see a clear need to simplify the use, installation, and configuration of test systems of this type. The problems attributable to software development tools suggest that testers implementing test automation need more skills in handling those tools, than historically has been assumed. Finally, we propose that further research into the benefits of centralization of tools and IT environments, as well as structured deployment and efficient use of test automation, is performed.
- 1 March 2014
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 113-122
Impediments for Automated Testing -- An Empirical Analysis of a User Support Discussion Board
To better understand the challenges encountered by users and developers of automatic software testing, we have performed an empirical investigation of a discussion board used for support of a test automation framework having several hundred users. The messages on the discussion board were stratified into problem reports, help requests, development information, and feature requests. The messages in the problem report and help request strata were then sampled and analyzed using thematic analysis, searching for common patterns. Our analysis indicate that a large part of the impediments discussed on the board are related to issues related to the centralized IT environment, and to erroneous behaviour connected to the use of the framework and related components. We also observed a large amount of impediments related to the use of software development tools. Turning to the help requests, we found that the majority of the help requests were about designing test scripts and not about the areas that appear to be most problematic. From our results and previous publications, we see a clear need to simplify the use, installation, and configuration of test systems of this type. The problems attributable to software development tools suggest that testers implementing test automation need more skills in handling those tools, than historically has been assumed. Finally, we propose that further research into the benefits of centralization of tools and IT environments, as well as structured deployment and efficient use of test automation, is performed.
- 1 May 2013
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 67-68
Can we do useful industrial software engineering research in the shadow of lean and agile?
The software industry is rapidly changing from traditional ways of working to lean and agile development methods using self-organized feature development teams that are performing a much larger part of the development process than before. Face to face communication will replace many of the design artifacts used for work-in-progress, such as defect reports and feature system design specifications. This type of data will cease to exist when the feature is developed or the problem is solved, and will not be readily available to researchers. As a consequence, software engineering research in industry will have to rely primarily on participatory and observational methods.
- 1 May 2013
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 67-68
Can we do useful industrial software engineering research in the shadow of lean and agile?
The software industry is rapidly changing from traditional ways of working to lean and agile development methods using self-organized feature development teams that are performing a much larger part of the development process than before. Face to face communication will replace many of the design artifacts used for work-in-progress, such as defect reports and feature system design specifications. This type of data will cease to exist when the feature is developed or the problem is solved, and will not be readily available to researchers. As a consequence, software engineering research in industry will have to rely primarily on participatory and observational methods.
- 1 January 2013
- Published by Springer Nature in Lecture Notes in Computer Science
- p. 35-49
Impediments in Agile Software Development: An Empirical Investigation
- 1 January 2013
- Published by Springer Nature in Lecture Notes in Computer Science
- p. 35-49
Impediments in Agile Software Development: An Empirical Investigation
- 1 April 2012
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 21594848,p. 887-892
Technical Debt in Test Automation
Automated test execution is one of the more popular and available strategies to minimize the cost for software testing, and is also becoming one of the central concepts in modern software development as methods such as test-driven development gain popularity. Published studies on test automation indicate that the maintenance and development of test automation tools commonly encounter problems due to unforeseen issues. To further investigate this, we performed a case study on a telecommunication subsystem to seek factors that contribute to inefficiencies in use, maintenance, and development of the automated testing performed within the scope of responsibility of a software design team. A qualitative evaluation of the findings indicates that the main areas of improvement in this case are in the fields of interaction design and general software design principles, as applied to test execution system development.
- 1 April 2012
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 21594848,p. 887-892
Technical Debt in Test Automation
Automated test execution is one of the more popular and available strategies to minimize the cost for software testing, and is also becoming one of the central concepts in modern software development as methods such as test-driven development gain popularity. Published studies on test automation indicate that the maintenance and development of test automation tools commonly encounter problems due to unforeseen issues. To further investigate this, we performed a case study on a telecommunication subsystem to seek factors that contribute to inefficiencies in use, maintenance, and development of the automated testing performed within the scope of responsibility of a software design team. A qualitative evaluation of the findings indicates that the main areas of improvement in this case are in the fields of interaction design and general software design principles, as applied to test execution system development.