Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Reorganize tests to use Verify. #69

Merged
merged 2 commits into from
Jan 28, 2025
Merged

Conversation

ChristianSauer
Copy link
Collaborator

Drop FluentAssertions due to license change. Reorganize Tests.
I've also tried out TUnit and while I like it's basic syntax more it has some issues with Rider and Verify, so I kept that out for now

@simonmckenzie Could you give me your opinion?

@simonmckenzie
Copy link
Contributor

I'm not fussy. My first impression is that it's harder to see the "expected" output and the test input at the same time, which I'm habituated to, but as long as it has good test coverage, I'm pretty happy.

@simonmckenzie
Copy link
Contributor

Glad to see the test are broken out into separate classes - that's something I've thought about a few times too.

@simonmckenzie
Copy link
Contributor

I just did some reading about Verify - I see the beauty of it now. No more fiddly manual config of "expected output" - that is nice!

@ChristianSauer
Copy link
Collaborator Author

@simonmckenzie Yes, especially with the Plugins for your IDE, Verify has a really good workflow. Much better than doing it by hand

@ChristianSauer ChristianSauer merged commit 1afa5e3 into master Jan 28, 2025
3 checks passed
@ChristianSauer ChristianSauer deleted the verify_for_testing branch January 28, 2025 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants