server assumes only scala_test targets - more flexibility needed about bazel-bsp HOT 6 CLOSED

easy part done in #101

from bazel-bsp.

re hard part- do you have any thoughts? do you need more info on how the mechanism works?
[Context- I wrote the rules_scala junit discovery mechanism]

from bazel-bsp.

hi! thank you for contact.
the main concern is whether it is possible to obtain an information about tests main classes without executing them? in our server we need to return such information to the client. One solution is simply implementing a test discovery mechanism on our side, but it seems a bit wrong.

from bazel-bsp.

Few questions:

1. Why is this needed?
2. Can this be iterative and while they're being executed?
3. How cheap/costly should/can this be?

from bazel-bsp.

1. Why is this needed?

bsp specification - this information might be useful for a client to for example display run test icon.

2. Can this be iterative and while they're being executed?

this information is usually fetched during importing - after that a client can use this information to ask server to execute a given test

3. How cheap/costly should/can this be?

well, as least costly as possible - there are endpoints that build the project, which could potentially be very costly. So, I believe that building is a limit - so executing tests isn't an option

from bazel-bsp.

first point done, second moved: https://youtrack.jetbrains.com/issue/BAZEL-41

from bazel-bsp.