Beta
Tic-Tac-Toe Winner
89chris_w
Loading description...
Logic
Strings
Puzzles
Games
Fundamentals
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
Needs random tests
Duplicate:
https://www.codewars.com/kata/search/?q=tic+tac+toe&beta=false
Testing for every outcome at least once in the standard test cases would be nice. One can write his own test cases, true, but it's better to have the obvious tests there from the beginning.
There are some warnings in the C# solution about unused member fields in the tests which are assigned but not used.
But only in the example testcases, so you easy can delete these unused "string messages" or you can add some own tests for these cases. Submit tests work, so kata is solvable;-)...
As smile67 said: It is only in the example tests. And for month this problem is solved by compiler-option.