-
Notifications
You must be signed in to change notification settings - Fork 176
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
Implement unit testing. #74
Comments
Due to limitations in Visual Studio (even 2017), we aren't going to be able to run multi-targeted tests within Visual Studio in the Test Explorer ;( We'll have to drop to the CLI and run the The build script will already be doing this anyways so there is no problem there. It's more of a papercut for us devs. My impression is the Test Explorer was designed in mind for the masses which don't usually have multi-targeted projects to the extend we do, or will have once we add .NET Core support. c'est la vie |
My comment immediately above applies for any test framework including xUnit, NUnit, and MS Test. |
For right now I'm just going to focus on implementing the unit testing with just the .NET Framework in mind. I'll worry about unit testing everything when we eventually add .NET Core support into the mix. |
Sir, I am trying to set up the ExampleWebSite. It gave me this error message Can you help me? What is wrong in my web.config? Thanks. |
I think it would be beneficial to implement unit testing in general so that we can use it to validate code and intended behavior in certain places.
The first tests I'd like us to create would be to validate #53
The text was updated successfully, but these errors were encountered: