thomhurst / bdtest Goto Github PK

[Test]
[ScenarioText("end to end testing scenario create and find")]
public async Task FindNonExistingAccountReturnsNotFound()
{
await When(() => AccountSteps.CreateAnAccount())
.Then(() => HttpAssertions.TheHttpStatusCodeIs(HttpStatusCode.OK))
.When(() => AccountSteps.FindAccount(12345)) // <- CANNOT RESOLVE SYMBOL WHEN
.Then(() => HttpAssertions.TheHttpStatusCodeIs(HttpStatusCode.NotFound))
.BDTestAsync();
}

We generate the lightweight single-page HTML report and publish to a build tab in Azure DevOps. This was a really useful feature and had the added benefit of being a single-page living document that we could share with Product Owners to discuss test coverage. The test report server is great, but being able to generate a report and publish it to the test summary page on the build pipeline is also a really handy feature. Please reinstate it.

I am unable to use BDTest within Signed test projects as BDTest assemblies are not strongly named.

The below exception is thrown upon test execution:

System.IO.FileLoadException : Could not load file or assembly 'BDTest, Version=2.3.27.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

Intiaiting code is a as simple as:

[Test]
public void TestPass()
{
    new BDTestBuilder()
        .When(() => DoNothing())
        .Then(() => DoNothing())
        .BDTest();
}

public void DoNothing()
{ 

}

Please note that not using the BDTestBuilder and inheriting from a base test class results in the test not running at all and no errors being produced

My test projects have to be strongly named as they require visibility of internal members of their production counterparts (the production counterparts are signed hence why the test project is signed)

https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming

https://learn.microsoft.com/en-us/dotnet/standard/assembly/sign-strong-name