rustworthy commented on issue #2517: URL: https://github.com/apache/iggy/issues/2517#issuecomment-3693237263
I do not think they should (but they of course can), since the e2e test suite is essentially another application sending commands to web driver and inspecting responses, right? And so why should this use the same language as the one powering the user interfaces? Maybe it's easier to adjust tests whenever one is working on the web UI code w/o switching to a different language. Also maybe colocation makes it easier to arrange for e2e tests to be launched whenever changes are detected in the web namespace. But for me personally neither of these arguments is a big deal or strong enough to not use my language of choice and it's ecosystem. But that's me and also there may be other arguments. In other projects, using Rust and hosting tests alongside the server allowed me to re-use the database drivers (e.g. sqlx) to inspect what we persisted. Also launching a dedicated backend (server) from the test context setup (for better isolation) is very straightforward when they use the same language :) -- 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]
