From df8253dbf6cb09093018333f99dd9c19ba0ff02b Mon Sep 17 00:00:00 2001 From: Daniel Smith Date: Sat, 28 Nov 2020 21:24:40 -0500 Subject: Initial commit `Tokenizer` can _just barely_ parse a basic, well-formed move list. Initially, I wanted to provide the movetext as a `Stream` rather than a string, the idea being that it could be processed as it was being read from a file without having to read the entire file into memory first. I had difficulties with the stream being unreadable in `Tokenizer.ParseMoves()`, so I switched to a string in order to get the actual parsing logic down first. Because of the `yield return` strategy, the debug console output includes all of the expected halfmoves multiple times in various orders. After running a test, generally the full, in-order list seems to exist at the bottom of the output. --- DotnetPgn.Test/PieceParserTest.cs | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 DotnetPgn.Test/PieceParserTest.cs (limited to 'DotnetPgn.Test/PieceParserTest.cs') diff --git a/DotnetPgn.Test/PieceParserTest.cs b/DotnetPgn.Test/PieceParserTest.cs new file mode 100644 index 0000000..e8aacf6 --- /dev/null +++ b/DotnetPgn.Test/PieceParserTest.cs @@ -0,0 +1,17 @@ +using System.Linq; +using DotnetPgn.Models; +using Xunit; + +namespace DotnetPgn.Test +{ + public class PieceParserTest + { + [Theory] + [InlineData("K", Piece.King)] + [InlineData("Q", Piece.Queen)] + public void ParsePieceTest(string input, Piece expectedOutput) + { + Assert.Equal(expectedOutput, PieceParser.ParsePiece(input)); + } + } +} -- cgit v1.2.3