Azure · tzhanl · Jul 15, 2020 · Jun 5, 2020 · Jun 5, 2020 · Jun 5, 2020
diff --git a/.docsettings.yml b/.docsettings.yml
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -10,32 +10,40 @@
 
 # Core
 /sdk/core/abort-controller/ @chradek @xirzec @bterlson
-/sdk/core/core-amqp/ @ramya-rao-a @chradek
+/sdk/core/core-amqp/ @ramya-rao-a @chradek @richardpark-msft @HarshaNalluru
 /sdk/core/core-auth/ @daviwil @xirzec @bterlson
-/sdk/core/core-http/ @daviwil @xirzec @bterlson
+/sdk/core/core-http/ @daviwil @xirzec @bterlson @chradek @jeremymeng
 /sdk/core/core-lro/ @sadasant @xirzec @bterlson
 /sdk/core/core-paging/ @daviwil @xirzec @bterlson
-/sdk/core/core-tracing/ @xirzec @bterlson
-/sdk/core/logger @xirzec @bterlson
+/sdk/core/core-tracing/ @xirzec @bterlson @chradek
+/sdk/core/logger @xirzec @bterlson @chradek
 
 # Service teams
-/sdk/appconfiguration/ @richardpark-msft
+/sdk/appconfiguration/ @richardpark-msft @chradek
 
 /sdk/batch/ @xingwu1 @matthchr @bgklein
-/sdk/cosmosdb/ @southpolesteve
+/sdk/cosmosdb/ @southpolesteve @zfoster
 
-/sdk/eventhub/ @ramya-rao-a @chradek @richardpark-msft
-/sdk/servicebus/ @ramya-rao-a @chradek @ramya0820
+/sdk/eventhub/ @ramya-rao-a @chradek @richardpark-msft @HarshaNalluru
+/sdk/servicebus/ @ramya-rao-a @chradek @richardpark-msft @HarshaNalluru
 
-/sdk/identity/ @daviwil @jonathandturner
+/sdk/identity/ @schaabs @daviwil @jonathandturner @sadasant
 /sdk/keyvault/ @jonathandturner @sadasant
 /sdk/storage/ @XiaoningLiu @jeremymeng @HarshaNalluru @vinjiang @jiacfan @ljian3377
 
-/sdk/test-utils/ @HarshaNalluru
-/sdk/textanalytics/ @xirzec
+/sdk/tables/ @mahdiva @joheredi
+
+/sdk/test-utils/ @HarshaNalluru @sadasant
+/sdk/textanalytics/ @xirzec @willmtemple
+/sdk/formrecognizer/ @jeremymeng @willmtemple
+
+/sdk/search/ @xirzec @sarangan12
+
+# Smoke Tests
+/common/smoke-test/ @ramya-rao-a @chradek @jonathandturner @sadasant @jeremymeng @southpolesteve
 
 # API review files
-/sdk/**/review/*api.md @bterlson
+/sdk/**/review/*api.md @bterlson @xirzec
 
 # Management Plane
 /**/*Management*.ts @qiaozha

diff --git a/.gitignore b/.gitignore
@@ -134,7 +134,6 @@ dist
 dist-*
 test-dist
 test-dist*
-browser
 test-browser
 typings
 typedoc
@@ -147,6 +146,3 @@ sdk/cosmosdb/cosmos/lib
 
 # autorest generated files
 swagger/*.json
-
-# library-specific ignores
-sdk/keyvault/*/src/**/*.js
diff --git a/.scripts/gulp.ts b/.scripts/gulp.ts
@@ -118,7 +118,7 @@ export async function setAutoPublish(azureSdkForJsRoot: string, include?: RegExp
             continue;
         }
 
-        config.content["authPublish"] = true;
+        config.content["autoPublish"] = true;
         fs.writeFileSync(config.path, JSON.stringify(config.content, undefined, "  ") + "\n");
         _logger.log("Saved");
     }

diff --git a/.scripts/readme.ts b/.scripts/readme.ts
@@ -102,7 +102,7 @@ export async function getSinglePackageName(typescriptReadmePath: string): Promis
     const readmeBuffer: Buffer = await fs.readFile(typescriptReadmePath);
     const yamlSectionBuffer = await getYamlSection(readmeBuffer, "``` yaml $(typescript)", "```");
     const yamlSectionText = yamlSectionBuffer.toString();
-    const yamlSection = yaml.safeLoad(yamlSectionText);
+    const yamlSection:any = yaml.safeLoad(yamlSectionText);
     return yamlSection["typescript"]["package-name"];
 }
 

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -14,7 +14,7 @@ contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additio
 
 # How to contribute to the Azure SDK for Javascript
 
-There are many ways that you can contribute to the Azure Event Hubs client project:
+There are many ways that you can contribute to the Azure SDK for JavaScript project:
 
 - Submit a bug
 - Submit a code fix for a bug
@@ -127,11 +127,43 @@ Run `rush rebuild` from anywhere in the repo to rebuild all projects from scratc
 
 Run `rush build -t <packagename>` to build a single project, and all local projects that it depends on. You can pass `-t` multiple times to build multiple projects. This works for `rush rebuild` as well. Keep in mind that Rush refers to packages by their full names, so packages will be named something like `@azure/<servicename>`.
 
-By default, Rush only displays things written to `STDERR`. If you want to see the full output, pass `--verbose` to any of the build commands. This is also true for script commands (see below).
+By default, Rush only displays things written to `STDERR`. If you want to see the full output, pass `--verbose` to any of the build commands.
+
+### Testing
+
+If you want to run the tests of a specific project, go to that project's folder and execute `rushx test`. All of the tests will automatically run both in NodeJS and in the browser. To target these environments individually, you can run `rushx test:node` and `rushx test:browser`.
+
+By default, these npm scripts run previously recorded tests. The recordings have been generated by using a custom recording library called [test-utils-recorder](https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/test-utils/recorder/README.md). We will examine how to run recorded tests and live tests in the following sections.
+
+#### Recorded tests
+
+Most of the tests in our projects run in playback mode by default, i.e they make no network requests to the real services. For HTTP requests made in each test case, there is a recorded response that reproduces the service behavior. The readme file in the `test` folder of each package will indicate whether the package uses recorded tests or not.
+
+#### Live tests
+
+To use the `rushx test` command to run the tests against live resources, you must:
+
+- Set the environment variable `TEST_MODE` to `live`.
+- Have previously created the necessary Azure resources needed by the tests.
+- Set the appropriate environment variables to point to these resources.
+
+The readme file in the `test` folder of each package lists the Azure resources and the environment variables needed.
+
+> Note: Our projects use dotenv to allow you to use `.env` files to set environment variables. Find the `sample.env` file nearest to the project you want to test to see a template of the expected `.env` file.
+
+You can create the necessary Azure resources on your own, or automate this process by using the script called `New-TestResources.ps1` which uses ARM templates defined in a file named `test-resources.json` that exists in each project's folder. Follow the steps in [`Example 1 of New-TestResources.ps1`](https://github.com/Azure/azure-sdk-for-js/blob/master/eng/common/TestResources/New-TestResources.ps1.md#example-1) to set up a service principal and deploy the live test resources.
+
+#### Regenerating recordings
+
+If you modify the network calls (both the number of calls or their shape) either by changing the tests or source code of the project you're working on, the recordings will need to be re-generated.
+
+Regenerating the recordings has the same requirements as running the live tests. You will be using the same `test` npm script with the environment variables pointing to previously created Azure resources. The only difference is that the `TEST_MODE` environment variable needs to be set to `record`. When this process finishes without errors, the recordings will be updated.
+
+For more information the recorder, please visit the [test-utils-recorder's readme](https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/test-utils/recorder/README.md).
 
 ### Other NPM scripts
 
-Most package scripts are exposed as Rush commands. Use `rush <scriptname>` in place of `npm run <scriptname>` to run the package script in all projects. Navigate to a project's directory and substitute `rushx` for `rush` to run the script for just the current project. Run `rush <scriptname> --help` for more information about each script.
+Most package scripts are exposed as Rush commands. Use `rushx <scriptname>` in place of `npm run <scriptname>` to run the package script in all projects. Navigate to a project's directory and substitute `rushx` for `rush` to run the script for just the current project. Run `rush <scriptname> --help` for more information about each script.
 
 All projects have at least the following scripts:
 
@@ -186,7 +218,7 @@ Generally speaking, the following commands are roughly equivalent:
 
 ## Onboarding a new library
 
-To add a new library to the repo, update `rush.json` in the root of the repo and add a new entry to the `projects` array at the bottom of the file. The package name must be the full name of the package as specified in its package.json. Your new library must follow our [repository structure](https://github.com/Azure/azure-sdk/blob/master/docs/engineering-system/repo-structure.md) (specifically, it must be located at `sdk/<servicename>/<packagename>`) and your library's package.json must contain the required scripts as documented [above](#other-npm-scripts). Once the library is added, run `rush update` to install and link dependencies. If your new library has introduced a dependency version conflict, this command will fail. See [above](#resolving-dependency-version-conflicts) to learn how to resolve dependency version conflicts.
+To add a new library to the repo, update `rush.json` in the root of the repo and add a new entry to the `projects` array at the bottom of the file. The package name must be the full name of the package as specified in its package.json. Your new library must follow our [repository structure](https://github.com/Azure/azure-sdk/blob/master/docs/policies/repostructure.md) (specifically, it must be located at `sdk/<servicename>/<packagename>`) and your library's package.json must contain the required scripts as documented [above](#other-npm-scripts). Once the library is added, run `rush update` to install and link dependencies. If your new library has introduced a dependency version conflict, this command will fail. See [above](#resolving-dependency-version-conflicts) to learn how to resolve dependency version conflicts.
 
 Rush assumes that anything printed to `STDERR` is a warning. Your package scripts should avoid writing to `STDERR` unless emitting warnings or errors, since this will cause Rush to flag them as warnings during the execution of your build or script command. If your library uses a tool that can't be configured this way, you can still append `2>&1` to the command which will redirect all output to `STDOUT`. You won't see warnings show up, but Rush will still consider the command to have failed as long as it returns a nonzero exit code.
 

diff --git a/README.md b/README.md
@@ -1,36 +1,24 @@
 # Azure SDK for JavaScript
 
-[![Packages](https://img.shields.io/badge/packages-latest-blue.svg)](https://azure.github.io/azure-sdk/releases/latest/js.html) [![Dependencies](https://img.shields.io/badge/dependencies-analyzed-blue.svg)](https://azuresdkartifacts.blob.core.windows.net/azure-sdk-for-js/dependencies/dependencies.html)
+[![Packages](https://img.shields.io/badge/packages-latest-blue.svg)](https://azure.github.io/azure-sdk/releases/latest/js.html) [![Dependencies](https://img.shields.io/badge/dependency-report-blue.svg)](https://azuresdkartifacts.blob.core.windows.net/azure-sdk-for-js/dependencies/dependencies.html) [![DependencyGraph](https://img.shields.io/badge/dependency-graph-blue.svg)](https://azuresdkartifacts.blob.core.windows.net/azure-sdk-for-js/dependencies/InterdependencyGraph.html)
 
-This repository is intended for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our [public developer docs](https://docs.microsoft.com/en-us/javascript/azure/) or our versioned [developer docs](https://azure.github.io/azure-sdk-for-js).
+This repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our [public developer docs](https://docs.microsoft.com/en-us/javascript/azure/) or our versioned [developer docs](https://azure.github.io/azure-sdk-for-js).
 
 ## Getting started
 
 For your convenience, each service has a separate set of libraries that you can choose to use instead of one, large Azure package. To get started with a specific library, see the **README.md** file located in the library's project folder. You can find service libraries in the `/sdk` directory.
 
 Each service might have a number of libraries available from each of the following categories:
 
-- [Client - November 2019 Releases](#Client-November-2019-Releases)
+- [Client - New Releases](#Client-New-Releases)
 - [Client - Previous Versions](#Client-Previous-Versions)
 - [Management](#Management)
 
-### Client: November 2019 Releases
+### Client: New Releases
 
 New wave of packages that we are announcing as **GA** and several that are currently releasing in **preview** on `npm`. These libraries allow you to use and consume existing resources and interact with them. These libraries share a number of core functionalities found in the Azure Core package such as retries, logging, transport protocols, authentication protocols, etc. Learn more about these libraries by reading [the guidelines](https://azure.github.io/azure-sdk/typescript/guidelines/) that they follow.
 
-The libraries released in the November 2019 GA release:
-
-- [@azure/storage-blob](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/storage/storage-blob)
-- [@azure/storage-queue](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/storage/storage-queue)
-- [@azure/keyvault-keys](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/keyvault/keyvault-keys)
-- [@azure/keyvault-secrets](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/keyvault/keyvault-secrets)
-- [@azure/identity](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/identity/identity)
-
-The libraries released in the November 2019 preview:
-- [@azure/storage-file-share@next](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/storage/storage-file-share)
-- [@azure/event-hubs@next](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/eventhub/event-hubs)
-- [@azure/keyvault-certificates@next](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/keyvault/keyvault-certificates)
-- [@azure/app-configuration@next](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/appconfiguration/app-configuration)
+You can find the [most up to date list of all of the new packages on our page](https://azure.github.io/azure-sdk/releases/latest/index.html#javascript-packages)
 
 > NOTE: If you need to ensure your code is ready for production use one of the stable, non-preview libraries.