
Resolves https://github.com/flutter/flutter/issues/154628
<br>
As a contributor, I would expect resources related to testing to be located in the [/docs/contributing/testing](https://github.com/flutter/flutter/tree/master/docs/contributing/testing) directory. This PR adds a page to that directory geared toward helping new contributors.
<br>
I've noticed that in `team-framework` triage meetings, comments along the lines of "could you take a look at the failing checks?" are a regular occurrence.
I believe we could save quite a bit of effort by changing this:
> [**Understanding a LUCI build failure**](a5ca16ea94/docs/infra/Understanding-a-LUCI-build-failure.md
)
to this:
> [**Flutter wiki â How to fix failing checks**](https://github.com/nate-thegrate/flutter/blob/fix-checks-wiki-page/docs/contributing/testing/Fix-failing-checks.md)
This is an index of team-facing documentation for topics relating to Engineering Productivity (also known as EngProd, and including topics relating to our CI infrastructure, security, autorollers, etc).
- Autorollers
- Autosubmit bot
- Dashboards
- Flutter FirebaseLab Tests
- Flutter Infrastructure Foundation
- Flutter Installation Bundles
- Flutter Self Service Index
- Flutter Test Fonts
- Flutter's Build Infrastructure
- Flutter's repository architecture
- GitHub Action Workflows
- Infra Ticket Queue
- Labeling PRs
- New Android Version