-
Notifications
You must be signed in to change notification settings - Fork 462
Checklist: Before Release
sibille edited this page Jun 1, 2021
·
10 revisions
- Ensure VB Templates are in sync
- Run https://github.com/Microsoft/WindowsTemplateStudio/blob/dev/_utils/Synchronize-Files-Used-By-VisualBasic-Templates.ps1 to make sure that any non-code changes made to C# templates are copied to their VB equivalent
- Run https://github.com/Microsoft/WindowsTemplateStudio/blob/dev/_utils/List-CSharp-Templates-Without-VisualBasic-Equivalents.ps1 to ensure that VB versions of any new C# templates have been created.
- Run the tests
EnsureProjectsGeneratedWithDifferentLanguagesAreEquivalent_G1_Async
andEnsureProjectsGeneratedWithDifferentLanguagesAreEquivalent_G2_Async
(all in the Templates.Test project) as these are not part of any automated process. They look for differences in apps generated with the same pages/features built with C# & VB.
- Run other manual tests:
- CaptureWizardScreenshots
- ExternalLinksTests
- ResourceUsageTests
- TemplateJsonLanguageConsistencyTests
- VisualComparisonTests
- Check if nuget packages need updates (templates and extension code) and revisit external issues, to see whats fixed.
- Ensure Pre-Release available and tested
- Ensure Pre-Release build has run successfully & last interactive tests has passed.
- Ensure Pre-release version has been delivered
- Use Pre-Release Feed to install latest Pre-Release generated (https://www.myget.org/F/windows-template-studio-prerelease/vsix/)
- Test extension on current windows version and previous version
- Test New Project
- Test Right click
- Test breaking change messages
- Test installation on different VS versions + concurrent installation)
- Verify docs are complete + all new pages and features included
- Publish generated app to store and install and test from there