Azure SignalR Service E2E Tests
Перейти к файлу
microsoft-github-policy-service[bot] 65e751f577
Microsoft mandatory file (#36)
Co-authored-by: microsoft-github-policy-service[bot] <77245923+microsoft-github-policy-service[bot]@users.noreply.github.com>
2023-06-01 10:37:54 +08:00
ManagementE2ETest E2E test for management sdk & AAD (#25) 2020-10-20 15:51:53 +08:00
SDKTest update (#35) 2022-10-26 14:55:36 +08:00
SDKTestWithAAD update (#35) 2022-10-26 14:55:36 +08:00
ServerlessTest update (#35) 2022-10-26 14:55:36 +08:00
arm Adding ARM templates for testing (#21) 2020-05-19 17:36:16 +08:00
server remove secrets 2022-05-06 08:09:46 +08:00
.dockerignore Add docker builder 2018-08-23 12:53:31 +08:00
.gitattributes Add docker builder 2018-08-23 12:53:31 +08:00
.gitignore update e2e test (#24) 2020-09-09 17:22:34 +08:00
Dockerfile update (#35) 2022-10-26 14:55:36 +08:00
LICENSE Initial commit 2018-08-01 02:15:35 -07:00
README.md update readme.md (#26) 2020-10-20 17:12:43 +08:00
RuntimeBase.Dockerfile update (#35) 2022-10-26 14:55:36 +08:00
SECURITY.md Microsoft mandatory file (#36) 2023-06-01 10:37:54 +08:00
build-management-image.sh update (#35) 2022-10-26 14:55:36 +08:00
build-sdk-image.sh update (#35) 2022-10-26 14:55:36 +08:00
run-server-aad.sh set aside the test cases for serverless (#31) 2021-08-04 18:00:18 +08:00
run.sh E2E test for management sdk & AAD (#25) 2020-10-20 15:51:53 +08:00
test.ps1 Fix bugs of async void in hubContext method and some other minor changes (#20) 2019-05-30 12:49:42 +08:00
test.sh Fix bugs of async void in hubContext method and some other minor changes (#20) 2019-05-30 12:49:42 +08:00

README.md

Azure SignalR Test

The project to provide automation E2E test on SignalR sdk and service runtime.

How to build and run

First check the SDK version needed. Each SDKVerison will build a separate docker image and the tag is the sdk version.

declare -a SDKVersion=("1.5.0" "1.5.1")

Run tests for Server SDK

./build-sdk-image.sh

Then you can run the test with Azure SignalR Service

docker run -e Azure__SignalR__ConnectionString="<your connection string>" signalr-test:<sdk version>

Run tests with app server AAD Auth

This test case is for a specific scenario, in which our customer used AAD Auth to authenticate their incoming requests.

Our SDK will simply pass most of the claims in the given JWT Token (for accessing their app server) to the newly generated JWT Token (for connecting to our service).

However, there are still some internal claims that will not be passed.

This test is to check if any of these unpassed claims will cause problems while connecting to ASRS.

docker run -e Azure__SignalR__ConnectionString="<your connection string>" -e signalr-test:<sdk version> -e clientId="<clientId>" -e clientSecret="<clientSecret>" -e tenantId="<tenantId>" run-server-aad.sh

The clientId, clientSecret, tenantId here could be any valid AAD Application.

Run tests for Management SDK

./build-management-image.sh

Then you can run the test with Azure SignalR Service

docker run -e Azure__SignalR__ConnectionString="<your connection string>" signalr-management-sdk-test:<sdk version>

How to upload images to private container registry

az login // use microsoft account
az acr login -n genevadev

Then docker push <image>

Test Coverage

  • Connect / Echo / Broadcast / AllExcept
  • Group join / leave
  • Send Group / Groups / Group Except / OthersInGroup
  • Send User / Users
  • JWT Auth
  • Generic hub / 128 character length hub name support

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.