#600: bytecode testing framework
---------------------+------------------------------------------------------
Reporter: allison | Owner:
Type: roadmap | Status: new
Priority: normal | Milestone: 1.7
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Comment(by dukeleto):
In light of this talk on #parrotsketch
{{{
<Util>: TT#600 (bytecode testing framework) - only progress is a vote
from dukeleto++
for running both .pir and .pbc versions of the testing as the default. I
need to
carry it into #parrot; among other issues, running both will more than
double our
current `make test` time
<allison> Util: aye, it's something that should be an option for fulltest,
but not part of the default tests
}}}
I think that if both version were run on fulltest, and only one on a
normal test run, that would be fine. An optional flag is also fine.
I would just like to note that getting 100% test coverage should always be
more important than making our test suite slower.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/600#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
