On Tue Sep 16 06:50:26 2008, particle wrote: > > > parrot needs a way for us to measure spec coverage in our test suite. > i started the current smartlinks code as an experiment in using moose, > and as a reaction to the mess of smartlink code that's in the pugs > repo. however, i'm not married to the code, so rip it out if you > like--i never completed it, anyway. > >... > > i'd *love* to see smartlinks working in parrot. one of the big > problems in the parrot test suite is our lack of ability to measure > the test coverage of both code and spec. although smartlinks likely > won't offer us solid quantitative metrics, it will provide important > visual qualitative measures.
Okay, here's what I propose we do: 1. I will examine the 12 unresolved tickets to see if there are any which will not be automatically closable once my patch is applied. 2. I will apply a refined version of the patch. It will delete inline comments referring to the deleted tickets. But I will leave to others dealing with reference to smartlinks under languages/. 3. I will resolve/reject the unresolved tickets. 4. I will then open up a new RT of the [RFC] class. This ticket will call for development of a specification of a way to visually display the extent to which Parrot's tests cover the specification. I'll be quoting from particle's post -- but I'm sure there will be additional questions for Jerry. The spec will call for a way to test whatever code we develop to meet the spec. So, rather than asking people to rush out to write code, we'll focus first on determining what we want and need. Thank you very much. kid51
