The scope of current implementation of the org.apache.pulsar.tests.integration.functions.PulsarFunctionsTest class is too broad, it is responsible for the end to end testing of Pulsar Functions, Pulsar Sources, and Pulsar Sinks. These test suites should be implemented in different test classes altogether since they test fundamentally different things.
Is your enhancement request related to a problem? Please describe.
No functional problem per se, just software maintainability. It is very difficult to maintain a class with 2700 lines of code that is responsible for performing multiple tests.
Describe the solution you'd like
Break the class into separate classes based on the type of Function they are testing, e.g. Functions, Sources, Sinks, etc.
Describe alternatives you've considered
Leaving the code as-is
Additional context
The scope of current implementation of the org.apache.pulsar.tests.integration.functions.PulsarFunctionsTest class is too broad, it is responsible for the end to end testing of Pulsar Functions, Pulsar Sources, and Pulsar Sinks. These test suites should be implemented in different test classes altogether since they test fundamentally different things.
Is your enhancement request related to a problem? Please describe.
No functional problem per se, just software maintainability. It is very difficult to maintain a class with 2700 lines of code that is responsible for performing multiple tests.
Describe the solution you'd like
Break the class into separate classes based on the type of Function they are testing, e.g. Functions, Sources, Sinks, etc.
Describe alternatives you've considered
Leaving the code as-is
Additional context