Jakub Jareš
Jakub Jareš
Personally I don't care that much about the exact definition of `--timeout` at that point my tests are already hanging for some unreasonable time that is much longer than normal...
Also who uploads the data when we crash in (single exe) myTests.exe mode? Is that via upload file output in azdo? Or requires a post-step in pipeline? https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash#upload-upload-an-artifact
@engyebrahim please have a look.
@fhnaseer to help, and review the decisions taken in the Code Coverage package, with shipping the dll.
We had similar request in vstest (which I cannot find right now), but the idea there was to do discovery, and say e.g. run at max 1000 tests per assembly....
> Or maybe what we should fix here is the ability to run single test case altogether. Yes that seems like a good problem to solve. But I can also...
What part do you agree with? :) The proposal from Youssef will hide it from anywhere, but then you say you prefer showing the whole stack. The naming convention that...
btw we check if the file is on disk, so we are the ones that see it point to assertion details, users won't
Yeah that is what I was afraid of. I see many many of repos checking out "infrastructure" + code. Need to see what impact it has. There is no urgency...
I think this needs a lot of design. For example the textual diff feels like it should be built in, without any user action. It also feels like in cases...