-
Notifications
You must be signed in to change notification settings - Fork 600
-
Notifications
You must be signed in to change notification settings - Fork 600
Remove usage of shouldly #420
Comments
And Shouldly doesn't run on DNXCore, either. |
If it's ok with everyone, I think that I might be able to tackle this. I'm looking for ways to contribute and this one seems low-risk. |
@jmloeffler go for it. Removing Shoudly is mostly a matter of writing clever regex's in VS search & replace to convert to a regular xUnit assert. Here's an example where I've previously done it: aspnet/StaticFiles@9c5e78b That should show the general pattern of conversions. |
Yep, that was my plan. Thanks for the cheat sheet @Eilon! |
And BTW most important is changing the project.json to of course remove Shouldly, but more importantly, to add |
@Eilon It appears that Moq is also a blocker for targeting |
FYI - in case we have to do this again somewhere, the following regex replacements in VS2015 converted most (but not all) of the statements for me. I'll submit a PR with the changes after I spend some time looking into the Moq thing.
|
No Moq on CoreCLR yet. If the usage of Moq is trivial, you could just remove it. If it's more involved, just leave it and don't enabled CoreCLR. We're working on Moq for CoreCLR so once that's available we can enable |
We should just be using xunit
The text was updated successfully, but these errors were encountered: