I'm starting to see that tests start running too soon before the application started. Increasing the wait time to a bigger number.
It will increase the test runtime of each selfhost variation by a couple more seconds, but it will increase the reliability.
A couple of selfhost variations are failing on some of the new CI machines. While trying to reproduce I see that the klr.exe processes are lauching fine. But the tests fail for a couple of self-host variations. Only suspicion is this time out as the client gets a socket exception. It is possible that client is making a request before the server is ready.
This does not include the deployment helper on mono. So the test needs to point to a statically deployed application url to run.
There are some bugs in mono Httpclient like in case of 302's RequestMessage's Uri not modified, cookies not cleared in cookie container etc. I will file bugs in mono on those and this is a work around until then.
There is still more work and refactoring. This is a first step.
- can't be done as a unit test because `k.cmd test` doesn't write assemblies for referenced projects
- instead support extending the "test" target in builds
To enable this in a repo, add the following to the makefile.shade file:
```
#xml-docs-test target='test'
k-xml-docs-test
```
Example output with one syntax error and one invalid reference:
```
info: Target xml-docs-test
warn: Invalid documentation syntax in src\Microsoft.AspNet.Mvc.Core\bin\debug\net45\Microsoft.AspNet.Mvc.Core.xml
warn: 3170: <!-- Badly formed XML comment ignored for member "T:Microsoft.AspNet.Mvc.Rendering.HtmlHelper" -->
warn: 3203: If the object is already an <see cref="!:IDictionaries<string, object>"/> instance, then it is
```
Chris Ross
Praburaj
Levi B
Pranav K
ajcvickers
harshgMSFT
Louis DeJardin
David Fowler
dougbu