News for hackers. Stuff that matters.

A comment on Implications of Rewriting a Browser Component in Rust. Parent comment

Re:Implications of Rewriting a Browser Component in Rust by eridius on Thursday February 28, 2019 @05:32PM (#19275971)
What confuses me about this is the tests were turned off because they were taking too long. But wouldn't the appropriate behavior there be "run a subset of the tests normally, but run the full test suite occasionally" rather than just disabling the tests completely?
[ Parent | on HN ]
Re:Implications of Rewriting a Browser Component in Rust by dmix on Thursday February 28, 2019 @09:37PM (#19277501)
Or turn off some during development but run the whole suite before release?

I have a feeling the a bunch of the tests in that particular category needed to be updated, so it wasn't simply just too long.

[ Parent | on HN ]
Re:Implications of Rewriting a Browser Component in Rust by indolering on Friday March 08, 2019 @10:06AM (#19338088)
Pretty clear that the QA process is at fault here, which is sadly common in the software industry.
[ Parent | on HN ]