TyrantLucifer commented on issue #2691: URL: https://github.com/apache/incubator-seatunnel/issues/2691#issuecomment-1246765139
> > > With the addition of `SeaTunnel Engine` every connector need add e2e-test for three engine. This is a difficult and boring job for developers. So I think it's time to add an automated test framework for SeaTunnel. The test framework need support some key features: > > > > > > 1. Automatically generate job configuration files based on the information provided by the connector. If the connector is a source connector, we need to determine whether a sink connector already exists. If already have a sink connector, we need generate two jobs. This first job is to generate test data, it looks like `FakeSource -> XxxSink` and another job is `XxxSource -> AssertSink`. On the other handle, If the connector is a sink connector, we need to determine whether a source connector already exists. If already have a source connector, we need generate two jobs. One of the job is `FakeSource->XxxSink` and another job is `XxxSource->AssertSink`. > > > 2. Test all engines automatically. The test framework need run the jobs in all of the engine SeaTunnel supported now. > > > > > > @hailin0 @CalvinKirs @getChan @531651225 @TyrantLucifer @2013650523 @chessplay Do you have any suggestions？ > > > > > > This is a good suggestion, but it can be difficult to implement. There will be different configuration files and parameters for different connectors, and different connectors will require different docker images. I don't really understand if the program automatically generates the configuration file or if the whole process code has to be generated automatically. > > The initialization of DataSources is the same for engin such as Spark,Flink,ST-engine. Yep, I agree with you, but we still have to develop the code for each connector manually, it's not automatically generated. I can understand if it is to unify the process, but I can't understand the automatic generation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
