Analyzing student code after introducing portfolio assessment and automated testing
Per Lauvås · 2015
Teaching students how to write program code is difficult. Teaching students how to write good program code is even harder. When educating future programmers, it is of great importance that they know the concept of technical debt, and how good code will reduce technical debt. In this paper I show you how the quality of student code changes when introducing two new aspects in a programming course; portfolio assessment and test coverage. Code produced from two succeeding classes was analyzed using an analyzing tool called SonarQube. The results indicate that both portfolio assessment and automated tests improve the quality of the code, but not with the same effect.