You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The method definition of killingTest can contain commas, in case the method has parameters.
These commas break CSV parsing, as they are interpreted as starting a new column.
Steps to reproduce
Simple example of code that will produce a breaking killinTest:
@ParameterizedTest@CsvSource({
"test,test",
})
publicvoidtestMethod(Stringparm1, Stringparam2 ) {
// code left out
}
This would generate the following definition for killingTest
testMethod(java.lang.String, java.lang.String)
Notice the comma.
What I expect to happen
That the method definition of the killingTest is quoted, as not to break CSV parsing.
What actually happens
The killingTest is written to the CSV report as-is, breaking CSV parsing.
The text was updated successfully, but these errors were encountered:
Summary
The method definition of
killingTest
can contain commas, in case the method has parameters.These commas break CSV parsing, as they are interpreted as starting a new column.
Steps to reproduce
Simple example of code that will produce a breaking
killinTest
:This would generate the following definition for
killingTest
testMethod(java.lang.String, java.lang.String)
Notice the comma.
What I expect to happen
That the method definition of the
killingTest
is quoted, as not to break CSV parsing.What actually happens
The
killingTest
is written to the CSV report as-is, breaking CSV parsing.The text was updated successfully, but these errors were encountered: