emilssolmanis commented on pull request #14272: URL: https://github.com/apache/beam/pull/14272#issuecomment-820518884
@kennknowles @rmannibucau sorry for the lack of response, been a bit snowed under at work. So 2 points I can extract from the conversation so far: 1. the dominant version of Junit and all that stems from there -- I think this would require data, and I'm not sure we have that available. I'm with @rmannibucau in that most new projects will start in Jupiter, and most old projects stay in Junit4 purely by inertia. I don't think there's a right or wrong solution, and supporting either seems simple enough, at least from what I've seen so far, so being independent of the testing framework sounds like a good thing to aim for and should be achievable. 2. > We export our "Beam Model Compliance" test suite via JUnit4 category. So it is a critical breaking change to do that differently. Not sure I follow, is this documented somewhere I can have a read about? Mainly I don't immediately understand how this would affect clients. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
