- Use Visual Studio 2022
- Use an Azure Pipelines image which has Visual Studio 2022 installed
- Use the v143 C++ build tools
- Use the Windows SDK version 22000
- Raise the minimum platform version to 17763
- As a consequence of this change, we will use the "msix" file extension instead of "appx" for our packages
- Update UI tests from .NET Core 2.1 to .NET Core 3.1
* Use different formatter for different currency
* Add functional tests for currency fraction digit format
* Revert "Add functional tests for currency fraction digit format"
This reverts commit bd8aab33847425f4dcfd0d76ce310c918729b2fd.
* Add TestCurrencyFormattingLogic in UnitConverterViewModelUnitTests
* Fix InitializeMultipleConverterTest
* Add comment for a line of code
* Add default case for switch in ConvertToLocalizedString
* Remove trailing decimal
Disable decimal input if maxFractionDigits is 0
Fix input may be blocked after switched active
* Fix: UpdateIsDecimalEnabled should do nothing for non-currency converter
* Remove unnecessary SetValue method
* Add a comment
* Add functional UI Tests for currency converter
Reset currency before tests
Fix: input is blocked after switching to currency with less fractional digits
* Set Priority=0 for currency format related tests
* Truncate digits in display value after switcing
To fix incorrect result after switching currency with less fractional digits
* Fixes issue #1409
Copy pasting into Currency locks the editor.
Skipping the validation of full editor lock when backspace or clear button is clicked.
* Adding code review feedback.
* Adding code review feedback.
* Take the high boundary of signed negative values into account
* UI unit tests for the Copy/Paste menu are added
* Additional corner case for the number notations without negative values
* Switching from Difference between dates to Add or subtract dates ignores the first date field
https://github.com/microsoft/calculator/issues/254
Date field needs to persist across Date Difference and Add/Subtract From Date Mode.
* Update DateCalculator.xaml.cpp
Addressing review comments (white space, small code refactor), also found a null pointer exception during testing, this fix addresses that as well.
* Issue 935 - Updates to Scientific/Graphing Keypad
Update Scientific and Graphing keyboard layouts to expose square root button at the top level
* Updated ScientificModeFunctionalTests/SmokeTest_Cube()
Updated broken test to work with changes.
* Maximize window during setup, and added divide by zero error test
* Added Error_CubedNegativeNumber test and AOT buttons
* Made Added AoT Tests and test are faster
* Hotkey and Mouse Input BVT Test added, Memory Test started
* Started Aligning BVTs with manual tests. Added TC23466694, TC17416429, and TC17416884, and a test to switching mode test
* Basic Scientific Mode Functional Test Tests
* Added history panel test, and history flyout test for Standard calculator, and added the supporting framework
* Added some functional tests for Scientific mode.
* Basic Scientific Mode functional tests, added solution to set Angle Operator button correctly.
* Created functions to resize the app to display history panel, to display history button, display memory panel, and memory button. Then I applied them to reduce areas with rewritten code, and to help with over all test stability and speed.
* I added the trigonometry functional tests
* Pull from latetest master, and retargeted solution
* Added a GetCalculatorWindowPostion function, when resizing window to show history/memory label, set window position to (0,0), and the same when resizing KOT calculator. This will make tests more stable by keeping calculator on screen. It will also help with any testing that may require tracking the apps postion. To fix a test failure, changed function from ResizeToDiplayHistoryButton to ResizeToNotDisplayHistoryLabel.
* Sorted Using Statements, modified .gitignore to ignore **src/out, etc...
* Merged CalcMemoryFlyout into MemoryPanel, and deleted CalcMemoryFlyout. Merged CalcHistoryFlyout in HistoryPanel, and deleted CalcMemory. Created GlobalCalculatorUI.cs. Updated tests to work with these changes.
* hold on to changes
* Changed all KOT to Aot,
Removed equal button click in Test Cleanup/History method uses page source,
Removed extra line in Calculator.vcxproj.filters, Removed Try/Catch in the ClearHistory method
* Removed unused elses
Added CalculatorResults class
Added StandardAoTCalculatorPage
Removed manual test case info in the comments
* - In test framework, where it worked,
made some elements private
- Created EnsureCalculatorHasFocus() in GlobalCalculatorUI.cs
- Due to new classes, moved some methods to more correct classes
- Moved "page.MemoryPanel.ResizeWindowToDiplayMemoryLabel();" from
SetupCalculatorSession() to ClassInitialize()
* Sorted Using
* Updating fork from latest master
* Don't stand so
* Minor edits, fixing things from PR comments
* Merging scientific and standard mode tests, minor merge conflict fixes
* Method work
- Created ResizeAoTWindowToDiplayInvertButton()
- Applied to test method AoT_ErrorMessage()
- Added page.ScientificOperators.ResetFEButton(fEButtonState.Normal);
to TestIniT in ScientificModeFunctionalTests
- Fixed if statement in public void ResetFEButton(fEButtonState value)
* Added StandardOperatorsPanel and removed duplicated code
* Created tests for Programmer mode, fixed a typo that appeared in multiple locations
* Fixed clear entry not working in Scientific test
* This time I really fixed the problem with clear memory not being found every time
* Revert shared changes
* Rebased onto master and resolved conflicts
* Fixed the 15 second delay on every scientific mode test
* Greatly shortened bitflipkeypad test
Co-authored-by: Crystal Edwards (Insight Global Inc) <v-credwa@microsoft.com>
Co-authored-by: Crystal Edwards <45952655+v-credwa@users.noreply.github.com>
The CalculatorUITestFramework project does not need Microsoft.NET.Test.Sdk or MSTest.TestAdapter. These dependencies are needed only in the project which produces the actual test assembly (in our case, the CalculatorUITests project).
Removing these resolves a build warning, since the test adapter package does not target .NET Standard.
Fixes#462
- Add x64 and x86 UI tests to the release builds (internal builds for the store)
- UI tests now accept the target app ID as a parameter in the runsettings file
- Added the CalculatorUIFramework to handle the WinAppDriver logic.
- Added Standard Mode smoke tests and BVTs to the CalculatorUITests project.
- Removed old UI tests that did not use the CalculatorUIFramework
