You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current state of code contributions (AI), I'd like to suggest a hard rule that says that all PR's going forward should include screenshots (at a minimum) included in the PR, but ideally video evidence of changes working.
I'm not sure exactly how we want to handle non-ui related changes, but with a code base this size it's nearly impossible to reliably recreate local scenarios that could validate the changes presented in a change request.
Obviously reviews and manual testing when feasible would not go away, but the inclusion of some visual cue for what we're testing would be nice.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
With the current state of code contributions (AI), I'd like to suggest a hard rule that says that all PR's going forward should include screenshots (at a minimum) included in the PR, but ideally video evidence of changes working.
I'm not sure exactly how we want to handle non-ui related changes, but with a code base this size it's nearly impossible to reliably recreate local scenarios that could validate the changes presented in a change request.
Obviously reviews and manual testing when feasible would not go away, but the inclusion of some visual cue for what we're testing would be nice.
All reactions