Sometimes the first request to the application results in exceptions like 'No connection could be made because the target machine actively refused it'. Adding a retry to mitigate that.
1. Changing the SigninAsAuthenticationType to a variable to avoid failures when the value changes.
2. Adding a Scripts folder like default VS projects.
3. Adding version numbers to GAC assemblies in the test project.
4. Adding a check for pack-exclude.
1. Moving framework assembly references to frameworkassemblies node.
Moving the framework references Removing the RunOnMono flag on Ntlm tests as it never runs on mono
2. Deleted a space from the batch file
3. Adding some pack-exclude items
4. Some general test cleanup.
Native module is still not fully working with automation. Will be avilable shortly.
The test project will undergo a little bit of refactoring and cleanup as well shortly.
Social mock tests are not executed right now due to 2 issues:
1. Identity extensions related to Social are not in yet.
2. Helios currently does not support loading of environment based startup class.
When a new album is created in the store a notification is posted to all the connected browsers using SignalR.
Also added automation for the signalR hubs.
There is still some UI formatting improvements required in the way new arrivals are displayed. Will fix it in future checkins.
1. This contains the new manage controller with a bunch of features like 2 factor auth
Some of the features are not enabled yet. But this is to set a baseline with update3 templates.
Automation to come up in future as more identity extensions are available.
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.
Praburaj
Suhas Joshi
Victor Hurdugaci
Hao Kung
Chris Ross
Wei Wang
Pranav K
Brice Lambson
David Fowler