Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 2
    "Obviously the tests I have a problem with are those that will need TokenSource filling with a large number of Tokens." could you explain why this is true ? Commented Jun 8, 2018 at 11:48
  • 1
    What's wrong with a bunch of [TestCase("...", ExpectedResult=AST(...)] (or equivalent reading input & output pairs from somewhere)? Commented Jun 8, 2018 at 12:00
  • @SteveChamaillard: Because my problem is an ability to write certain tests. The test I showed has been written, and serves as an example of the very basic interface. Commented Jun 8, 2018 at 12:26
  • @Caleth: Reading input pairs from somewhere is the problem, I think. I'm not sure. Most of the tests of that form I came up with repeated testing functionality that will need to be tested at a lower level. Commented Jun 8, 2018 at 12:26
  • 1
    The rigidity of TDD is not always an advantage, especially for a parser. Generally speaking, ordinary automated testing is used for language development, especially when the language is in flux. Commented Jun 8, 2018 at 22:32