A computer-implemented method for generating a human-readable, language-independent stack trace summary (125, 425), the method comprising: receiving a plurality of error reports (115, 405), each error report (115, 405) including a language-dependent stack trace generated in response to a software test failure of a code implemented in a specific programing language and a plurality of metadata, wherein the generated language-dependent stack trace includes one or more frames; generating a language-independent stack trace summary (125, 425) by processing each frame of the language-dependent stack trace regardless of the specific programing language, wherein the processing includes at least two of: removing line number values from each of the one or more frames, removing column number values from each of the one or more frames, collapsing one or more file names identified in each of the one or more frames, removing spaces from each of the one or more frames, and removing special characters from each of the one or more frames; outputting the generated language-independent stack trace summary (125, 425); generating a cluster of language-independent stack trace summaries, wherein the cluster of stack trace summaries includes similar language-independent stack trace summaries, wherein the generating of the cluster comprises determining the language-independent stack trace summaries are similar by comparing error types, error messages, and file names identified in each of one or more frames included in each of the language-independent stack trace summaries to one another; associating the cluster with a unique software test failure; and assigning the cluster and the unique software test failure to development resources for reviewing the code. receiving a plurality of error reports (115, 405), each error report (115, 405) including a language-dependent stack trace generated in response to a software test failure of a code implemented in a specific programing language and a plurality of metadata, wherein the generated language-dependent stack trace includes one or more frames; generating a language-independent stack trace summary (125, 425) by processing each frame of the language-dependent stack trace regardless of the specific programing language, wherein the processing includes at least two of: removing line number values from each of the one or more frames, removing column number values from each of the one or more frames, collapsing one or more file names identified in each of the one or more frames, removing spaces from each of the one or more frames, and removing special characters from each of the one or more frames; removing line number values from each of the one or more frames, removing column number values from each of the one or more frames, collapsing one or more file names identified in each of the one or more frames, removing spaces from each of the one or more frames, and removing special characters from each of the one or more frames; outputting the generated language-independent stack trace summary (125, 425); generating a cluster of language-independent stack trace summaries, wherein the cluster of stack trace summaries includes similar language-independent stack trace summaries, wherein the generating of the cluster comprises determining the language-independent stack trace summaries are similar by comparing error types, error messages, and file names identified in each of one or more frames included in each of the language-independent stack trace summaries to one another; associating the cluster with a unique software test failure; and assigning the cluster and the unique software test failure to development resources for reviewing the code.