Gary Chan

@dchristensen - thoughts? I see that you were the last one to touch _AllReady.ScenarioTest.fsproj_.

Found another issue related to **AllReady.ScenarioTest** project. It is missing a dependency on the **allReady** project. Fixed - PR to come.

@dchristensen I agree with you. My primary goal right now is simply to get the web part of the solution building and passing unit tests. I messaged @stevejgordon on Slack...

I've changed the description of this issue so it encompasses all the issues I've discovered. I was initially just having issues getting **AllReady.ScenarioTest** to build consistently. 1. **AllReady.ScenarioTest** built before...

Attempted to isolate a fix for this issue alone - PR #2350. Build test showed  The initial error is a timeout. This did not occur when the test was...

Temporarily disabled the two broken tests and committed -https://github.com/HTBox/allReady/pull/2350/commits/3bec7257809fd0d88d85e5aba68e0551bb2d6588. The [results](https://ci.appveyor.com/project/HTBox/allready/builds/22590585) still show a timeout at line 646. Now looking into [extending the timeouts in Canopy](https://lefthandedgoat.github.io/canopy/configuration.html).

After multiple trial an error, I was able to reproduce the problem found in AppVeyor. The cause appears to be because a critical NPM package was not being restored in...

> After multiple trial an error, I was able to reproduce the problem found in AppVeyor. The cause appears to be because a critical NPM package was not being restored...

Finally figured it out.  Will create a PR with the fix.

I've abandoned a possible fix in PR #2350 and closed. I did learn a few things and included the fix as part of PR #2352. - Upgraded the _Scenario.Test_ project...