Discuss testing strategy #41

Closed
opened 2026-02-06 19:13:24 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @BnMcG on GitHub (Dec 12, 2018).

It looks like there aren't any (at least, no open-source) test suites for the codebase, I think we should look at what to prioritise in terms of testing the existing codebase, and perhaps implement a policy that all future PRs require tests? At least the problem can be addressed going forwards, then.

With that in mind, it may be a good idea to decide on a testing library/toolset and then create test projects for each of the C# projects in the solution, so that it's easy for future contributors to add tests to their PRs.

I've personally had good experience with NUnit as a unit testing framework, Moq for mocking and Autofixture for resolving dependencies easily, but I'm happy to accept whatever is popular nowadays.

Originally created by @BnMcG on GitHub (Dec 12, 2018). It looks like there aren't any (at least, no open-source) test suites for the codebase, I think we should look at what to prioritise in terms of testing the existing codebase, and perhaps implement a policy that all future PRs require tests? At least the problem can be addressed going forwards, then. With that in mind, it may be a good idea to decide on a testing library/toolset and then create test projects for each of the C# projects in the solution, so that it's easy for future contributors to add tests to their PRs. I've personally had good experience with NUnit as a unit testing framework, Moq for mocking and Autofixture for resolving dependencies easily, but I'm happy to accept whatever is popular nowadays.
OVERLORD added the roadmap label 2026-02-06 19:13:24 +03:00
Author
Owner

@BnMcG commented on GitHub (Dec 12, 2018):

#59 - This seems like it could benefit from however the roadmap pans out, so linking it for visibility.

@BnMcG commented on GitHub (Dec 12, 2018): #59 - This seems like it could benefit from however the roadmap pans out, so linking it for visibility.
Author
Owner

@SpootDev commented on GitHub (Dec 12, 2018):

From the boo-boo's that get released with Emby........I've assumed there are no unit tests at all. hehhee

@SpootDev commented on GitHub (Dec 12, 2018): From the boo-boo's that get released with Emby........I've assumed there are no unit tests at all. hehhee
Author
Owner

@JustAMan commented on GitHub (Dec 12, 2018):

Yeah, the codebase looks like it's written in "release it and test by running on your users' machines" way.

I'm personally okay with whatever framework you choose, as I know none right now :D

@JustAMan commented on GitHub (Dec 12, 2018): Yeah, the codebase looks like it's written in "release it and test by running on your users' machines" way. I'm personally okay with whatever framework you choose, as I know none right now :D
Author
Owner

@anthonylavado commented on GitHub (Sep 17, 2019):

We'll be revisiting this in a new Roadmap document, currently in progress.

@anthonylavado commented on GitHub (Sep 17, 2019): We'll be revisiting this in a new Roadmap document, currently in progress.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#41