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

Create Guides for Authoring & Testing in C# #339

Open
awesomeAD1 opened this issue Jul 26, 2021 · 0 comments
Open

Create Guides for Authoring & Testing in C# #339

awesomeAD1 opened this issue Jul 26, 2021 · 0 comments

Comments

@awesomeAD1
Copy link
Contributor

Note: I'm raising this issue specifically about C# to keep with established convention, however it really relates to most languages apart from Python and Javascript

The current language page for C# is notably lacking in any sort of guidance for users attempting to author or translate kata in C#.

Coming from the Python Authoring Guide particularly shows a stark contrast in content.
While that level of details is probably unrealistic, it would be great if someone with expertise/competence in C# and NUnit could compose a short article about the best practice methodology, e.g.

  • Organizing Solution, Preloaded and Tests by Namespace
  • Best practice for Class setup
  • Do's and Don'ts of method signatures, input & return types
  • Basic NUnit usage
  • Test organization (TestFixture, Test, and TestCase attributes)
  • Best practice for Random Test generation
  • Usage of Constraint Model vs Classical Model
  • How to compare actual and expected value (types) efficiently

In the meantime, it would be helpful if the current documentation page could at least specify the actual version of NUnit used (I believe there are differences between features that otherwise require guesswork to see if they are available on CW), and possibly a link to the official NUnit documentation

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

No branches or pull requests

1 participant