From ee6b117631a4dd58df420ee5c05086d604d7be57 Mon Sep 17 00:00:00 2001 From: mariam-abdulla Date: Thu, 12 Dec 2024 14:26:42 +0100 Subject: [PATCH] Update titles' suggestions --- docs/RFCs/011-Sdk-Testing-Platform.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/RFCs/011-Sdk-Testing-Platform.md b/docs/RFCs/011-Sdk-Testing-Platform.md index 096ae40053..eaeb75dc23 100644 --- a/docs/RFCs/011-Sdk-Testing-Platform.md +++ b/docs/RFCs/011-Sdk-Testing-Platform.md @@ -22,13 +22,13 @@ The reason for opting-in/out this experience is We want to design in a way that is future proof and easy to keep backwards compatible. -### Proposed solution +## Proposed solution Make this option configurable in global.json. We chose global.json because it's located on the current directory level or its parent directories and is picked up by the dotnet sdk. Here are some global.json suggestions: -1. Enable/Disable Testing Platform +### 1. Enable/Disable Testing Platform ```json { @@ -43,7 +43,7 @@ What if we want to support another test runner? We simply can't, with this approach we either use the testing platform, or fallback to vstest if this property was set to false. -2. Specify the Tool +### 2. Specify the Test Runner Tool ```json { @@ -60,7 +60,7 @@ We still could support more options. But if, for some reason, the latest version of the testing platform was broken, we will break as well. -3. Specify the Tool and Version +### 3. Specify the Test Runner Tool and Version ```json {