Euphoria
Ticket #408:
Missing unit tests for tokenizer
-
Reported by
jimcbrown
Nov 18, 2010
We need to implement t_tokenizer.e to test unit tests against euphoria/tokenize.e
This is a complex library with a lot of functionality that needs to be tested for correctness.
Details
1. Comment by jeremy
Nov 22, 2010
I'll be adding more tests as eubeautify and eudoc work continues. Tests, however, have been added to ensure it at least it parses and works minimally thus I am removing the 4.0RC2 milestone requirement.
2. Comment by SDPringle
Nov 28, 2010
I think you ought to at least set this milestone to '4.0.0'.
3. Comment by jimcbrown
Nov 28, 2010
I agree with Shawn, and will add the 4.0.0 milestone.
Mostly, I can't think of a good reason not to have it. But if there is one, I'm open to removing the milestone altogether (or delaying to 4.1 or 5.0).
4. Comment by jeremy
Nov 28, 2010
I will not be able to complete this before 4.0, it's a complex library and will require a serious amount of unit testing. Therefore, knowing that I can't complete it in that amount of time, we have to decide 1 of 2 things.
- It remains as a future non-4.0 milestone
- Someone else does it
Therefore, at least for now, I am removing me as the assigned person.
5. Comment by jimcbrown
Nov 28, 2010
I don't think we have anyone who could solve the problem faster than Jeremy.
Unless someone else steps up, I'd say we move this to a 4.1.0 milestone and reassign the ticket back to Jeremy. (We can later bump this up to 4.2.0, 4.30, and so on if need be.)
6. Comment by DerekParnell
Nov 28, 2010
I'd change the milestone and the severity. The tokenizer is mostly working now for what we use it for and I don't think it will be a highly-used module. So not having a full test suite for it is not a major issue that needs to be resolved before 4.0 goes live, IMHO.
7. Comment by jeremy
Dec 02, 2010
Changed to milestone 4.1. We use tokenizer in eudoc and eubeautify (a personal project, not oe) and it seems to be working, thus reducing the severity.
Adding enough tests to this module is going to take some time to make this ticket "complete", so assigning to 4.1 milestone.
GitHub