Test update, was: What happens with the lexical value space and the closure of dynamic functions?

> 
> It looks as if you are writing some interesting tests. I do hope you will get
> around to committing them. In many ways, committing the test would be
> more useful than raising the question by email, because we will automatically
> have a discussion about the question if it turns out that different
> implementations have interpreted the spec differently. I have to admit I am
> a little disappointed how few test cases we are seeing from other
> implementors, as they are always the most useful ones.
> 

Yes, I have been trying to commit a significant set of tests, but keep getting an error:

 abort: stream ended unexpectedly (got 8431946 bytes, expected 28428783)

The numbers are different each time. I'm afraid I broke my local repository or something. Not sure (yet) how to fix it, I will probably create a new repository and merge my changes back in.

I have been working the past couple of weeks to convert our F# tests. This is no easy task, as they use "quotations", which is a technology where in-line expressions are parsed in a certain way into expanded expressions, which in turn are processed to create a test set using NUnit dynamic test catalog loading methods. While this has proven very productive by using an extremely terse syntax to create many tests, I have been struggling for a very long time to convert these.

Eventually I settled by recreating the logic in parts in XSLT to semi-auto-generate a bunch of tests. A first attempt proves successful, and I want to apply it to other tests. However, I started out with a relative simple case and I need to expand this method on the more complex cases.

I have started this effort before, but had to give up a few times. I hope that now it goes better and that the tests we have had internally for quite a long time can become part of the test suite, as they should have a long time ago.

Cheers,
Abel

Received on Thursday, 1 October 2015 15:48:14 UTC