Nikolay Borisenko
Nikolay Borisenko
It doesn't work on my side. ``` Message: OneTimeSetUp: System.ArgumentNullException : Value cannot be null. (Parameter 'path1') Stack Trace: ArgumentNullException.Throw(String paramName) Path.Combine(String path1, String path2, String path3) TestWebServer.Start() line 80...
The same for test/launch name. API requires length 1..256
https://github.com/reportportal/client-net/issues/57 and there is limitation for attributes value. I propose to get rid of any kind of string length limitations on server side.
At build phase - yes. An user is able to pull SM binaries he needs (even cached). If user builds his project for `win64` - we can pull appropriate SM...
What about the following report: ```xml ... result (with output, failures) ... result (with output, failures) ``` And runner generates events - `start-test-attempt` when new test attempt started - `test-case-attempt`...
@CharliePoole @rprouse, it's seems I am able to contribute here. Need your vision of what we want to do to resolve it.
Just for advanced reporting. It would be amazing if user is able to see the details of tests execution flow. Retry/Repeat feature is popular in UI testing to make tests...
This PR can be considered as actual when it starts using of our BiDi implementation. For me it is interesting how we are going to spread BiDi Driver instance across...
Now we have own implementation.
And ask me, together we will find the best approach.