Custom Assertions for v6

[claudiospizzi]

Hi all

We currently use a bunch of custom assertions in v5 and would like to migrated them to v6 in the future, so that the old Should -Be is not used anymore. We checked the docs for v6, there is a section for custom assertions in v5 but not v6: Custom assertions (v5)

As the assertion library is the big change for v6, is there a documentation about creating custom assertions with the new Should-Be style? If yes, would be great to include that to the official Pester v6 docs. I think the core issue where we struggle is the knowledge, how we have to return successful and failed tests in self-created custom assertions.

Thank you.

[nohwnd]

At the moment there is no way to plug-into the new should style of assertions. I am not sure how to best expose that to users.

[claudiospizzi]

Maybe we start adding a note to the official docs, that this is currently not supported in v6 with the new assertions?

The workaround is always having a lot of Should-xxx assertions in a single test instead of our custom assertions. With the (new?) feature Should.ErrorAction = 'Continue' to show the result of all assertions in one run, I think we can reach a good result in our case. We will try.

[nohwnd]

Unless you are in a hurry to move to new assertions I would wait few weeks maybe I will get it through in 6.1

[nohwnd]

https://github.com/pester/Pester/pull/2848/changes are you able to consume the module from our code, or it is better to release 6.1.0-alpha1 so you can try? (alternatively I could setup a nuget feed for all our previews, but I am not sure about the limits on my signing of files per month and don't have access to billing right now).

[claudiospizzi]

@nohwnd Thank you for the rapid response, appreciate it! We are not in a hurry, if you could provide a 6.1.0-alpha1 as soon as it's ready, that would be great.

I just had a few minutes to check your pull request: If I understand it right, you've added a generic way go generate an assertion result and you also reused that in all built-in Should-*, so the custom are equally handled as the built-in? We'll use the provided examples as a starting point to try to implement our custom assertions.

[nohwnd]

You understanding is correct.

[nohwnd]

6.1.0-alpha1 should be out in 5 minutes