No not testers but programmers willing to write some unit tests.
a unit test is simply code that tests and verifies the correctness of other code (production code).
ex. does the GetPreferedAudioStreamIndex return the correct index value based on input params etc.
Having a bunch of solid unit tests both for the server and client parts will insure us a more stable product.
When modifying existing code that is unit tested gives us the benefit of knowing wether or not the modification broke the already existing unit tests.
Simply done by running all unit tests
If they fail, we either introduced a bug, or we need to adapt the existing unit tests to the new change.
install :
NUnit - Home TestDriven.Net > Home
A standalone assembly/project should be created (TvPluginTests)
Then we could start by adding a single class to the project called "TvHomeTest.cs"
Add a reference to the nunit binaries (nunit.framework.dll) in that TvPluginTests project.
Also add a reference to the tvplugin assembly.
In the "TvHomeTest" class add ; using NUnit.Framework;
Now we're set.
The "TvHomeTest" should test all relevant functions within the TvHome class in tvplugin.
We want to focus on the GetPreferedAudioStreamIndex function.
Lots of tutorials on google.
NUnit: A tutorial Selva [Ne0] Samuel
/gibman
Quote:
Originally Posted by disaster123  OK :-) So now we need testers? |