Hacker News Reader

- 0 open PRs

- 2 PRs merged, 1 PR closed in the past 4 years

- All PRs reviewed by a member of the Flutter team within 24hrs

- [“If I'm still supposed to write tests, even for this change, then this is probably as far as I take the PR.”](https://github.com/flutter/flutter/pull/128910#issuecomment-...)

- 40+ PRs from 2019

So, disgruntled ex-employee?

View on HN

I can understand the test frustration on both sides.

* He's being asked to fix tests that were already failing. That can be an enormous task depending on the nature of the failure and the code base.

* The team doesn't want to merge his PR since they don't have a test. The code is presumably working without his PR and understandably they won't change a single byte without seeing tests work.

If existing tests are failing then how are they accepting any PRs at all?

Reply on news.ycombinator.com