Automated UI Tests for the Scientific Calculator Mode

[edwcry]

Problem Statement
Currently, the basic smoke tests for Scientific calculator mode are all manual. There aren't any automated UI tests for calculator modes other than the standard calculator mode. Automation testing is faster than manual testing. Repeated test that can be automated, should be automated.

Evidence or User Insights
It would be helpful to developers and testers to have some streamlined, reliable UI tests for the Scientific calculator mode.

Proposal

• These tests would allow developers to know that their feature/code change, when introduced to the application, does not break other aspects of the application.
• These tests allow testers to focus on more creative, testing scenarios during manual testing rather than spending a lot of extra time executing tests that an automaton could complete.

Goals

• Replace basic, repeatable manual tests, with streamlined, reliable automated UI tests for the Scientific calculator mode
• Use these tests as a gate when checking in new features

Non-Goals

• The UI automated tests are not a replacement for Unit tests
• The UI automated tests will not cover end-to-end testing (It will cover smoke/BVT type tests)

Low-Fidelity Concept
Read through "ManualTests.md" (https://github.com/microsoft/calculator/blob/master/docs/ManualTests.md). Would you prefer to execute these tests manually, or if possible, execute most of these through automation?

Requested Assignment
If possible, I would like to implement this.

[MicrosoftIssueBot]

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

This issue has been automatically marked as stale because it has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. Thank you for your contributions to Windows Calculator!

[grochocki]

cc: @sanderl