Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs on how to access and use the test status database #56063

Open
jakemac53 opened this issue Jun 20, 2024 · 6 comments
Open

Docs on how to access and use the test status database #56063

jakemac53 opened this issue Jun 20, 2024 · 6 comments
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). type-documentation A request to add or improve documentation

Comments

@jakemac53
Copy link
Contributor

The testing docs mention the results database, but don't link to it or give any instructions for how to access it, understand current test status, etc. I cannot find any other docs on it either.

I was assigned #56002 but I have no idea how to actually go about addressing that. For example, how can I find a recent failure, or know what the current status is?

In general, these issues should have some documentation they can point to, for how to diagnose a test that is failing etc.

Presumably also this would be a good place to put documentation on how to list all the currently failing tests for a project, etc?

@jakemac53 jakemac53 added type-documentation A request to add or improve documentation area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). labels Jun 20, 2024
@athomas
Copy link
Member

athomas commented Jun 21, 2024

The documentation there is right now is go/dart-status-file-free-workflow which links to go/dart-test-approval which links to the results feed UI.

@jakemac53
Copy link
Contributor Author

jakemac53 commented Jun 21, 2024

Can we link to these from the external docs, and/or transcribe them into the external docs/ directory? I don't see how somebody is intended to discover these?

@jakemac53
Copy link
Contributor Author

Ah, fwiw https://dart-current-results.web.app/ seems to be the most useful, to me at least. I found I can pretty easily search for a test based on path and see the status, as well as logs for recent failures. I will for now at least add a link to that to the docs.

I don't understand how the test filters on https://dart-ci.firebaseapp.com/ work at all, I can't get anything I want to show up.

I do think a distilled version of go/dart-status-file-free-workflow is really what we need here.

copybara-service bot pushed a commit that referenced this issue Jun 24, 2024
Bug: #56063
Change-Id: I1b6c70273d97e9d87a6f81e8f52e7c379c302448
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/372740
Reviewed-by: Alexander Thomas <[email protected]>
Commit-Queue: Jake Macdonald <[email protected]>
@athomas
Copy link
Member

athomas commented Jun 26, 2024

I don't understand how the test filters on https://dart-ci.firebaseapp.com/ work at all, I can't get anything I want to show up.

Example of a search with results (the problem is likely that you tried a prefix search and got no results because it doesn't do those, unlike the more modern current results app):
https://dart-ci.web.app/#showLatestFailures=false&test=pkg/analysis_server/test/integration/edit/get_postfix_completion_test&configurations=analyzer-unittest-asserts-release-win

The results feed AngularDart app should be rewritten in Flutter and offer a consistent UX with current results Flutter app (sharing most UI, but also improving search). Not sure if that will ever happen, though.

@jakemac53
Copy link
Contributor Author

Example of a search with results (the problem is likely that you tried a prefix search and got no results because it doesn't do those, unlike the more modern current results feed app):

Hmm, I also did try putting in the full name (or what I thought was the full name, maybe it was wrong, idk).

@jakemac53
Copy link
Contributor Author

It would be great if some of these internal Google docs could be migrated to public markdown docs at some point also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). type-documentation A request to add or improve documentation
Projects
None yet
Development

No branches or pull requests

2 participants