In this step we will create a PetStoreTest project to perform an integration test against the PetStoreDev stack. We will test:
The automated tests we will create in this step require an IMAP account with subaddressing capabilities. For example, Gmail, Outlook or AWS WorkMail will work just fine. AWS Cognito will email authorization codes to an email account during the tests. For instance, the sign-up process will email the new user a authorization code. Our sign-up process test must log into the user's email account, find the email containing the authorization code and then use that code to finalize the sign-up process.
AWS Cognito requires each user to have a unique email address. We don't want to create a new email address each time we run the tests and deleting users from the Cognito User Pool is not convenient or always what we what.
Lucky for us, email subaddressing is a nifty feature that allows you to use a dynamic email address alias. For example, if you email address is firstname.lastname@example.org, you can send email to that address with the alias email@example.com. As far as AWS Cognito is concerned, this alias is a unique email address. This means we can use a single Gmail account to create and test multiple AWS Cognito accounts where each of the AWS Cognito accounts is associated with a unique Gmail address alias.
For the purposes of this demo we will use the AWS WorkMail service. AWS WorkMail accounts currently cost $4/mo but you get a free 30 day trail. One nice feature of the AWS WorkMail service is that it offers a "free" subdomain so you don't have to configure any domains or spend a lot of time setting things up.
dotnet new mstest -o PetStoreTests
dotnet sln add PetStoreTests\PetStoreTests.csproj
The new PetStoreTests project is added to your solution.
dotnet sln add PetStoreTests/PetStoreTests.csproj
dotnet tool install -g dotnet-guid
A guid is printed to the console. Make a note of this GUID as you will need it in the next step.
<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net6.0</TargetFramework> <Nullable>enable</Nullable> <IsPackable>false</IsPackable> <UserSecretsId>66025cbf-84df-4bb8-b739-175a8d130e36</UserSecretsId> </PropertyGroup> <ItemGroup> <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.0.0" /> <PackageReference Include="MSTest.TestAdapter" Version="2.2.10" /> <PackageReference Include="MSTest.TestFramework" Version="2.2.8" /> <PackageReference Include="coverlet.collector" Version="3.1.2" /> </ItemGroup> <ItemGroup> <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="6.0.1" /> <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="6.0.0" /> <ProjectReference Include="..\PetStoreClientSDK\PetStoreClientSDK.csproj" /> <EmbeddedResource Include="..\Stacks\Dev\AwsSettings.json" /> </ItemGroup> </Project>
dotnet user-secrets -p PetStoreTests set "EmailAccount:Domain" "imap.mai.us-east-1.awsapps.com"
dotnet user-secrets -p PetStoreTests set "EmailAccount:Port" "993"
dotnet user-secrets -p PetStoreTests set "EmailAccount:UseSSL" "true"
dotnet user-secrets -p PetStoreTests set "EmailAccount:Email" "firstname.lastname@example.org"
dotnet user-secrets -p PetStoreTests set "EmailAccount:Password" "maypassword"
dotnet test PetStoreTests
In this step we created a Integration test project and ran our first tests against the published stack.
Reviewing the contents of the PetStoreIntegrationTest.cs class may yield valuable insights into how you should use the libraries in your client apps. Take note of the following implementation elements: