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

CT: Add release branch testing to CT #203

Closed
zepumph opened this issue Jan 23, 2024 · 1 comment
Closed

CT: Add release branch testing to CT #203

zepumph opened this issue Jan 23, 2024 · 1 comment

Comments

@zepumph
Copy link
Member

zepumph commented Jan 23, 2024

From discussion with @jonathanolson related to phetsims/chipper#983 and #202.

We believe it would save a lot of time with maintenance if we had a tool on the server that could tell us the current status and errors with our release branches. Here is our first idea:

  • This would be a new tool, since it doesn't fit well into the idea of snapshots.
  • We want these tests:
    • ReleaseBranch.getStatus()
    • build/lint/tsc (noting here that lint could potentially because annoying to maintain, but let's start with it in.
    • Fuzz the built sim. This may lead to a lot of noise, but it would be good to see to start. At its best it could help us see when old releases break on modern browsers. At its worst it could just show us fuzz errors that we have already deemed unimportant and not blocking publication.
  • The server could have data that could integrate into the current CT report (kinda like CTQ does).

I'm not going to work on this right away, but I'm glad to have an idea, and to be able to crank away at it on the back burner.

@zepumph
Copy link
Member Author

zepumph commented May 14, 2024

Duplicate of #123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant