#357: Enable meaningful testing of t/native_pbc/*.t
------------------------------+---------------------------------------------
Reporter: doughera | Owner: rurban
Type: cage | Status: reopened
Priority: normal | Milestone:
Component: none | Version:
Severity: medium | Resolution:
Keywords: 64bit needreview | Lang:
Patch: applied | Platform:
------------------------------+---------------------------------------------
Comment(by rurban):
Allison, please provide arguments about the claim that these tests are not
stable or robust enough yet. They are young, but all known tests pass, and
some tests on unknown platforms are todo.
Your change did not changed it back to the previous skipped state,
header was always passing,
and the skip message says now "pending robust testing strategy, TT #357"
How should a robust test strategy look like?
Get 100% coverage first? Good. Lets skip all todo tests then for a major
release
(? => 0)
But disabling these tests will not lead to more robust tests, it will lead
to less coverage, less robust tests, with the same bugs in core.
I've added the previous state commented out, so that at least willing
parties
can help in adding test coverage.
Good that the release_manager guide was changed, because the wrong tool
broke the tests in 0.9.1 and it is not needed anyway.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/357#comment:16>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
