You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The single most important feature that must always work in Squirrel is: update. As long as update works we can fix any bug that might be introduced along the way.
Therefore we need a robust set of integration tests that validate all manner of updates supported by Squirrel.
The end result should be confidence that any change submitted will be able to update old versions of Squirrel and be updated by future versions of Squirrel.
The text was updated successfully, but these errors were encountered:
It would be nice if the issue with the version updated not working when closing the application while squirrel update is running be dealt with the official squirrel release.
Can you share an update on the plans to improve integrations tests? How can we help? Is the plan to create an automated test suite that runs using AzureDevops/GithubActions? Happy to help if you can give some direction.
The single most important feature that must always work in Squirrel is: update. As long as update works we can fix any bug that might be introduced along the way.
Therefore we need a robust set of integration tests that validate all manner of updates supported by Squirrel.
The end result should be confidence that any change submitted will be able to update old versions of Squirrel and be updated by future versions of Squirrel.
The text was updated successfully, but these errors were encountered: