Use registered ParameterResolver(s) when invoking @MethodSource factory methods

[nishant-vashisth]

Currently, the MethodSource methods are supposed to not have any parameters, however, it'll help to have parameters to be resolved in these methods if registered similar to Before/After methods.

Along with #2190, this will give access to MethodSource methods to possibly use Extension.Store and store any initialized details, which could be purged in @AfterAll methods

Also, in case of creating dynamic tests using details from a resolved Object, ParameterResolver can enhance abilities of MethodSource by a fair bit.

Currently, the way to achieve the same is to have a class implementing ArgumentsProvider and possibly manage the value of the object there, or have it in the MethodSource method itself statically initializing it in test class.

[marcphilipp]

@nishantvas Could you please add a concrete code example?

[nishant-vashisth]

static Stream<Arguments> createElementArguments(){
    // The below function is basically a wrapped function which my ParameterResolver also calls
    MyElement elem  = MyElement.staticInitializer(); // Possibly with test specific arguments
    return Stream.of(createArguments(elem));
  }

  // This way, I can have a common place to initialize / resolve the MyElement type class
  static Stream<Arguments> createElementArgumentsFromResolver(MyElement element){
    return Stream.of(createArguments(elem));
  }

  @MethodSource("createElementArguments")
  @ParameterizedTest(name = "Do Something With Element {0} and expect {2}")
  void testArguments(
      String test,
      MyElemment element,
      int expectedCode) {
    given()
        .request()
          .body(element)
        .then()
          .expect()
          .statusCode(expectedCode)
        .request()
        .put("/path/to/put");
  }

@marcphilipp , I'm suggesting something like this, so that The code to resolve MyElement type can stay standardised or perhaps also secure by delegating via ParameterResolvers

[marcphilipp]

@nishantvas Thanks!

@sbrannen Would you mind adding an example of the @BeforeTransaction use case in Spring?