Dmitry Timofeev

@vitvakatu Would it make sense to update these tests (which one can be enabled already?) by changing the classpath in use to something else (e.g., the app classpath)?

Reviewers, see https://jira.bf.local/browse/ECR-3918

There are some warnings during `npm install`. @KateNegrienko , @boguslavsky , is it possible to fix them here or is it better to do in a separate PR? ``` [WARNING]...

WIP until `npm install` does not make changes when not requested

Let me share my experience with parameterized tests in the new JUnit. Hope that helps to clarify the uses cases and requirements for Parameterized classes. I think that this feature...

@marcphilipp , I can think of a class-level annotation with `name` attribute, or, if users need more flexibility, let them provide an instance method returning a test description + a...

> How about we annotate fields/method parameters with `@Parameter(index=0, optional=true)` (optional should be false by default) and inject null for non-parameterized tests? Won't that be hard to explain to users...

I've updated the questions section in the issue description, based on the feedback on a PoC PR. As a user of this feature, I'd expect the following: 1. `CsvSource` &...

@sbrannen, Thank you for taking a look at the issue! >> CsvSource & CsvFileSource with an optional attribute and an empty description by default. > I think that would be...

As an alternative to `@CsvXSource#descriptionColumnIndex` we may add an enum specifying where to get description from `@CsvXSource#description = Column.{FIRST, LAST, NONE}`. Less flexible, but easier to deal with in providers...