Noah Falk d783a8c812 Update library testing docs page to reduce confusion (#54324) ... * Add warning on unmaintained testing doc page * Update testing.md Some example text that seems more clear to me, but only offered as a suggestion. Feel free to adjust it or if you want to use it as-is please double check what I wrote is accurate : ) I think the useful elements are: 1. Being explicit about what workflow steps need to happen in total 2. Being explicit about which commands are covering the entire workflow and which ones are only covering a part of it 3. Show the simple "do-it-all" options first before showing more complex partial options. Glancing at the first example and blindly copying it should land in the pit of success. Co-authored-by: Viktor Hofer <viktor.hofer@microsoft.com>		2021-06-23 09:00:47 +02:00
..
filtering-tests.md	Cleanup PlatformSpecific/SkipOnMono attributes that skip a platform (#50907)	2021-04-09 13:20:18 +02:00
testing-android.md	Update testing-android.md (#50484)	2021-03-31 10:03:27 -07:00
testing-apple.md	Update iOS workflow docs to clarify simulator/device os split (#50366)	2021-04-05 07:55:20 -04:00
testing-wasm.md	[wasm][testing] hosting echo server in xharness process (#52923)	2021-06-09 17:32:58 +02:00
testing.md	Update library testing docs page to reduce confusion (#54324)	2021-06-23 09:00:47 +02:00