You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if we run connectivity tests concurrently (using --test-concurrency flag) JUnit report will be created for each test namespace of K8S cluster.
I think it makes more sense to have a single JUnit report that collects all the data.
Run connectivity tests concurrently with JUnit report:
cilium connectivity test --test-concurrency=3 --junit-file report.xml
can you provide the steps to reproduce this issue? Example: a command run and the list of files generated.
can you provide an example of a single JUnit test where multiple tests run in sequence?
is the expectation of this bug report to generate a single XML file?
a. if so, have we asked for feedback from the people that consume the generated reports?
b. what approach would you recommend? sending the output of a concurrent test via a channel for all inputs to be written on a single file?
What would a single JUnit report file look like? Let's say 5 concurrent go-routines and some tests in one of the go-routines fails. Is the expectation that all tests will run and the single XML file will show the tests that failed? Or is it expected that as soon as a test fails (on any of the go-routines), no further tests will run?
Currently, if we run connectivity tests concurrently (using
--test-concurrency
flag) JUnit report will be created for each test namespace of K8S cluster.I think it makes more sense to have a single JUnit report that collects all the data.
Run connectivity tests concurrently with JUnit report:
Single file JUnit report examples
The text was updated successfully, but these errors were encountered: