Corvus.Testing.AzureFunctions is published by two repository

[scrocquesel]

Hello,

I saw that this repository is publishing the same package Corvus.Testing.AzureFunctions as https://github.com/corvus-dotnet/Corvus.Testing. It triggered a security alert because the source link has changed. Is this officialy the new repository for this package ?

[HowardvanRooijen]

Hi! Sorry about that. Yes. We've been working on modernising many of our projects to:

1. Support .NET 8.0
2. Migrate from SpecFlow to Reqnroll
3. Migrate to our new open source build system - ZeroFailed
4. Update all dependencies

It's a major version change - and we're operating under the assumption that folks are following semantic versioning and wouldn't automatically update without understanding what the breaking changes were.

I've updated the readme on Corvus.Testing to explain the changes and point to the new packages, and I'll update the readme files in both:

• Corvus.Testing.AzureFunctions.ReqnRoll
• Corvus.Testing.ReqnRoll

We should also look at adding code signing for the packages to allay any fears.

Does that help explain the situation?

[scrocquesel]

Hi! Sorry about that. Yes. We've been working on modernising many of our projects to:

1. Support .NET 8.0
2. Migrate from SpecFlow to Reqnroll
3. Migrate to our new open source build system - ZeroFailed
4. Update all dependencies

It's a major version change - and we're operating under the assumption that folks are following semantic versioning and wouldn't automatically update without understanding what the breaking changes were.

I've updated the readme on Corvus.Testing to explain the changes and point to the new packages, and I'll update the readme files in both:

• Corvus.Testing.AzureFunctions.ReqnRoll
• Corvus.Testing.ReqnRoll

We should also look at adding code signing for the packages to allay any fears.

Does that help explain the situation?

Yes, thank you. It is encouraging to see that the project remains active and has undergone a significant enhancement.

[HowardvanRooijen]

Yes! Porting your specs to Reqnroll is a really simple process. Most type names are the same (one gotcha - TableRow is now DataTableRow) - you just need to update some namespaces & package names. specflow.json becomes reqnroll.json but has a new schema entry. Would recommend the effort.

Upgrading AzFunctions to .NET 8 was a little more tricky. I needed to create new projects & merge back the differences. 🤷

[scrocquesel]

Upgrading AzFunctions to .NET 8 was a little more tricky. I needed to create new projects & merge back the differences. 🤷

I really do understand the pain. Azure Functions is the worst framework I’ve ever worked with. .NET Aspire brings some support for it, although it's still in preview. It could be a nice alternative to start the function.