Investigating the Readability of Test Code: Combining Scientific and Practical Views (2403.16639v1)
Abstract: The readability of source code is key for understanding and maintaining software systems and tests. Several studies investigate the readability of source code, but there is limited research on the readability of test code and related influence factors. We investigate the factors that influence the readability of test code from an academic perspective complemented by practical views. First, we perform a Systematic Mapping Study (SMS) with a focus on scientific literature. Second, we extend this study by reviewing grey literature sources for practical aspects on test code readability and understandability. Finally, we conduct a controlled experiment on the readability of a selected set of test cases to collect additional knowledge on influence factors discussed in practice. The result set of the SMS includes 19 primary studies from the scientific literature. The grey literature search reveals 62 sources for information on test code readability. Based on an analysis of these sources, we identified a combined set of 14 factors that influence the readability of test code. 7 of these factors were found in scientific and grey literature, while some factors were mainly discussed in academia (2) or industry (5) with limited overlap. The controlled experiment on practically relevant influence factors showed that the investigated factors have a significant impact on readability for half of the selected test cases. Our review of scientific and grey literature showed that test code readability is of interest for academia and industry with a consensus on key influence factors. However, we also found factors only discussed by practitioners. For some of these factors we were able to confirm an impact on readability in a first experiment. Therefore, we see the need to bring together academic and industry viewpoints to achieve a common view on the readability of software test code.
- S. Afshan, P. McMinn and M. Stevenson “Evolving readable string test inputs using a natural language model to reduce human oracle cost” In Proceedings - IEEE 6th Int. Conf. on Software Testing, Verification and Validation, ICST 2013, 2013, pp. 352–361
- Naser Al Madi “How Readable is Model-generated Code? Examining Readability and Visual Inspection of GitHub Copilot” In 37th IEEE/ACM International Conference on Automated Software Engineering, 2022, pp. 1–5
- “An industrial evaluation of unit test generation: Finding real faults in a financial application” In Proceedings - 2017 IEEE/ACM 39th Int. Conf. on Software Engineering: Software Engineering in Practice Track, ICSE-SEIP 2017 Institute of ElectricalElectronics Engineers Inc., 2017, pp. 263–272
- Abdullah Alsharif, Gregory M. Kapfhammer and Phil McMinn “What Factors Make SQL Test Cases Understandable for Testers? A Human Study of Automated Test Data Generation Techniques” In 2019 IEEE International Conference on Software Maintenance and Evolution (ICSME), 2019, pp. 437–448 DOI: 10.1109/ICSME.2019.00076
- Maurício Aniche “Effective Software Testing Version 4 - Academia.edu” nan, 2022 URL: https://www.academia.edu/70086528/Effective%5C_Software%5C_Testing%5C_Version%5C_4
- Gleb Bahmutov “Readable Cypress.io tests - Gleb Bahmutov”, Blog, 2019 URL: https://glebbahmutov.com/blog/readable-tests/
- “Is Assertion Roulette still a test smell? An experiment from the perspective of testing education” In 2022 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC), 2022, pp. 1–7 DOI: 10.1109/VL/HCC53370.2022.9833107
- Anshul Bansal “Best Practices For Unit Testing In Java - Baeldung”, Magazine, 2021 URL: https://www.baeldung.com/java-unit-testing-best-practices
- “Are test smells really harmful? an empirical study” In Empirical Software Engineering 20.4 Springer, 2015, pp. 1052–1094
- Vdaas Vald Company blog “The Unit Test Strategy In Vald”, Blog, 2021 URL: https://vdaas-vald.medium.com/the-unit-test-strategy-in-vald-912ed6f14fbd
- Peter Bloomfield “How to write a good unit test - Peter Bloomfield”, Blog, 2020 URL: https://peter.bloomfield.online/how-to-write-a-good-unit-test/
- Rafał Borowiec “Test code readability improved: JUnit with Mockito and FEST …”, Blog, 2013 URL: https://blog.codeleak.pl/2013/07/test-code-readability-improved-junit.html
- “How Good Are My Tests?” In Int. Workshop on Emerging Trends in Software Metrics, WETSoM IEEE Computer Society, 2017, pp. 9–14
- Marcos Brizeno “Write Better Tests in 5 Steps - Thoughtworks”, Blog, 2014 URL: https://www.thoughtworks.com/insights/blog/write-better-tests-5-steps
- Vadim Bulavin “Vadim Bulavin auf Twitter: ”9. A good unit test must have three …”, Blog, 2020 URL: https://twitter.com/v8tr/status/1217483476406079491?lang=de
- Raymond PL Buse and Westley R Weimer “A metric for software readability” In Proceedings of the 2008 int. symposium on Software testing and analysis, 2008, pp. 121–130
- Dan Carter “Make your automated tests easy to read - DC Coding - Dan …”, Blog, 2011 URL: https://codingblog.carterdan.net/2020/02/11/make-your-automated-tests-easy-to-read/
- Roberto Casadei “Effective unit testing - SlideShare”, Presentation, 2013 URL: https://de.slideshare.net/RobertoCasadei/effective-unit-testing
- “Do Automatically Generated Test Cases Make Debugging Easier? An Experimental Assessment of Debugging Effectiveness and Efficiency” New York, NY, USA: Association for Computing Machinery, 2015 DOI: 10.1145/2768829
- Henry Coles “Write Damp Test Code - Java for small teams - ncrcoe”, Wiki, 2015 URL: https://ncrcoe.gitbooks.io/java-for-small-teams/content/v/restructure/tests/1900%5C_write%5C_damp%5C_test%5C_code.html
- company “Unit Testing Tutorial: 5 Best Practices - VTEST Blog”, Blog, 2020 URL: https://www.vtestcorp.com/blog/unit-testing-best-practices/
- Flavio Company blog “More readable tests with Kotlin - Tengio”, Blog, 2016 URL: https://www.tengio.com/blog/more-readable-tests-with-kotlin/
- Ryan Cook “In Programming, is it worth to sacrifice some DRY-ness for …”, Other, 2017 URL: https://www.quora.com/In-Programming-is-it-worth-to-sacrifice-some-DRY-ness-for-code-readability-or-the-other-way-around
- Fernando Chovich Correa “How to write legible QA tests - Codacy - Blog”, Blog, 2019 URL: https://blog.codacy.com/how-to-write-legible-qa-tests/
- “Modeling readability to improve unit tests” In 2015 10th Joint Meeting of the European Software Engineering Conf. and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015 - Proceedings Association for Computing Machinery, Inc, 2015, pp. 107–118
- E. Daka, J.M. Rojas and G. Fraser “Generating unit tests with descriptive names or: Would you name your children thing1 and thing2?” In ISSTA 2017 - Proceedings of the 26th ACM SIGSOFT Int. Symposium on Software Testing and Analysis Association for Computing Machinery, Inc, 2017, pp. 57–67
- Thomas Deiß “Refactoring and converting a TTCN-2 test suite” In Int. Journal on Software Tools for Technology Transfer 10.4 Springer, 2008, pp. 347–352
- “An activity-based quality model for maintainability” In 2007 IEEE International Conference on Software Maintenance, 2007, pp. 184–193 IEEE
- “Rotten green tests” In 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE), 2019, pp. 500–511 IEEE
- Amey Dhoke “Do you really want moist test - AmeyDhoke’s blog”, Blog, 2009 URL: http://maverick-amey.blogspot.com/2009/05/do-you-really-want-moist-test.html
- Erik Dietrich “Test Readability: Best of All Worlds - DaedTech”, Blog, 2013 URL: https://daedtech.com/test-readability-best-of-all-worlds/
- Bas Dijkstra “Three practices for creating readable test code”, Blog, 2016 URL: https://www.ontestautomation.com/three-practices-for-creating-readable-test-code/
- Marc Duiker “Improving unit test readability: helper methods & named …”, Blog, 2016 URL: https://blog.marcduiker.nl/2016/06/01/improving-unit-test-readability-named-args.html
- Trevor Foucher Dustin Boswell “The Art of Readable Code” https://www.oreilly.com/library/view/the-art-of/9781449318482/ch14.html O’Reilly, 2012
- Urs Enzler “Clean Code Cheat Sheet - planetgeek.ch”, Cheatsheet, 2014 URL: https://www.planetgeek.ch/wp-content/uploads/2014/11/Clean-Code-V2.4.pdf
- Henning Femmer, Jakob Mund and Daniel Méndez Fernández “It’s the activities, stupid! a new perspective on RE quality” In 2015 IEEE/ACM 2nd International Workshop on Requirements Engineering and Testing, 2015, pp. 13–19 IEEE
- Javier Fernandes “Rethinking Testing Through Declarative Programming”, Blog, 2020 URL: https://betterprogramming.pub/rethinking-testing-through-declarative-programming-335897703bdd
- “Specification-Based testing in software engineering courses” In SIGCSE 2018 - Proc. of the 49th ACM Techn. Symposium on Computer Science Education 2018-January Association for Computing Machinery, Inc, 2018, pp. 800–805
- James Flournoy “Category: coverage - Pervasive Code”, Blog, 2008 URL: http://www.pervasivecode.com/blog/category/coverage/
- Michael Foord “30 best practices for software development and testing”, Magazine, 2017 URL: https://opensource.com/article/17/5/30-best-practices-software-development-and-testing
- “Exploiting common object usage in test case generation” In Proceedings - 4th IEEE Int. Conf. on Software Testing, Verification, and Validation, ICST 2011, 2011, pp. 80–89
- “Does Automated White-Box Test Generation Really Help Software Testers?” In Proceedings of the 2013 International Symposium on Software Testing and Analysis, ISSTA 2013 Lugano, Switzerland: Association for Computing Machinery, 2013, pp. 291–301 DOI: 10.1145/2483760.2483774
- “Developing, verifying, and maintaining high-quality automated test scripts” In IEEE Software 33.3 IEEE, 2016, pp. 68–75
- Vahid Garousi, Michael Felderer and Mika V Mäntylä “Guidelines for including grey literature and conducting multivocal literature reviews in software engineering” In Information and Software Technology 106 Elsevier, 2019, pp. 101–121
- “Smells in software test code: A survey of knowledge in industry and academia” In Journal of systems and software 138 Elsevier, 2018, pp. 52–81
- Tobias Goeschel “Writing Better Tests With JUnit - codecentric AG Blog”, Blog, 2016 URL: https://blog.codecentric.de/en/2016/01/writing-better-tests-junit/
- Jason Gorman “Readable Parameterized Tests - Codemanship’s Blog”, Blog, 2020 URL: https://codemanship.wordpress.com/2020/09/26/readable-parameterized-tests/
- “An empirical investigation on the readability of manual and generated test cases” In Proceedings of the Int. Conf. on Software Engineering IEEE Computer Society, 2018, pp. 348–351
- “Pizza versus pinsa: On the perception and measurability of unit test code quality” In 2020 IEEE Int. Conf. on Software Maintenance and Evolution (ICSME), 2020, pp. 336–347 IEEE
- Hugh Grigg “A simple, readable, meaningful test style with Jest”, Blog, 2020 URL: https://notestoself.dev/posts/simple-readable-meaningful-jest-test-style/
- Philip Hauer “Modern Best Practices for Testing in Java - Philipp Hauer’s Blog”, Blog, 2021 URL: https://phauer.com/2019/modern-best-practices-testing-java/
- Ev Haus “102. Whether or Not to Repeat Yourself: DRY, DAMP, or WET”, Podcast / transcript, 2020 URL: https://www.heroku.com/podcasts/codeish/102-whether-to-repeat-yourself-dry-damp-or-wet
- Brian Hnat “DRYer Tests - The Dumpster Fire Project”, Blog, 2020 URL: https://thedumpsterfireproject.com/dryer-tests
- Arho Huttunen “How to Make Your Tests Readable - Arho Huttunen”, Blog, 2021 URL: https://www.arhohuttunen.com/test-readability/
- Jason Jarrett “Fluent Specification Extensions - Developing on Staxmanade”, Blog, 2009 URL: https://staxmanade.com/2009/02/fluent-specification-extensions/
- Kristopher Johnson “Is duplicated code more tolerable in unit tests? - Stack Overflow”, Stackoverflow, 2008 URL: https://stackoverflow.com/questions/129693/is-duplicated-code-more-tolerable-in-unit-tests
- Petri Kainulainen “Writing Clean Tests - Petri Kainulainen”, Blog, 2014 URL: https://www.petrikainulainen.net/writing-clean-tests/
- Tuomas Kareinen “Readable tests - Tuomas Kareinen’s blog”, Blog, 2012 URL: https://tkareine.org/articles/readable-tests.html
- Vladimir Khorikov “DRY vs DAMP in Unit Tests - Enterprise Craftsmanship”, Blog, 2008 URL: https://enterprisecraftsmanship.com/posts/dry-damp-unit-tests/
- Pavneet Singh Kochhar, Xin Xia and David Lo “Practitioners’ views on good software testing practices” In 2019 IEEE/ACM 41st Int. Conf. on Software Engineering: Software Engineering in Practice (ICSE-SEIP), 2019, pp. 61–70 IEEE
- Lasse Koskela “Effective Unit Testing” https://livebook.manning.com/effective-unit-testing/chapter-4 Manning, 2013
- “Code smells and refactoring: A tertiary systematic review of challenges and observations” In Journal of Systems and Software 167 Elsevier, 2020, pp. 110610
- Adit Lal “Kotlin DSL - let’s express code in ”mini-language” - Part 5 of 5”, Blog, 2019 URL: https://www.aditlal.dev/kotlin-dsl-part-5/
- Roberto Latorre “A successful application of a Test-Driven Development strategy in the industrial environment” In Empirical Software Engineering 19.3 Springer, 2014, pp. 753–773
- Daniel Lehner “3 easy fixes for perfect unit test code - devmate”, Blog, 2021 URL: https://www.devmate.software/3-easy-fixes-for-perfect-unit-test-code/
- “Fluent vs Basic Assertions in Java: An Empirical Study” In 2018 11th International Conference on the Quality of Information and communications Technology (QUATIC), 2018, pp. 184–192 DOI: 10.1109/QUATIC.2018.00036
- “Fluent vs Basic Assertions in Java: An Empirical Study” In 2018 11th International Conference on the Quality of Information and Communications Technology (QUATIC), 2018, pp. 184–192 DOI: 10.1109/QUATIC.2018.00036
- “Automatically Documenting Unit Test Cases” In Proceedings - 2016 IEEE Int. Conf. on Software Testing, Verification and Validation, ICST 2016 Institute of ElectricalElectronics Engineers Inc., 2016, pp. 341–352
- “Aiding Comprehension of Unit Test Cases and Test Suites with Stereotype-Based Tagging” In Proceedings of the 26th Conference on Program Comprehension, 2018, pp. 52–63 DOI: 10.1145/3196321.3196339
- “On the quality of identifiers in test code” In Proceedings - 19th IEEE Int. Working Conf. on Source Code Analysis and Manipulation, SCAM 2019 Institute of ElectricalElectronics Engineers Inc., 2019, pp. 204–215
- Daniel Lindner “unit test - Schneide Blog”, Blog, 2013 URL: https://schneide.blog/tag/unit-test/
- Pawel Lipinski “or how to write tests so that they serve you well”, Presentation, 2013 URL: https://2013.jokerconf.com/presentations/03%5C_02%5C_lipinski%5C_pawel%5C_jokerconf-presentation.pdf
- NAIDELE MANJUNATH and OLIVIER DE MEULDER “No Code? No Problem — Writing Tests in Plain English - NYT …”, Blog, 2019 URL: https://open.nytimes.com/no-code-no-problem-writing-tests-in-plain-english-537827eaaa6e
- Robert C. Martin “Clean Code: Chapter 9” https://reee3.home.blog/2021/02/17/clean-code-9/ nan, 2021
- Phil McMinn, Muzammil Shahbaz and Mark Stevenson “Search-Based Test Input Generation for String Data Types Using the Results of Web Queries” In 2012 IEEE Fifth International Conference on Software Testing, Verification and Validation, 2012, pp. 141–150 DOI: 10.1109/ICST.2012.94
- Gerard Meszaros “xUnit test patterns: Refactoring test code” Pearson Education, 2007
- Roberto Minelli, Andrea Mocci and Michele Lanza “I know what you did last summer-an investigation of how developers spend their time” In 2015 IEEE 23rd Int. Conf. on Program Comprehension, 2015, pp. 25–35 IEEE
- “On the interplay between software testing and evolution and its effect on program comprehension” In Software evolution Springer, 2008, pp. 173–202
- Brooklin Myers “Readable test code matters. - Brooklin Myers”, Blog, 2021 URL: https://brooklinmyers.medium.com/readable-test-code-matters-e46cc5c411bb
- Mark Needham “TDD: Test DRYness - Mark Needham”, Blog, 2009 URL: https://www.markhneedham.com/blog/2009/01/30/tdd-test-dryness/
- “Evaluating code readability and legibility: An examination of human-centric studies” In 2020 IEEE Int. Conf. on Software Maintenance and Evolution (ICSME), 2020, pp. 348–359 IEEE
- “Automatic test case generation: What if test code quality matters?” In ISSTA 2016 - Proceedings of the 25th Int. Symposium on Software Testing and Analysis Association for Computing Machinery, Inc, 2016, pp. 130–141
- “Test smells 20 years later: detectability, validity, and reliability” In Empirical Software Engineering 27.7 Springer, 2022, pp. 170
- “The impact of test case summaries on bug fixing performance: An empirical investigation” In Proceedings - Int. Conf. on Software Engineering 14-22-May-2016 IEEE Computer Society, 2016, pp. 547–558
- Thomas Papendieck “Why Sometimes Unit Tests do More Harm than Good?”, Blog, 2017 URL: https://www.beyondjava.net/why-sometimes-unit-tests-do-more-harm-than-good
- Kai Petersen, Sairam Vakkalanka and Ludwik Kuzniarz “Guidelines for conducting systematic mapping studies in software engineering: An update” In Information and Software Technology 64 Elsevier, 2015, pp. 1–18
- Corina Pip “Clean Code in Tests: What, Why and How? - TestProject”, Blog, 2020 URL: https://blog.testproject.io/2020/04/22/clean-code-in-tests-what-why-and-how/
- Daryl Posnett, Abram Hindle and Premkumar Devanbu “A simpler model of software readability” In Proceedings of the 8th working conf. on mining software repositories, 2011, pp. 73–82
- Rudolf Ramler, Claus Klammer and Georg Buchgeher “Applying automated test case generation in industry: a retrospective” In 2018 IEEE Int. Conf. on Software Testing, Verification and Validation Workshops (ICSTW), 2018, pp. 364–369 IEEE
- Patrick Reagan “Keep Your Friends Close, But Your Test Data Closer - Viget”, Blog, 2009 URL: https://www.viget.com/articles/keep-your-friends-close-but-your-test-data-closer/
- Jon Reid “3 Reasons Why It’s Important to Refactor Tests - Quality Coding”, Blog, 2016 URL: https://qualitycoding.org/why-refactor-tests/
- “Using acceptance tests as a support for clarifying requirements: A series of experiments” In Information and Software Technology 51.2 Elsevier, 2009, pp. 270–283
- Jason Roberts “Diagnosing Failing Tests More Easily and Improving Test …”, Blog, 2019 URL: http://dontcodetired.com/blog/post/Diagnosing-Failing-Tests-More-Easily-and-Improving-Test-Code-Readability
- Jason Roberts “Improve Test Asserts with Shouldly - Visual Studio Magazine”, Magazine, 2015 URL: https://visualstudiomagazine.com/articles/2015/08/01/improve-test-asserts-with-shouldly.aspx
- Matheus Rodrigues “What Makes Good Unit Test? Readability - Matheus Rodrigues”, Blog, 2018 URL: https://matheus.ro/2018/01/15/makes-good-unit-test-readability/
- “Appropriate statistics for ordinal level data: Should we really be using t-test and Cohen’sd for evaluating group differences on the NSSE and other surveys” In annual meeting of the Florida Association of Institutional Research 177, 2006, pp. 34
- “DeepTC-Enhancer: Improving the Readability of Automatically Generated Tests” In Proceedings - 2020 35th IEEE/ACM Int. Conf on Automated Software Engineering, ASE 2020 Institute of ElectricalElectronics Engineers Inc., 2020, pp. 287–298
- Jan Van Ryswyck “Avoid Inheritance For Test Classes - Principal IT”, Blog, 2021 URL: https://principal-it.eu/2021/01/avoid-inheritance-for-test-classes/
- Anmol Sarna “Do you think your code is Perfect? Well, Think again.”, Blog, 2018 URL: https://blog.knoldus.com/do-you-think-your-code-is-perfect-well-think-again/
- Simone Scalabrino “Automatically Assessing and Improving Code Readability and Understandability” https://iris.unimol.it/retrieve/handle/11695/90885/92359/Tesi_S_Scalabrino.pdf, 2019
- “Automatically assessing code understandability: How far are we?” In 2017 32nd IEEE/ACM Int. Conf. on Automated Software Engineering (ASE), 2017, pp. 417–427 IEEE
- “Improving code readability models with textual features” In 2016 IEEE 24th Int. Conf. on Program Comprehension (ICPC), 2016, pp. 1–10 IEEE
- Carlos Schults “Unit Testing Best Practices: 9 to Ensure You Do It Right”, Blog, 2021 URL: https://www.testim.io/blog/unit-testing-best-practices/
- N. Setiani, R. Ferdiana and R. Hartanto “Developer’s Perspectives on Unit Test Cases Understandability” In Proceedings of the IEEE Int. Conf. on Software Engineering and Service Sciences, ICSESS 2021-August IEEE Computer Society, 2021, pp. 251–255
- N. Setiani, R. Ferdiana and R. Hartanto “Test case understandability model” In IEEE Access 8 Institute of ElectricalElectronics Engineers Inc., 2020, pp. 169036–169046
- “How Do Automatically Generated Unit Tests Influence Software Maintenance?” In 2018 IEEE 11th International Conference on Software Testing, Verification and Validation (ICST), 2018, pp. 250–261 DOI: 10.1109/ICST.2018.00033
- Jenny Shih “A Field Guide to Unit Testing: Readability”, Blog, 2020 URL: https://codecharms.me/posts/unit-testing-readability
- John Ferguson Smart “What makes a great test automation framework? - LinkedIn”, Blog, 2020 URL: https://www.linkedin.com/pulse/what-makes-great-test-automation-framework-john-ferguson-smart
- “Testing on the Toilet: Tests Too DRY? Make Them DAMP!”, Blog, 2019 URL: https://testing.googleblog.com/2019/12/testing-on-toilet-tests-too-dry-make.html
- “On the relation of test smells to software code quality” In 2018 IEEE international conference on software maintenance and evolution (ICSME), 2018, pp. 1–12 IEEE
- “Test-case quality–understanding practitioners’ perspectives” In Int. Conf. on Product-Focused Software Process Improvement, 2019, pp. 37–52 Springer
- “An empirical investigation into the nature of test smells” In Proceedings of the 31st IEEE/ACM international conference on automated software engineering, 2016, pp. 4–15
- Arash Vahabzadeh, Amin Milani Fard and Ali Mesbah “An empirical study of bugs in test code” In 2015 IEEE international conference on software maintenance and evolution (ICSME), 2015, pp. 101–110 IEEE
- “Refactoring test code” In Proceedings of the 2nd international conference on extreme programming and flexible processes in software engineering (XP2001), 2001, pp. 92–95 Citeseer
- Stephen Vance “Quality Code: Software Testing Principles, Practices, And …” https://vdoc.pub/documents/quality-code-software-testing-principles-practices-and-patterns-781g7idb34f0 nan, 2013
- “Operationalised product quality models and assessment: The Quamoco approach” In Information and Software Technology 62 Elsevier, 2015, pp. 101–123
- “The Quamoco product quality modelling and assessment approach” In 2012 34th international conference on software engineering (ICSE), 2012, pp. 1133–1142 IEEE
- Dietmar Winkler, Pirmin Urbanke and Rudolf Ramler “Data set for ”Investigating the Readability of Test Code: Combining Scientific and Practical Views”” TU Wien, Data Set, 2023 DOI: 10.48436/w4q8v-28695
- Dietmar Winkler, Pirmin Urbanke and Rudolf Ramler “What do we know about readability of test code? - A Systematic Mapping Study” In Proceedings of the 5th Workshop on Validation, Analysis, and Evolution of Software Tests, in conjunction with the 29th IEEE International Conference on Software Analysis, Evolution, and Reengineering (SANER), 2021
- “Experimentation in software engineering” Springer Science & Business Media, 2012
- Burak Yetistiren, Isik Ozsoy and Eray Tuzun “Assessing the quality of GitHub copilot’s code generation” In Proceedings of the 18th International Conference on Predictive Models and Data Analytics in Software Engineering, 2022, pp. 62–71
- T. Yonekubo “Readable Test Code - Medium”, Blog, 2021 URL: https://medium.com/@t-yonekubo/readable-test-code-cad8a7babc7b
- Vahid Garousi Yusifoğlu, Yasaman Amannejad and Aysu Betin Can “Software test-code engineering: A systematic mapping” In Information and Software Technology 58 Elsevier, 2015, pp. 123–147
- “Studying the co-evolution of production and test code in open source and industrial developer test processes through repository mining” In Empirical Software Engineering 16.3 Springer, 2011, pp. 325–364
- B. Zhang, E. Hill and J. Clause “Towards automatically generating descriptive names for unit tests” In ASE 2016 - Proceedings of the 31st IEEE/ACM Int. Conf. on Automated Software Engineering Association for Computing Machinery, Inc, 2016, pp. 625–636
- Gil Zilberfeld “Test Attribute #2: Readability - Java Code Geeks”, Blog, 2014 URL: https://www.javacodegeeks.com/2014/07/test-attribute-2-readability.html
- Dietmar Winkler (4 papers)
- Pirmin Urbanke (1 paper)
- Rudolf Ramler (14 papers)