About unit testing and UI standardization to simplify UI scaffolding code

[shlxue]

A JUnit 5.x extension for hop plugins: https://github.com/shlxue/hop-tools

In the past month, we have been using our free time to migrate 100+ kettle plugins.

This is a very arduous task. It is not about upgrading these plugins itself, but about how to better integrate hop with our existing application system. We are still trying

We have a sample testing module for kettle plugins: pdi-plugin-testing for plugin functional testing.
But with the introduction of beam engine in hop, we are considering whether we need to refactor the implementation here

Now：
the junit extension: only a test template is implemented to detect whether the plugin dialog is standardized

If possible, I would like to add the testing module to hop repository

[shlxue]

@mattcasters @hansva @bamaer

[dmainou]

How does this differs/is better than the current implementation of unit tests?
https://hop.apache.org/manual/latest/pipeline/pipeline-unit-testing.html