ADD file via upload

ApplicationArchitecture.md

@@ -0,0 +1,205 @@
+# Application Architecture
+
+Windows Calculator is a [C++/CX][C++/CX] application, built for the Universal Windows Platform ([UWP][What is UWP?]).
+Calculator uses the [XAML][XAML Overview] UI framework, and the project follows the Model-View-ViewModel ([MVVM][MVVM])
+design pattern. This document discusses each of the layers and how they are related to the three Visual Studio projects
+that build into the final Calculator application.
+
+--------------------
+## Table of Contents
+
+* [View](#view)
+    * [VisualStates](#visualstates)
+    * [Data-Binding](#data-binding)
+* [ViewModel](#viewmodel)
+    * [PropertyChanged Events](#propertychanged-events)
+* [Model](#model)
+
+--------------------
+
+## View
+
+The View layer is contained in the [Calculator project][Calculator folder]. This project contains mostly XAML files
+and various custom controls that support the UI. [App.xaml][App.xaml] contains many of the [static][StaticResource] and
+[theme][ThemeResource] resources that the other XAML files will reference. Its code-behind file, [App.xaml.cs][App.xaml.cs],
+contains the main entry point to the application. On startup, it navigates to the main page.
+
+```C#
+rootFrame.Navigate(typeof(MainPage), argument)
+```
+
+In Calculator, there is only one concrete [Page][Page] class: [MainPage.xaml][MainPage.xaml]. `MainPage` is the root
+container for all the other application UI elements.  As you can see, there's not much content. `MainPage` uses a
+`NavigationView` control to display the toggleable navigation menu, and empty containers for delay-loaded UI elements.
+Of the many modes that Calculator shows in its menu, there are actually only three XAML files that `MainPage` needs to
+manage in order to support all modes. They are:
+
+* [Calculator.xaml][Calculator.xaml]: This [UserControl] is itself a container for the [Standard][CalculatorStandardOperators.xaml],
+  [Scientific][CalculatorScientificOperators.xaml], and [Programmer][CalculatorProgrammerOperators.xaml] modes.
+* [DateCalculator.xaml][DateCalculator.xaml]: Everything needed for the DateCalculator mode.
+* [UnitConverter.xaml][UnitConverter.xaml]: One `UserControl` to support every Converter mode.
+
+### VisualStates
+
+[VisualStates][VisualState] are used to change the size, position, and appearance ([Style][Style]) of UI elements
+in order to create an adaptive, responsive UI. A transition to a new `VisualState` is often triggered by specific
+window sizes. Here are a few important examples of `VisualStates` in Calculator. Note that it is not a
+complete list. When making UI changes, make sure you are considering the various `VisualStates` and layouts that
+Calculator defines.
+
+#### History/Memory Dock Panel expansion
+
+In the Standard, Scientific, and Programmer modes, the History/Memory panel is exposed as a flyout in small window sizes.
+Once the window is resized to have enough space, the panel becomes docked along the edge of the window.
+
+<img src="Images\VisualStates\Standard1.gif" height="400" />
+
+#### Scientific mode, inverse function button presence
+
+In the Scientific mode, for small window sizes there is not enough room to show all the function buttons. The mode
+hides some of the buttons and provides a Shift (↑) button to toggle the visibility of the collapsed rows. When the
+window size is large enough, the buttons are re-arranged to display all function buttons at the same time.
+
+<img src="Images\VisualStates\Scientific1.gif" height="400" />
+
+#### Unit Converter aspect ratio adjustment
+
+In the Unit Converter mode, the converter inputs and the numberpad will re-arrange depending on if the window is in
+a Portrait or Landscape aspect ratio.
+
+<img src="Images\VisualStates\Converter1.gif" height="400" />
+
+### Data-Binding
+
+Calculator uses [data binding][Data Binding] to dynamically update the properties of UI elements. If this concept
+is new for you, it's also worth reading about [data binding in depth][Data binding in depth].
+
+The [x:Bind][x:Bind] markup extension is a newer replacement for the older [Binding][Binding] style. You may see both
+styles in the Calculator codebase. Prefer `x:Bind` in new contributions because it has better performance. If you need
+to add or modify an existing `Binding`, updating to `x:Bind` is a great first step. Make sure to read and understand
+the difference between the two styles, as there are some subtle behavioral changes. Refer to the
+[binding feature comparison][BindingComparison] to learn more.
+
+------------
+## ViewModel
+
+The ViewModel layer is contained in the [CalcViewModel][CalcViewModel folder] project. ViewModels provide a source of
+data for the UI to bind against and act as the intermediary separating pure business logic from UI components that
+should not care about the model's implementation. Just as the View layer consists of a hierarchy of XAML files, the
+ViewModel consists of a hierarchy of ViewModel files. The relationship between XAML and ViewModel files is often 1:1.
+Here are the notable ViewModel files to start exploring with:
+
+* [ApplicationViewModel.h][ApplicationViewModel.h]: The ViewModel for [MainPage.xaml][MainPage.xaml]. This ViewModel
+  is the root of the other mode-specific ViewModels. The application changes between modes by updating the `Mode` property
+  of the `ApplicationViewModel`. The ViewModel will make sure the appropriate ViewModel for the new mode is initialized.
+* [StandardCalculatorViewModel.h][StandardCalculatorViewModel.h]: The ViewModel for [Calculator.xaml][Calculator.xaml].
+  This ViewModel exposes functionality for the main three Calculator modes: Standard, Scientific, and Programmer.
+* [DateCalculatorViewModel.h][DateCalculatorViewModel.h]: The ViewModel for [DateCalculator.xaml][DateCalculator.xaml].
+* [UnitConverterViewModel.h][UnitConverterViewModel.h]: The ViewModel for [UnitConverter.xaml][UnitConverter.xaml].
+  This ViewModel implements the logic to support every converter mode, including Currency Converter.
+
+### PropertyChanged Events
+
+In order for [data binding](#data-binding) to work, ViewModels need a way to inform the XAML framework about
+updates to their member properties. Most ViewModels in the project do so by implementing the
+[INotifyPropertyChanged][INotifyPropertyChanged] interface. The interface requires that the class provides a
+[PropertyChanged event][PropertyChanged]. Clients of the ViewModel (such as the UI), can register for the
+`PropertyChanged` event from the ViewModel, then re-evaluate bindings or handle the event in code-behind when the
+ViewModel decides to raise the event. ViewModels in the Calculator codebase generally uses a macro, defined in the
+[Utils.h][Utils.h] utility file, to implement the `INotifyPropertyChanged` interface. Here is a standard
+implementation, taken from [ApplicationViewModel.h][ApplicationViewModel.h].
+
+```C++
+[Windows::UI::Xaml::Data::Bindable]
+public ref class ApplicationViewModel sealed : public Windows::UI::Xaml::Data::INotifyPropertyChanged
+{
+public:
+    ApplicationViewModel();
+
+    OBSERVABLE_OBJECT();
+```
+
+The `OBSERVABLE_OBJECT()` macro defines the required `PropertyChanged` event. It also defines a private
+`RaisePropertyChanged` helper function for the class. The function takes a property name and raises a
+`PropertyChanged` event for that property.
+
+Properties that are intended to be the source for a data binding are also typically implemented with a macro. Here is
+one such property from `ApplicationViewModel`:
+
+```C++
+OBSERVABLE_PROPERTY_RW(Platform::String^, CategoryName);
+```
+
+The `OBSERVABLE_PROPERTY_RW` macro defines a Read/Write property that will raise a `PropertyChanged` event if its value
+changes. Read/Write means the property exposes both a public getter and setter. For efficiency and to avoid raising
+unnecessary `PropertyChanged` events, the setter for these types of properties will check if the new value is
+different from the previous value before raising the event.
+
+From this example, either `ApplicationViewModel` or clients of the class can simply assign to the `CategoryName`
+property and a `PropertyChanged` event will be raised, allowing the UI to respond to the new `CategoryName` value.
+
+--------
+## Model
+
+The Model for the Calculator modes is contained in the [CalcManager][CalcManager folder] project. It consists of three layers: a `CalculatorManager`, which relies on a `CalcEngine`, which relies on the `Ratpack`.
+
+### CalculatorManager
+
+The CalculatorManager contains the logic for managing the overall Calculator app's data such as the History and Memory lists, as well as maintaining the instances of calculator engines used for the various modes. The interface to this layer is defined in [CalculatorManager.h][CalculatorManager.h].
+
+### CalcEngine
+
+The CalcEngine contains the logic for interpreting and performing operations according to the commands passed to it. It maintains the current state of calculations and relies on the RatPack for performing mathematical operations. The interface to this layer is defined in [CalcEngine.h][CalcEngine.h].
+
+### RatPack
+
+The RatPack (short for Rational Pack) is the core of the Calculator model and contains the logic for
+performing its mathematical operations (using [infinite precision][Infinite Precision] arithmetic
+instead of regular floating point arithmetic). The interface to this layer is defined in [ratpak.h][ratpak.h].
+
+[References]:####################################################################################################
+
+[C++/CX]:                             https://docs.microsoft.com/en-us/cpp/cppcx/visual-c-language-reference-c-cx
+[What is UWP?]:                       https://docs.microsoft.com/en-us/windows/uwp/get-started/universal-application-platform-guide
+[XAML Overview]:                      https://docs.microsoft.com/en-us/windows/uwp/xaml-platform/xaml-overview
+[MVVM]:                               https://docs.microsoft.com/en-us/windows/uwp/data-binding/data-binding-and-mvvm
+
+[Calculator folder]:                  ../src/Calculator
+[App.xaml]:                           ../src/Calculator/App.xaml
+[App.xaml.cs]:                       ../src/Calculator/App.xaml.cs
+[StaticResource]:                     https://docs.microsoft.com/en-us/windows/uwp/xaml-platform/staticresource-markup-extension
+[ThemeResource]:                      https://docs.microsoft.com/en-us/windows/uwp/xaml-platform/themeresource-markup-extension
+[Page]:                               https://docs.microsoft.com/en-us/uwp/api/Windows.UI.Xaml.Controls.Page
+[UserControl]:                        https://docs.microsoft.com/en-us/uwp/api/Windows.UI.Xaml.Controls.UserControl
+[MainPage.xaml]:                      ../src/Calculator/Views/MainPage.xaml
+[Calculator.xaml]:                    ../src/Calculator/Views/Calculator.xaml
+[CalculatorStandardOperators.xaml]:   ../src/Calculator/Views/CalculatorStandardOperators.xaml
+[CalculatorScientificOperators.xaml]: ../src/Calculator/Views/CalculatorScientificOperators.xaml
+[CalculatorProgrammerOperators.xaml]: ../src/Calculator/Views/CalculatorProgrammerOperators.xaml
+[DateCalculator.xaml]:                ../src/Calculator/Views/DateCalculator.xaml
+[UnitConverter.xaml]:                 ../src/Calculator/Views/UnitConverter.xaml
+
+[VisualState]:                        https://docs.microsoft.com/en-us/windows/uwp/design/layout/layouts-with-xaml#adaptive-layouts-with-visual-states-and-state-triggers
+[Style]:                              https://docs.microsoft.com/en-us/windows/uwp/design/controls-and-patterns/xaml-styles
+
+[Data Binding]:                       https://docs.microsoft.com/en-us/windows/uwp/data-binding/data-binding-quickstart
+[Data binding in depth]:              https://docs.microsoft.com/en-us/windows/uwp/data-binding/data-binding-in-depth
+[x:Bind]:                             https://docs.microsoft.com/en-us/windows/uwp/xaml-platform/x-bind-markup-extension
+[Binding]:                            https://docs.microsoft.com/en-us/windows/uwp/xaml-platform/binding-markup-extension
+[BindingComparison]:                  https://docs.microsoft.com/en-us/windows/uwp/data-binding/data-binding-in-depth#xbind-and-binding-feature-comparison
+
+[CalcViewModel folder]:               ../src/CalcViewModel
+[ApplicationViewModel.h]:             ../src/CalcViewModel/ApplicationViewModel.h
+[StandardCalculatorViewModel.h]:      ../src/CalcViewModel/StandardCalculatorViewModel.h
+[DateCalculatorViewModel.h]:          ../src/CalcViewModel/DateCalculatorViewModel.h
+[UnitConverterViewModel.h]:           ../src/CalcViewModel/UnitConverterViewModel.h
+
+[INotifyPropertyChanged]:             https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.data.inotifypropertychanged
+[PropertyChanged]:                    https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.data.inotifypropertychanged.propertychanged
+[Utils.h]:                            ../src/CalcViewModel/Common/Utils.h
+
+[CalcManager folder]:                 ../src/CalcManager
+[CalculatorManager.h]:                ../src/CalcManager/CalculatorManager.h
+[CalcEngine.h]:                       ../src/CalcManager/Header&#32;Files/CalcEngine.h
+[Infinite Precision]:                 https://en.wikipedia.org/wiki/Arbitrary-precision_arithmetic
+[ratpak.h]:                           ../src/CalcManager/Ratpack/ratpak.h

ManualTests.md

@@ -0,0 +1,494 @@
+# Calculator Manual Tests
+These manual tests are run before every release of the Calculator app.
+
+## Smoke Tests
+
+### Calculators
+
+### Math in Standard Calculator 
+
+**Test 1**
+Steps:
+1. From the Standard Calculator page, input “3”, “+”, “3”, “Enter” on the keyboard 
+*Expected: “6” shows up in the display *
+2. Input “4”, “-”, “2”, “=” using the in-app buttons 
+*Expected: “2” shows up in the display*
+ 
+ **Test 2**
+ Steps:
+1. From the Standard Calculator page, input “3”, “+”, “3”, “Enter” on the keyboard 
+2. Navigate to the History pane, and verify that “3 + 3 = 6” shows up in the pane 
+3. Input “MS” using the in-app buttons 
+4. Navigate to the Memory pane
+*Expected: “6” shows up in the pane*
+
+### Math in Scientific Calculator
+
+**Test 1**
+Steps: 
+1. From the Scientific Calculator page, input “3”, “^”, “3”, “Enter” on the keyboard 
+*Expected: “27” shows up in the display*
+
+**Test 2**
+Steps:
+1. Input “5”, “n!”, “=” using the in-app buttons 
+*Expected: “120” shows up in the display*
+
+### Math in Programmer Calculator 
+
+**Test 1**
+Steps:
+1. From the Programmer Calculator page, input “1”, “&”, “0”, “Enter” on the keyboard 
+*Expected: “0” shows up in the display*
+
+**Test 2**
+Steps:
+1. Input “15” using the in-app buttons and select “HEX” 
+*Expected: “F” shows up in the display and the letters A-F show up as in-app buttons*
+
+### Converters 
+
+**Converter Usage**
+Steps:
+1. From the Length Converter page, select “kilometers” as the unit type in the input field and input “5” using the keyboard 
+2. Select “miles” as the unit type in the output field 
+*Expected: The output starts with is “3.106856”*
+
+### Always-on-Top
+
+**Test 1**
+Steps:
+1. Launch the "Calculator" app and navigate to "Standard" Calculator
+*Expected: Always-on-Top button's tooltip says "Keep on top"*
+2. Click the Always-on-Top button
+*Expected: Always-on-Top button's tooltip now says "Back to full view"*
+3. Launch the "Notepad" app and put it in full-screen mode
+*Expected: Calculator is still on top of Notepad and in Always-on-Top mode*
+
+**Test 2**
+Steps: 
+1. Launch the "Calculator" app and from "Standard" Calculator, input “3”, “+”, “3” (do not press “Enter”)
+2. Tab over the Always-on-Top button and press "Enter" on the keyboard
+*Expected: The application title, hamburger menu, calculator type title, calculation expression (the secondary line above the main display), history button and memory buttons are no longer visible. The main display shows "3"*
+2. Press “Enter”
+*Expected: The main display shows "6"*
+3. Press "Ctrl-H" on the keyboard
+*Expected: Nothing happens (history keyboard shortcuts are disabled)*
+4. Press "Ctrl-P" on the keyboard, then tab over the Always-on-Top button and press "Enter" on the keyboard again
+5. Open the Memory panel
+*Expected: Nothing is stored in memory (memory keyboard shortcuts are disabled in Always-on-Top mode) and "6" is in history*
+
+**Test 3**
+Steps: 
+1. Launch the "Calculator" app and from "Standard" Calculator, click the Always-on-Top button
+2. Resize the window horizontally
+*Expected: The buttons automatically expand or shrink to fit the available screen size*
+3. Resize the window vertically
+*Expected: The buttons automatically expand or shrink to fit the available screen size and the percent, square-root, squared and reciprocal buttons disappear when the screen height is small*
+4. Click the Always-on-Top button again
+*Expected: Calculator is in Standard mode and the original window layout from before Step 1 is restored*
+5. Click the Always-on-Top button again
+*Expected: Calculator is in Always-on-Top mode and the window size from after Step 3 is restored*
+6. Close the "Calculator" app
+7. Launch the "Calculator" app again and click the Always-on-Top button
+*Expected: The window size from right before closing from Always-on-Top mode (ie. after Step 5) is restored*
+
+**Test 4**
+Steps:
+1. Launch the "Calculator" app and from "Standard" Calculator, click the Always-on-Top button
+2. Input "/", "0", “Enter” on the keyboard
+*Expected: "Result is undefined" is displayed in the system default app language*
+3. Click the Always-on-Top button again
+*Expected: Calculator is in Standard mode and all operator (except for "CE", "C", "Delete" and "=") and memory buttons are disabled
+
+**Test 5**
+Steps:
+1. Launch the "Calculator" app and navigate to "Scientific" Calculator
+*Expected: The Always-on-Top button is hidden*
+2. Navigate to "Standard" Calculator
+*Expected: The Always-on-Top button is visible*
+
+## Basic Verification Tests
+
+**Launch App Test**
+Steps:
+1.	Press the Windows key.
+2.	Navigate to "all apps".
+3.	Look for "Calculator".
+4.	Click to launch the "Calculator" app.
+*Expected: The calculator app launches gracefully.*
+
+
+**All Calculators Test: Verify All Numbers & Input Methods**
+Steps:
+1.	Launch the "Calculator" app.
+2.	Navigate to "Standard" Calculator.
+3.	Mouse Input
+*Expected: All numbers work via mouse click.*
+4.	Keyboard Input:
+*Expected: All numbers work via number pad.*
+5.	Navigate to "Scientific" Calculator and Repeat Steps 3-5
+*Expected: Steps 3-5 pass in Scientific mode*
+6.	Navigate to "Programmer" Calculator and Repeat Steps 3-5
+*Expected: Steps 3-5 pass in Programmer mode*
+
+
+**All Calculators Test: Verify Basic Arithmetic Functions**
+Steps:
+1.	Launch the "Calculator" app.
+2.	Navigate to "Standard" Calculator.
+3.	Using the Number Pad and Mouse perform the following arithmetic functions and verify the result.
+    a.	(+) Addition
+    b.	(-) Subtraction
+    c.	(x) Multiplication
+    d.	(÷) Division
+    e.	(1/x) Reciprocal
+    f.	(√) Square Root
+    g.	(x²) Squared
+    h.	(x³) Cubed
+    i.	(%) Percent
+    j.	(±) Positive / Negative
+    k.	(=) Equals
+    l.	Delete Button (flag with x in it)
+    m.	[CE] Clear
+    n.	[C] Global Clear
+    o.	(.) Decimal
+4.	Navigate to "Scientific" Calculator and Repeat Steps 3-19.
+5.	Navigate to "Programmer" Calculator and Repeat Steps 3-18 (No Decimal in Programming Calc).
+
+
+**Scientific Calculator Test: Verify advanced arithmetic functions**
+Steps:
+1.	Launch the "Calculator" app.
+2.	Navigate to "Scientific" Calculator.
+3.	Using the Number Pad and Mouse perform the following arithmetic functions and verify the result.
+    a.	(xʸ) Xth Power of Y
+    b.	(y√x) Y Root of X
+    c.	(10ˣ) 10 Power of X
+    d.	(ex) E Power of X
+    e.	(π) Pi
+    f.	(n!) Factorial
+    g.	(Ln) Natural Logarithm
+    h.	(Log) Logarithm
+    i.	(Exp) Exponential
+    j.	(dms) Degrees, Minutes, Seconds
+    k.	(deg) Degrees
+    l.	(Mod) Modulo
+    m.	“( )" Parenthesis
+
+
+**All Calculators Test: Verify memory functions**
+Steps:
+1.	Launch the "Calculator" app.
+2.	Navigate to "Standard" Calculator.
+3.	Perform a calculation and press the MS button.
+4.	If small scale, Select the (M) with the drop down arrow
+*Expected: Calculation from previous step is present.*
+5.	Click the (M+) Add to Memory.
+*Expected: Previous calculation is added to itself.*
+6.	Click the (M-) Subtract from Memory.
+*Expected: Previous calculation is subtracted from the base calculation.*
+7.	Click the (MR) Memory Recall.
+*Expected: Previous calculation is made primary (This is not available in the Programmer mode).*
+8.	Check the MC button.
+*Expected: The stored information is cleared.*
+9.	Navigate to "Scientific" Calculator and Repeat Steps 3-8.
+*Expected: All in "Scientific" mode.*
+10.	Navigate to "Programmer" Calculator and Repeat Steps 3-8.
+*Expected: All in "Programmer" mode.*
+
+
+**Scientific Calculator Test: Verify trigonometric functions**
+Steps:
+1.	Launch the "Calculator" app.
+2.	Navigate to "Scientific" Calculator.
+3.  Using the Number Pad and Mouse perform the following trigonometric functions and verify the result.
+3.	Sine (sin)
+4.	Cosine (cos)
+5.	Tangent (tan)
+6.	Inverse Sine (sin-1)
+7.	Inverse Cosine (cos-1)
+8.	Inverse Tangent (tan-1) Inverse Tangent:
+9.	Press (HYP) for Hyperbolic trig functions: 
+*Expected: Trig function buttons show hyperbolic trig functions.*
+10.	Hyperbolic Sine (sinh)
+11.	Hyperbolic Tangent (tanh) 
+12.	Hyperbolic Cosine (cosh) 
+13.	Inverse Hyperbolic Sine (sinh-1) 
+14.	Inverse Hyperbolic Tangent (tanh-1) 
+15.	Inverse Hyperbolic Cosine (cosh-1) 
+
+
+**Programmer Calculator Test: Verify logical functions**
+Steps:
+1.	Launch the "Calculator" app
+2.	Navigate to "Programmer" Calculator.
+3.  Using the Number Pad and Mouse perform the following trigonometric functions and verify the result.
+4.	Rotate Left (RoL) Logical Operator:
+    01011001 rol 3 = 11001010.
+5.	Rotate Right (RoR) Logical Operator:
+    01011001 RoR 3 = 00101011.
+6.	(Lsh) Logical Operator:
+    (10 multiplied by 2 three times)
+    10 Lsh 3 = gives 80.
+    10.345 Lsh 3 = also gives 80.
+7.	(Rsh) Logical Operator:
+    (16 divided by 2 twice)
+    16 Rsh 2 = gives 4.
+    16.999 Rsh 2 = also gives 4.
+7.	(Or) Logical Operator
+    101 OR 110 = gives 111.
+9.	Exclusive Or (Xor) Logical Operator:
+    101 XOR 110 = gives 11.
+9.	(Not) Logical Operator
+    NOT 1001100111001001 =
+    0110011000110110.
+10.	(And) Logical Operator
+    101 AND 110 = gives 100.
+11.	(Mod) Logical Operator
+    Remainder of integer division (Modulo x)
+12.	"( )" Parenthesis
+
+
+**All Calculators and Converters Test: Verify scaling functions and languages**
+Steps:
+1.	Launch the "Calculator" app.
+2.	For All Modes: While scaling in both directions to capacity
+*Expected: Elements like Memory and History are shifted or integrated appropriately.*
+3.	In Any Mode: While at the Smallest scale, Select the Menu Button
+*Expected: The menu items are scrollable with nothing overlapping.*
+4.	While in the Menu: Check the About Page
+*Expected:  Everything in the about page fits into its window*
+5.	For Scientific Mode: At a Larger Scale
+*Expected: All buttons are present and the 2nd button is grayed out.*
+6.	For Scientific Mode: At a Smaller Scale
+*Expected: All buttons are present and the 2nd button is able to be toggled.*
+7.	For Programmer Mode: At a Any Scale
+*Expected: All buttons are present and the 2nd button is able to be toggled.*
+8.	For Converter Mode: While Scaling
+*Expected: The number pad and input areas move around each other gracefully.*
+9.  For Graphing Mode: While Scaling
+*Expected: The number pad, graph area, and input areas move around each other gracefully.*
+10.	Changing Language: Open Settings app > Time & language > Region & language > Add a language > Select a Right to Left (RTL) language such as Hebrew > Install the associated files> Set it to the system default.
+11.	Set the system number format preference: Open a Run dialog (WIN + R) > type ‘intl.cpl’ > Enter > In the format dropdown list > Select Hebrew > Apply.
+12.	Initiating the change: Package has completed installing > Sign out > Sign in. (This change to the app may also require a reinstallation of the build)
+13.	Repeat Steps 2-6 again in a (RTL) language.
+*Expected: No elements fall out of intended boundaries.*
+
+
+**All Calculators Test: Verify toggling functions**
+Steps:
+1.	Launch the "Calculator" app.
+2.	For Standard & Scientific Modes: While in the Smallest scale, verify that the History Icon brings up the history panel gracefully and is displayed appropriately.
+For Scientific Mode: At a Smaller Scale
+Verify the following:
+3.	Grad / Deg / Rad
+    Perform a trig function
+*Expected: The answer to the function is in the selected grad/deg/rad. Repeat for each of the modes.*
+4.	(Hyp) Hyperbolic
+*Expected: Sin toggles to Sinh, Cos toggles to Cosh, Tan toggles to Tanh.*
+5.	(F-E key) Floating Point Notation & Scientific Notation.
+*Expected: Display toggles between floating point and Scientific notation.*
+For Programmer Mode
+Verify the following:
+6.	"Bit Toggling Keypad":
+*Expected: In app keypad changes to represent Bits (1s and 0s).*
+7.	"QWORD / DWORD / WORD / BYTE":
+*Expected: Toggles as expected.*
+8.	"Hex" Hexadecimal:
+*Expected: A B C D E F become active and user can use them. A maximum of 16 characters can be entered.*
+9.	"Dec" Decimal:
+*Expected: A B C D E F are inactive. A maximum of 19 characters can be entered.*
+10.	"Oct" Octal:
+*Expected: A B C D E F 8 9 are inactive. A maximum of 22 characters can be entered.*
+11.	"Bin" Binary:
+*Expected: A B C D E F 2 3 4 5 6 7 8 9 are inactive. A maximum of 64 characters can be entered.*
+
+**Graphing Mode Test: Verify Graphing mode functions**
+Steps:
+1.  Launch the "Calculator" app
+2.  Navigate to "Graphing" Calculator
+3.  Enter a function of x in the input field <br>
+*Expected: Function is plotted in the graph area. Line color matches the colored square next to the input field*
+4.  Select the "+" button below the function input and enter more functions in the fields that appear <br>
+*Expected: All functions are plotted in the graph area and match the colors of the input field squares*
+5.  Select the colored square for any function <br>
+*Expected: Visibility of the function in the graph is toggled off/on*
+6.  Select the "Zoom In", "Zoom Out", and "Reset View' buttons in the graph area <br>
+*Expected: Both X and Y axes zoom in, out, and revert to default settings, respectively*
+7.  Select the Trace button, then click + drag the graph until the red square is near a graphed function<br>
+*Expected: Closest (X, Y) coordinates of the function to the red square are displayed with a black dot to indicate the location*
+8.  Enter "y=mx+b" into a function input field, then select "Variables" button <br>
+*Expected: y=x+1 function is plotted in the graph, "Variables" modal window shows two variables "m" and "b" with values set to 1.*
+9.  Adjust the value, minimum, maximum, and step for each variable <br>
+*Expected: y=mx+b graph adjusts to the new values for m and b, step size changes the increments of the slider for each value*
+10.  Share the graph via OneNote, Outlook/Mail, Twitter, and Feedback Hub <br>
+*Expected: Modifiable message that contains an image of the graph customized for the chosen application opens*
+11.  Verify Key Graph Features tab shows the correct information for the following functions: <br>
+    *(Note: IP = Inflection Points, VA = Vertical Asymptotes, HA = Horizontal Asymptotes, OA = Oblique Asymptotes)* <br>
+    a.  **y=x** <br>
+    *Expected: Domain: ⁅𝑥∈ℝ⁆; Range: ⁅y∈ℝ⁆; X/Y Intercepts: (0)/(0); Max: none; Min: none; IP: none; VA: none; HA: none; OA: none; Parity: Odd; Monotonicity: (-∞, ∞) Increasing* <br>
+    b.  **y=1/x** <br>
+    *Expected: Domain: ⁅𝑥≠0⁆; Range: ⁅y∈ℝ\{0}⁆; X/Y Intercepts: ø/ø; Max: none; Min: none; IP: none; VA: x=0; HA: y=0; OA: none; Parity: Odd; Monotonicity: (0, ∞) Decreasing, (-∞, 0) Increasing* <br>
+    c.  **y=x^2** <br>
+    *Expected: Domain: ⁅𝑥∈ℝ⁆; Range: ⁅y∈{0, ∞)⁆; X/Y Intercepts: (0)/(0); Max: none; Min: (0,0); IP: none; VA: none; HA: none; OA: none; Parity: Even; Monotonicity: (0, ∞) Increasing, (-∞, 0) Decreasing* <br>
+    d.  **y=x^3** <br>
+    *Expected: Domain: ⁅𝑥∈ℝ⁆; Range: ⁅y∈ℝ⁆; X/Y Intercepts: (0)/(0); Max: none; Min: none; IP: (0,0); VA: none; HA: none; OA: none; Parity: Odd; Monotonicity: (-∞, ∞) Increasing* <br>
+    e.  **y=e^x** <br>
+    *Expected: Domain: ⁅𝑥∈ℝ⁆; Range: ⁅y∈(0, ∞)⁆; X/Y Intercepts: ø/(1); Max: none; Min: none; IP: none; VA: none; HA: y=0; OA: none; Parity: none; Monotonicity: (-∞, ∞) Increasing* <br>
+    f.  **y=ln(x)** <br>
+    *Expected: Domain: ⁅𝑥>0⁆; Range: ⁅y∈ℝ⁆; X/Y Intercepts: (1)/ø; Max: none; Min: none; IP: none; VA: x=0; HA: none; OA: none; Parity: none; Monotonicity: (0, ∞) Increasing* <br>
+    g.  **y=sin(x)** <br>
+    *Expected: Domain: ⁅𝑥∈ℝ⁆; Range: ⁅𝑦∈[−1,1]⁆; X/Y Intercepts: (⁅𝜋n1,n1∈ℤ⁆)/(0); Max: ⁅(2𝜋n1+𝜋/2,1),n1∈ℤ⁆; Min: ⁅(2𝜋n1+3𝜋/2,−1),n1∈ℤ⁆; IP: ⁅(𝜋n1,0),n1∈ℤ⁆; VA: none; HA: none; OA: none; Parity: Odd; Monotonicity: ⁅(2𝜋n1+𝜋/2,2𝜋n1+3𝜋/2),n1∈ℤ⁆ Decreasing; ⁅(2𝜋n1+3𝜋/2,2𝜋n1+5𝜋/2),n1∈ℤ⁆ Increasing; Period: 2𝜋* <br>
+    h.  **y=cos(x)** <br>
+    *Expected: Domain: ⁅𝑥∈ℝ⁆; Range: ⁅𝑦∈[−1,1]⁆; X/Y Intercepts: (⁅𝜋n1+𝜋/2,n1∈ℤ⁆)/(1); Max: ⁅(2𝜋n1,1),n1∈ℤ⁆; Min: ⁅(2𝜋n1+𝜋,-1),n1∈ℤ⁆; IP: ⁅(𝜋n1+𝜋/2,0),n1∈ℤ⁆; VA: none; HA: none; OA: none; Parity: Even; Monotonicity: ⁅(2𝜋n1+𝜋,2𝜋n1+2𝜋),n1∈ℤ⁆ Increasing, ⁅(2𝜋n1,2𝜋n1+𝜋),n1∈ℤ⁆ Decreasing; Period: 2𝜋* <br>
+    i.  **y=tan(x)** <br>
+    *Expected: Domain: ⁅x≠𝜋n1+𝜋/2,∀n1∈ℤ⁆; Range: ⁅𝑦∈ℝ⁆; X/Y Intercepts: (x=𝜋n1, n1 ∈ℤ)/(0); Max: none; Min: none; IP: x=𝜋n1, n1 ∈ℤ; VA: x=𝜋n1+𝜋/2, n1∈ℤ; HA: none; OA: none; Parity: Odd; Monotonicity: ⁅(𝜋n1+𝜋/2,𝜋n1+3𝜋/2),n1∈ℤ⁆ Increasing; Period: 𝜋* <br>
+    j.  **y=sqrt(25-x^2)** <br>
+    *Expected: Domain: ⁅x∈[-5,5]⁆; Range: ⁅𝑦∈[0,5]⁆; X/Y Intercepts: (5),(-5)/(5); Max: (0,5); Min: (-5,0) and (5,0); IP: none; VA: none; HA: none; OA: none; Parity: Even; Monotonicity: (0,5) Decreasing, (-5,0) Increasing* <br>
+    k.  **y=(-3x^2+2)/(x-1)** <br>
+    *Expected: Domain: ⁅x≠1⁆; Range: ⁅𝑦∈(-∞, -2√3 - 6}U{2√3 -6,∞⁆; X/Y Intercepts: (-√6/3),(√6/3)/(-2); Max: ⁅(√3/3+1,-2√3−6)⁆; Min: ⁅(−√3/3+1,2√3−6)⁆; IP: none; VA: x=1; HA: none; OA: y=-3x-3; Parity: none; Monotonicity: (√3/3+1,∞) Decreasing, (1,√3/3+1,) Increasing(-√3/3+1,1), Increasing, (-∞,-√3/3+1) Decreasing* <br>
+    l. **y=sin(sin(x))** ("too complex" error test) <br>
+    *Expected: Domain: ⁅𝑥∈ℝ⁆; Range: Unable to calculate range for this function; X/Y Intercepts: none; Max: none; Min: none; IP: none; VA: none; HA: none; OA: none; Parity: odd; Monotonicity: Unable to determine the monotonicity of the function* <br>
+    *These features are too complex for Calculator to calculate: Range, X Intercept, Period, Minima, Maxima, Inflection Points, Monotonicity*
+    m. **y=mx+b** <br>
+    *Expected: Analysis is not supported for this function*
+
+**Date Calculation Test: Verify dates can be calculated.**
+Steps:
+1.	Launch the "Calculator" app
+2.	Navigate to "Date Calculation" Calculator
+3.  With "Difference between dates" Selected
+    Change the various date input fields
+*Expected: From and To reflect dates input respectively.*
+5.	With "Add or Subtract days" Selected
+    Change the various date input fields
+*Expected: Verify changes made to both add and subtract reflect input respectively.*
+
+
+**Currency Converter Test: Verify conversion & updating current currency rates.**
+Steps:
+1.	Launch the "Calculator" app.
+2.	Navigate to "Currency Converter" Calculator.
+3.	Select 2 Currency types from the dropdowns & enter a "1" into a conversion slot.
+*Expected: The currency is slotted properly and converted rate matches the ratio provided under the selected currency types.*
+4.	Click "Updated"
+*Expected: Display matches PC's date and time.*
+5.	After at least a minute: Select "Update rates" & Check "Updated" again:
+*Expected: The "Update Rates" button changes the date and time to match the computer's current date and time.*
+
+
+**All Calculators Test: Hotkeys: Verify Hot Key function.**
+Steps:
+1.	Launch the "Calculator" app.
+
+    For All Applicable Modes verify the following (note: only 11-15 and 20 work in Always-on-Top mode):
+2.	Press **Alt +1** to enter "Standard" mode
+*Expected: Move to "Standard" screen.*
+3.	Press **Alt +2** to enter "Scientific" mode
+*Expected: Move to "Scientific" screen.*
+4.	Press **Alt +3** to enter "Programmer" mode
+*Expected: Move to "Programming" screen.*
+5.	Press **Alt +4** to enter "Date Calculation" mode
+*Expected: Move to "Date Calculation" screen.*
+6   Press **Alt +5** to enter "Graphing" mode
+*Expected: Move to "Graphing" screen.*
+7.	Press **Ctrl +M** to Store in Memory
+8.	Press **Ctrl +P** to Add to Active Memory
+9.	Press **Ctrl +Q** to Subtract form Active Memory
+10.	Press **Ctrl +R** to Recall from Memory
+11.	Press **Ctrl +L** to Clear from Memory
+12.	Press **Delete** to Clear Current Input 'CE'
+13.	Press **Esc** to Full Clear Input 'C'
+14.	Press **F9** to Toggle '±'
+15.	Press **R** to Select '1/x'
+16.	Press **@** to Select '√'
+17.	Press **Ctrl + H** to Toggle History Panel
+*Expected: Function when in small scale window.*
+18.	Press **Up arrow** to Move up History Panel
+*Expected: Function when in small scale window.*
+19.	Press **Down arrow** to Move Down History Panel
+*Expected: Function when in small scale window.*
+20.	Press **Ctrl + Shift + D** to Clear History Panel
+*Expected: Function when in small scale window.*
+21.	Press **Spacebar** to Repeat Last Input
+
+    Verify the following in Scientific Mode
+22.	Press **F3** to Select 'DEG'
+23.	Press **F4** to Select 'RAD'
+24.	Press **F5** to Select 'GRAD'
+25.	Press **Ctrl +G** to Select '10ˣ'
+26.	Press **Ctrl +Y** to Select 'y√x'
+27.	Press **Shift +O** to Select 'sin-1'
+28.	Press **Shift + S** to Select 'cos-1'
+29.	Press **Shift +T** to Select 'tan-1'
+30.	Press **Ctrl +O** to Select 'Cosh'
+31.	Press **Ctrl +S** to Select 'Sinh'
+32.	Press **Ctrl +T** to Select 'Tanh'
+33.	Press **D** to Select 'Mod'
+34.	Press **L** to Select 'log'
+35.	Press **M** to Select 'dms'
+36.	Press **N** to Select 'ln'
+37.	Press **Ctrl +N** to Select 'ex'
+38.	Press **O** to Select 'Cos'
+39.	Press **P** to Select 'π'
+40.	Press **Q** to Select 'x²'
+41.	Press **S** to Select 'Sin'
+42.	Press **T** to Select 'Tan'
+43.	Press **V** to Toggle 'F-E'
+44.	Press **X** to Select 'Exp'
+45.	Press **Y** or **^** to Select 'xʸ'
+46.	Press **#** to Select 'x³'
+47.	Press **!** to Select 'n!'
+
+    Verify the following in Programmer Mode
+48.	Press **F2** to Select 'DWORD'
+49.	Press **F3** to Select 'WORD'
+50.	Press **F4** to Select 'BYTE'
+51.	Press **F5** to Select 'HEX'
+52.	Press **F6** to Select 'DEC'
+53.	Press **F7** to Select 'OCT'
+54.	Press **F8** to Select 'BIN'
+55.	Press **F12** to Select 'QWORD'
+56.	Press **A-F** to Input in HEX
+57.	Press **J** to Select 'RoL'
+58.	Press **K** to Select 'RoR'
+59.	Press **<** to Select 'Lsh'
+60.	Press **>** to Select 'Rsh'
+61.	Press **%** to Select 'Mod'
+62.	Press **|** to Select 'Or'
+63.	Press **~** to Select 'Not'
+64.	Press **&** to Select 'And'
+
+    Verify the following in Graphing Mode
+65. Press **x** to Select 'x'
+66. Press **y** to Select 'y'
+67. Press **Ctrl +[Numpad+]** to Select 'Zoom In'
+68. Press **Ctrl +[Numpad-]** to Select 'Zoom Out'
+
+## Localization Tests
+
+### Always-on-Top
+
+**Test 1**
+Steps:
+1. Change the system default app language to Arabic
+2. Launch the "Calculator" app and from "Standard" Calculator, click the Always-on-Top button
+*Expected: UI/Menu is localized (for example, the title bar buttons is in right-to-left order)*
+3. Input "/", "0", “Enter” on the keyboard
+*Expected: Error message is in Arabic*
+
+## Ease of Access Tests
+
+### Always-on-Top
+
+**Test 1**
+Steps:
+1. Open the "Narrator" app
+2. Launch the "Calculator" app and from "Standard" Calculator, click the Always-on-Top button
+3. Tab over the Always-on-Top button
+*Expected: Narrator reads the localized version of "Back to full view"*
+4. Tab over the main results field
+*Expected: Narrator reads the localized version of exactly what's displayed (ie. "0")*
+5. Tab over the rest of the UI elements
+*Expected: Narrator reads the localized version of the UI elements' contents*

NewFeatureProcess.md

@@ -0,0 +1,113 @@
+# New feature process
+
+## Where do I submit my idea for a new feature?
+The easiest way to submit new feature requests is through 
+[Feedback Hub](https://insider.windows.com/en-us/fb/?contextid=130).
+In Feedback Hub, any Windows user (even if they aren't on GitHub) can upvote suggestions. The
+Calculator team reviews these suggestions regularly, and when we're ready to work on an idea we
+create [feature pitch issues here on GitHub](https://github.com/Microsoft/calculator/issues?q=is%3Aissue+is%3Aopen+project%3AMicrosoft%2Fcalculator%2F1).
+
+But using Feedback Hub is not required—_you_ can create feature pitches too! This document
+explains the elements of a good pitch and how we'll guide features from a pitch to a finished
+product. The [Feature Tracking board](https://github.com/Microsoft/calculator/projects/1) shows
+all the features we're working on and where they're at in the process.
+
+## Do I need to follow this process? Can I just start coding and submit a PR?
+You **do not** need to follow this process for bug fixes, performance improvements, or changes to the
+development tools. To contribute these changes, 
+[discuss the proposed change in an issue](https://github.com/Microsoft/calculator/issues/new)
+and then submit a pull request.
+
+You **do** need to follow this process for any change which "users will notice". This applies
+especially to new features and major visual changes.
+
+## Step 1: Feature pitch
+Feature pitches are submitted as issues on GitHub using the 
+[Feature Request template](https://github.com/Microsoft/calculator/issues/new?assignees=&labels=&template=feature_request.md&title=). 
+We encourage discussion on open issues, and as discussion progresses we will edit the issue description to refine the 
+idea until it is ready for review.
+
+We review pitches regularly, and will approve or close issues based on whether they broadly align with the 
+[Calculator roadmap](https://github.com/Microsoft/calculator/blob/master/docs/Roadmap.md). Approved pitches are moved 
+into [planning](https://github.com/Microsoft/calculator/projects/1) on the feature tracking board.
+
+## Step 2: Planning
+For most features, the output of this phase is a specification which describes how the feature will work, supported by 
+design renderings and code prototypes as needed. The original issue will continue to track the overall progress of the 
+feature, but we will create and iterate on spec documentation in the 
+[Calculator Spec repo](https://github.com/Microsoft/calculator-specs). Sometimes we'll learn new things about a feature 
+proposal during planning, and we'll edit or close the original pitch.
+
+We welcome community participation throughout planning. The best ideas often come from trying many ideas during 
+the planning phase. To enable rapid
+experimentation, we encourage developing and sharing rough ideas—maybe even with pencil and
+paper—before making designs pixel-perfect or making code robust and maintainable.
+
+After the [spec review](https://github.com/Microsoft/calculator-specs#spec-review) is completed, we will move the issue 
+into [implementation](https://github.com/Microsoft/calculator/projects/1) on the feature tracking board. In _some_ cases, 
+all of the details of an idea can be captured concisely in original feature pitch. When that happens, we may move ideas
+directly into implementation.
+
+## Step 3: Implementation
+A feature can be implemented by the original submitter, a Microsoft team member, or by other
+community members. Code contributions and testing help are greatly appreciated. Please let everyone know if you're 
+actively working on a feature to help avoid duplicated efforts from others.
+
+You might be able to reuse code written during the prototype process, although there will typically
+be more work required to make the solution robust. Once the code is ready, you can begin
+[submitting pull requests](../CONTRIBUTING.md).
+
+### Technical review
+As with all changes, the code for new features will be reviewed by a member of the Microsoft team
+before being checked in to the master branch.
+
+New features often need a more thorough technical review than bug fixes. When reviewing code for
+new features, the Microsoft team considers at least these items:
+
+- [ ] All items on the [Accessibility checklist](https://docs.microsoft.com/en-us/windows/uwp/design/accessibility/accessibility-checklist)
+  should be addressed.
+- [ ] All items on the [Globalization checklist](https://docs.microsoft.com/en-us/windows/uwp/design/globalizing/guidelines-and-checklist-for-globalizing-your-app)
+  should be addressed.
+- [ ] The change should be tested on the oldest version of Windows that the app supports. You can
+  find this version number in AppxManifest.xml. Any calls to APIs newer than that version should be
+  [conditionally enabled](https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/version-adaptive-apps).
+- [ ] The change should use only supported APIs. If there are any questions about whether legacy or
+  undocumented APIs are in use, the [Windows App Certification Kit](https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/windows-app-certification-kit)
+  should be run to check.
+- [ ] The change should save the user's progress if the app is
+  [suspended and resumed](https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/optimize-suspend-resume).
+  Code to handle these cases should be
+  [tested in the Visual Studio debugger](https://docs.microsoft.com/en-us/visualstudio/debugger/how-to-trigger-suspend-resume-and-background-events-for-windows-store-apps-in-visual-studio).
+- [ ] If the change [has customizations for particular device families](https://docs.microsoft.com/en-us/uwp/extension-sdks/device-families-overview),
+  it should be tested on those device families.
+- [ ] The change should be tested with the app window resized to the smallest possible size.
+- [ ] The change should be tested with light, dark, and high contrast themes. It should honor the
+  user's preferred [accent color](https://docs.microsoft.com/en-us/windows/uwp/design/style/color#accent-color-palette).
+- [ ] If the change adds new libraries or other dependencies:
+    - [ ] If the library is packaged with the app, the increased size of the binaries should be
+      measured.
+    - [ ] If the library is not maintained by Microsoft, the Microsoft team will need to set up a
+      plan to monitor the upstream library for changes like security fixes.
+    - [ ] If the library is being used under an open-source license, we must comply with the license
+      and credit third parties appropriately.
+- [ ] If the change adds code which runs during the app's startup path, or adds new XAML elements
+  which are loaded at startup:
+    - [ ] Run the perf tests to measure any increase in startup time. Move work out of the startup
+      path if possible.
+- [ ] If the change adds additional logging:
+    - [ ] All logging should use 
+         [TraceLogging](https://docs.microsoft.com/en-us/windows/desktop/tracelogging/trace-logging-about).
+    - [ ] Unnecessary log events should be removed, or configured so that they are collected only when
+      needed to debug issues or measure feature usage.
+- [ ] If the change reads user data from files or app settings:
+    - [ ] Verify that state saved in a previous version of the app can be used with the new version.
+- [ ] If the change makes network requests:
+    - [ ] Microsoft must plan to keep these dependencies secure and functional for the lifetime of
+      the app (which might be several years).
+    - [ ] The app should be fully functional if some network requests are slow or fail. Tools like
+      [Fiddler](https://docs.telerik.com/fiddler/knowledgebase/fiddlerscript/perftesting)
+      can be used to simulate slow or failed requests.
+
+## Step 4: Final product review and merge to master
+After the technical review is complete, the product team will review the finished product to make
+sure the final implementation is ready to [release to Windows customers](Roadmap.md#Releases).

Roadmap.md

@@ -0,0 +1,19 @@
+# Windows Calculator Roadmap
+
+Windows Calculator is under active development by Microsoft.
+
+## Focus
+
+In 2021, the Windows Calculator team is focused on:
+* Iterating upon the existing app design based on the latest guidelines for [Fluent Design](https://developer.microsoft.com/en-us/windows/apps/design) and [WinUI](https://github.com/microsoft/microsoft-ui-xaml).
+* Unblocking community contributions by identifying and addressing bottlenecks affecting developers, including:
+  * Migrating the codebase to C# ([#893](https://github.com/microsoft/calculator/issues/893))
+  * Releasing infinite-precision engine as standalone package ([#1545](https://github.com/microsoft/calculator/issues/1545)) and adding support for arbitrary expression parsing ([#526](https://github.com/microsoft/calculator/issues/526))
+  * Adding a settings page ([#596](https://github.com/microsoft/calculator/issues/596))
+* [Your feature idea here] - please review our [new feature development process](https://github.com/Microsoft/calculator/blob/main/docs/NewFeatureProcess.md) to get started!
+
+We welcome contributions of all kinds from the community, but especially those that support the efforts above. Please see our [contributing guidelines](https://github.com/Microsoft/calculator/blob/main/CONTRIBUTING.md) for more information on how to get involved.
+
+## Releases
+
+Windows Calculator is included in every Windows 10 release as a [provisioned Windows app](https://docs.microsoft.com/en-us/windows/application-management/apps-in-windows-10#provisioned-windows-apps). We also deliver updates through the [Microsoft Store](https://www.microsoft.com/store/productId/9WZDNCRFHVN5) approximately monthly.

action-ci.yml

@@ -0,0 +1,169 @@
+name: Windows Calculator Continuous Integration Pipeline
+run-name: WinCalc-CI-0.${{ github.run_number }}
+on:
+  push:
+    branches: [main, release/**, feature/**]
+  pull_request:
+    branches: [main, release/**, feature/**]
+  workflow_dispatch:
+jobs:
+  defineBuilds:
+    name: Define builds
+    runs-on: windows-latest 
+    env:
+      isPR: ${{ github.event_name == 'pull_request' }}
+    outputs:
+      version: ${{ steps.version.outputs.version }}
+      platformList: ${{ steps.platformList.outputs.platformList }}
+      unitTestPlatformList: ${{ steps.unitTestPlatformList.outputs.unitTestPlatformList }}
+    steps:
+      - name: Generate version number
+        id: version
+        run: |
+          $version = "0.${{ github.run_number }}.${{ github.run_attempt }}.0"
+          "version=`"$version`"" | Out-File $env:GITHUB_OUTPUT -Append
+        shell: pwsh
+      - name: Choose platforms to build
+        id: platformList
+        run: |
+          if ($env:isPR -eq $false) {
+            'platformList=["x64", "x86", "ARM64"]' | Out-File $env:GITHUB_OUTPUT -Append
+            echo 'Build all platforms.'
+          }
+          else {
+            'platformList=["x64"]' | Out-File $env:GITHUB_OUTPUT -Append
+            echo 'Build x64 only.'
+          }
+        shell: pwsh
+      - name: Choose platforms for unit test
+        id: unitTestPlatformList
+        run: |
+          if ($env:isPR -eq $false){
+            'unitTestPlatformList=["x64", "x86"]' | Out-File $env:GITHUB_OUTPUT -Append
+            echo 'Test x64, x86'
+          }
+          else{
+            'unitTestPlatformList=["x64"]' | Out-File $env:GITHUB_OUTPUT -Append
+            echo 'Test x64'
+          }
+        shell: pwsh
+
+  build:
+    needs: defineBuilds
+    name: Build
+    runs-on: windows-latest
+    strategy:
+      matrix:
+        platform: ${{ fromJSON(needs.defineBuilds.outputs.platformList) }}
+    env:
+      buildVersion: ${{ fromJSON(needs.defineBuilds.outputs.version) }}
+    steps:
+    - uses: actions/checkout@v4
+    - uses: microsoft/setup-msbuild@v2
+      name: Setup msbuild
+    - uses: nuget/setup-nuget@v2
+      name: Use nuget 6.x
+      with:
+        nuget-version: '6.x'
+    - run: nuget restore ./src/Calculator.sln
+      name: Restore nuget dependencies
+    - run: |
+        ./build/scripts/UpdateAppxManifestVersion.ps1 `
+          -AppxManifest ./src/Calculator/Package.appxmanifest `
+          -Version ${{ env.buildVersion }}
+      shell: pwsh
+      name: Set version number in AppxManifest
+    - run: |
+        msbuild ./src/Calculator.sln `
+          -bl:${{ github.workspace }}/output/Calculator.binlog `
+          -p:OutDir=${{ github.workspace }}\output\ `
+          -p:Platform=${{ matrix.platform }} `
+          -p:Configuration=Release `
+          -p:GenerateProjectSpecificOutputFolder=true `
+          -p:Version=${{ env.buildVersion }} `
+          -maxCpuCount `
+          -t:Publish `
+          -p:PublishDir=${{ github.workspace }}\output\publish\
+      shell: pwsh
+      name: Build calculator.sln
+    - uses: actions/upload-artifact@v4
+      name: Upload build outputs
+      with:
+        name: Build-${{ matrix.platform }}
+        path: ${{ github.workspace }}/output
+    - uses: actions/upload-artifact@v4
+      with:
+        name: Tools-${{ matrix.platform }}
+        path: ${{ github.workspace }}/build/scripts/SignTestApp.ps1
+
+  unitTests:
+    needs: [defineBuilds, build]
+    runs-on: windows-latest
+    name: Run unit tests
+    strategy:
+      matrix:
+        platform: ${{ fromJSON(needs.defineBuilds.outputs.unitTestPlatformList) }}
+    env:
+      testDir: ${{ github.workspace }}/download/CalculatorUnitTests/AppPackages/CalculatorUnitTests_Test
+    steps:
+    - uses: actions/download-artifact@v4
+      name: Download build outputs
+      with:
+        name: Build-${{ matrix.platform }}
+        path: ${{ github.workspace }}/download
+    - uses: actions/download-artifact@v4
+      name: Download tools
+      with:
+        name: Tools-${{ matrix.platform }}
+        path: ${{ github.workspace }}/download/tools
+    - run: |
+        ${{ github.workspace }}/download/tools/SignTestApp.ps1 -AppToSign ${{ env.testDir }}/CalculatorUnitTests.msix
+      shell: pwsh
+      name: Install test certificate
+    - uses: ilammy/msvc-dev-cmd@v1  # this is a workaround because microsoft/vstest-action is broken.
+      name: Setup dev tools
+    - run: vstest.console.exe ${{ env.testDir }}/CalculatorUnitTests.msix /Platform:${{ matrix.platform }}
+      name: Run unit tests
+        
+  uiTests:
+    needs: build
+    runs-on: windows-latest
+    name: Run UI tests (x64)
+    env:
+      appDir: ${{ github.workspace }}/download/Calculator/AppPackages/Calculator*_Test
+      pubDir: ${{ github.workspace }}/download/publish
+    steps:
+    - uses: actions/download-artifact@v4
+      name: Download build outputs
+      with:
+        name: Build-x64
+        path: ${{ github.workspace }}/download
+    - uses: actions/download-artifact@v4
+      name: Download tools
+      with:
+        name: Tools-x64
+        path: ${{ github.workspace }}/download/tools
+    - run: |
+        Set-DisplayResolution -Width 1920 -Height 1080 -Force
+      shell: pwsh
+      name: Set screen resolution
+    - run: |
+        ${{ github.workspace }}/download/tools/SignTestApp.ps1 -AppToSign '${{ env.appDir }}/Calculator_*.msixbundle'
+        ${{ env.appDir }}/Add-AppDevPackage.ps1 -Force
+      shell: powershell
+      name: Install app
+    - run: |
+        Invoke-WebRequest 'https://github.com/microsoft/WinAppDriver/releases/download/v1.2.1/WindowsApplicationDriver_1.2.1.msi' `
+          -OutFile (New-Item -Path '${{ github.workspace }}/download2/wad.msi' -Force)
+        cd ${{ github.workspace }}/download2
+        msiexec.exe /i wad.msi /quiet /passive
+      shell: powershell
+      name: Install WindowsApplicationDriver
+    - uses: ilammy/msvc-dev-cmd@v1  # this is a workaround because microsoft/vstest-action is broken.
+      name: Setup dev tools
+    - run: |
+        vstest.console.exe ${{ github.workspace }}\download\publish\CalculatorUITests.dll `
+          /Platform:x64 `
+          /Settings:${{ github.workspace }}\download\publish\CalculatorUITests.ci.runsettings
+      shell: pwsh
+      name: Run UI tests

bug_report.md

@@ -0,0 +1,60 @@
+---
+name: Bug report
+about: Report a problem with Calculator
+title: ''
+labels: ''
+assignees: ''
+
+---
+<!--
+Before filing a bug
+- Ensure the bug reproduces on the latest version of the app.
+- Search existing issues and make sure this issue is not already filed.
+-->
+
+**Describe the bug**
+<!-- A clear and concise description of what the bug is. -->
+
+**Steps To Reproduce**
+<!--
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+-->
+
+**Expected behavior**
+<!-- A clear and concise description of what you expected to happen. -->
+
+**Screenshots**
+<!-- If applicable, add screenshots to help explain your problem. -->
+
+**Device and Application Information**
+ - OS Build:
+ - Architecture:
+ - Application Version:
+ - Region:
+ - Dev Version Installed:
+
+<!--
+Run the following commands in Powershell and copy/paste the output.
+" - OS Build: $([Environment]::OSVersion.Version)"
+" - Architecture: $((Get-AppxPackage -Name Microsoft.WindowsCalculator).Architecture)"
+" - Application Version: $((Get-AppxPackage -Name Microsoft.WindowsCalculator).Version)"
+" - Region: $((Get-Culture).Name)"
+" - Dev Version Installed: $($null -ne (Get-AppxPackage -Name Microsoft.WindowsCalculator.Dev))"
+-->
+
+**Additional context**
+<!-- Add any other context about the problem here. -->
+
+**Requested Assignment**
+<!--
+Some people just want to report a bug and let someone else fix it.
+Other people want to not only submit the bug report, but fix it as well.
+Both scenarios are completely ok. We just want to know which one it is.
+Please indicate which bucket you fall into by keeping one and removing the other.
+-->
+If possible, I would like to fix this.
+I'm just reporting this problem.  I don't want to fix it.

feature_request.md

@@ -0,0 +1,54 @@
+---
+name: Feature request
+about: Propose a new feature in the app
+title: ''
+labels: 'Enhancement'
+assignees: ''
+
+---
+
+<!--
+See https://github.com/Microsoft/calculator/blob/main/docs/NewFeatureProcess.md for suggestions on how to write a good feature pitch. Just want to submit an idea quickly? Try Feedback Hub instead: https://insider.windows.com/en-us/fb/?contextid=130
+-->
+
+**Problem Statement**
+<!--
+What problem are we trying to solve? Who’s the target audience? Is there a customer need or pain point we need to remedy? Is there a business goal or metric we are trying to improve? Do we have a hypothesis we want to prove or disprove?
+-->
+
+**Evidence or User Insights**
+<!--
+Why should we do this? Potential sources of data: Feedback Hub, other GitHub issues, other anecdotes from listening to customers in person or online, request from another team, telemetry data, user research, market or competitive research
+-->
+
+**Proposal**
+<!--
+How will the solution/feature help us solve the problem? How will it meet the target audience’s needs? If there are business goals or metrics, how does this improve them?
+-->
+
+**Goals**
+<!--
+What you want to accomplish with this feature. Typical examples include
+"User Can *perform some task*"
+-->
+
+**Non-Goals**
+<!--
+Things we are explicitly not doing or supporting or that are out of scope, including reasons why.
+-->
+
+**Low-Fidelity Concept**
+<!--
+Show as much of the experience as needed to explain the idea. This can be as simple as a napkin drawing but can also be a code prototype, or a design comp. Keep it simple at this stage, as it can be refined later during the pre-production stage.
+-->
+
+**Requested Assignment**
+<!--
+Some people just want to suggest a feature and let someone else implement it.
+Other people want to not only suggest a feature, but implement it as well.
+Both scenarios are completely ok. We just want to know which one it is.
+We are likely to prioritize the review of feature requests if they already have someone who can implement them.
+Please indicate which bucket you fall into by keeping one and removing the other.
+-->
+If possible, I would like to implement this.
+I'm just suggesting this idea.  I don't want to implement it.

localization_suggestion.md

@@ -0,0 +1,54 @@
+---
+name: Localization Suggestion
+about: Report a problem or suggested change to Calculator's localized content.
+title: '[Localization] '
+labels: 'Area: World-Readiness'
+assignees: ''
+---
+<!--
+PLEASE NOTE: 
+We cannot _merge_ any suggested localization changes to our localized resources files. These files are automatically generated from an internal localization process.  Any suggestion submitted this way will be duplicated into our internal localization system, and then closed here.
+
+Alternatively, you can launch feedback-hub://, click on the "Language Community" tab on the left-side of the app, and follow the steps to submit a localization suggestion that way.  (The "Language Community" tab currently will only be visible if your system is running a non-English language).
+
+Before filing a bug
+- Ensure the bug reproduces on the latest version of the app.
+- Search existing issues and make sure this issue is not already filed.
+-->
+
+**Describe the bug**
+<!-- A clear and concise description of what the bug is. -->
+
+**Steps To Reproduce**
+<!--
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+-->
+
+**Expected behavior**
+<!-- A clear and concise description of what you expected to happen. -->
+
+**Screenshots**
+<!-- If applicable, add screenshots to help explain your problem. -->
+
+**Device and Application Information**
+ - OS Build:
+ - Architecture:
+ - Application Version:
+ - Region: 
+ - Dev Version Installed: 
+ 
+<!--
+Run the following commands in Powershell and copy/paste the output.
+" - OS Build: $([Environment]::OSVersion.Version)"
+" - Architecture: $((Get-AppxPackage -Name Microsoft.WindowsCalculator).Architecture)"
+" - Application Version: $((Get-AppxPackage -Name Microsoft.WindowsCalculator).Version)"
+" - Region: $((Get-Culture).Name)"
+" - Dev Version Installed: $($null -ne (Get-AppxPackage -Name Microsoft.WindowsCalculator.Dev))"
+-->
+
+**Additional context**
+<!-- Add any other context about the problem here. -->

pull_request_template.md

@@ -0,0 +1,16 @@
+## Fixes #.
+
+
+### Description of the changes:
+-
+-
+-
+
+### How changes were validated:
+<!--Review https://github.com/Microsoft/calculator/blob/main/CONTRIBUTING.md and ensure all contributing requirements are met.
+
+Specify how you tested your changes (i.e. manual/ad-hoc testing, automated testing, new automated tests added)-->
+-
+-
+-
+

resourceManagement.yml

@@ -0,0 +1,135 @@
+id: 
+name: GitOps.PullRequestIssueManagement
+description: GitOps.PullRequestIssueManagement primitive
+owner: 
+resource: repository
+disabled: false
+where: 
+configuration:
+  resourceManagementConfiguration:
+    scheduledSearches:
+    - description: 
+      frequencies:
+      - hourly:
+          hour: 3
+      filters:
+      - isPullRequest
+      - isOpen
+      - hasLabel:
+          label: needs author feedback
+      - noActivitySince:
+          days: 7
+      - isNotLabeledWith:
+          label: no recent activity
+      actions:
+      - addLabel:
+          label: no recent activity
+      - addReply:
+          reply: This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **7 days**. Thank you for your contributions to Windows Calculator!
+    eventResponderTasks:
+    - if:
+      - payloadType: Issue_Comment
+      - hasLabel:
+          label: no recent activity
+      then:
+      - removeLabel:
+          label: no recent activity
+      description: 
+    - if:
+      - payloadType: Issues
+      - isAction:
+          action: Closed
+      then:
+      - removeLabel:
+          label: needs pitch review
+      - removeLabel:
+          label: needs more info
+      - removeLabel:
+          label: needs spec
+      - removeLabel:
+          label: no recent activity
+      - removeLabel:
+          label: help wanted
+      - removeLabel:
+          label: needs spec review
+      - removeLabel:
+          label: needs spec
+      description: 
+      triggerOnOwnActions: true
+    - if:
+      - payloadType: Pull_Request_Review
+      - isAction:
+          action: Submitted
+      - isReviewState:
+          reviewState: Changes_requested
+      then:
+      - addLabel:
+          label: needs author feedback
+      description: 
+    - if:
+      - payloadType: Pull_Request
+      - isActivitySender:
+          issueAuthor: True
+      - not:
+          isAction:
+            action: Closed
+      - hasLabel:
+          label: needs author feedback
+      then:
+      - removeLabel:
+          label: needs author feedback
+      description: 
+    - if:
+      - payloadType: Issue_Comment
+      - isActivitySender:
+          issueAuthor: True
+      - hasLabel:
+          label: needs author feedback
+      then:
+      - removeLabel:
+          label: needs author feedback
+      description: 
+    - if:
+      - payloadType: Pull_Request_Review
+      - isActivitySender:
+          issueAuthor: True
+      - hasLabel:
+          label: needs author feedback
+      then:
+      - removeLabel:
+          label: needs author feedback
+      description: 
+    - if:
+      - payloadType: Pull_Request
+      - not:
+          isAction:
+            action: Closed
+      - hasLabel:
+          label: no recent activity
+      then:
+      - removeLabel:
+          label: no recent activity
+      description: 
+    - if:
+      - payloadType: Issue_Comment
+      - hasLabel:
+          label: no recent activity
+      then:
+      - removeLabel:
+          label: no recent activity
+      description: 
+    - if:
+      - payloadType: Pull_Request_Review
+      - hasLabel:
+          label: no recent activity
+      then:
+      - removeLabel:
+          label: no recent activity
+      description: 
+    - if:
+      - payloadType: Issue_Comment
+      then:
+      - cleanEmailReply
+      description: 
+onFailure: 
+onSuccess: