Run Clipboard test sequentially, this is not eliminating potential interferences, but is an improvement in my observations, the next step would be to add a Clear in the try/finally block in every test.
enabled nullability in ClipboardTests
Used fluent assertions, particularly BeEquivalentTo was helpful to make some tests more specific. Several test names didn't match the content due to a copy/paste mistake
Run Clipboard test sequentially, this is not eliminating potential interferences, but is an improvement in my observations, the next step would be to add a Clear in the try/finally block in every test. enabled nullability in ClipboardTests Used fluent assertions, particularly BeEquivalentTo was helpful to make some tests more specific. Several test names didn't match the content due to a copy/paste mistake
Microsoft Reviewers: Open in CodeFlow