For the automatic functional tests, we should add instructions on how to write functional testing scripts in a README on the Scuba git repo.

Example of a test script:

$WebDriversPath = Join-Path -Path (Get-Module Selenium).ModuleBase -ChildPath "assemblies"
.\Testing\Functional\SmokeTest\UpdateSelenium.ps1 -webDriversPath $WebDriversPath

$TestContainers = @()
$TestContainers += New-PesterContainer -Path "./Testing/Functional/Products" `
-Data @{
	TenantDomain = "cisaent.onmicrosoft.com";
	Thumbprint = "<your thumbprint here>";
	AppId = "<app id>";
	TenantDisplayName = "Cybersecurity and Infrastructure Security Agency";
	ProductName = "teams";
	M365Environment = "gcc" }
Invoke-Pester -Container $TestContainers -Output Detailed

Yes, and the document should be wholly separate from the user-facing documentation since it is for developers. Either we create a docs folder so its out of the way and we can further organize into subfolders or create a docs folder under Testing perhaps. Either way, it should be largely transparent and out of the way for a normal user who will never create a test plan or script.

This is related to but distinct from #877.

The PR #983 fixing this issue is pushed to Halibut - changing the targeted release.