Skip to content

Conversation

@johnnesky
Copy link
Contributor

@johnnesky johnnesky commented May 10, 2025

Many test methods had been disabled. In fact, only one of them was actually running (because it called suite.only()). I re-enabled most of the tests, adapted them to the current behavior, and temporarily reverted one line in test_setup.ts to callgetCursor()?.setCurNode(field) instead of field.getFocusableElement()?.focus() because the latter doesn't work yet and I figure it would be more useful for the tests to be functional and enabled.

EDIT: Whoops, it looks like existing code in this repo was broken by RaspberryPiFoundation/blockly#9016 so github's automated test run fails for reasons that aren't related to my changes.

@johnnesky johnnesky requested a review from a team as a code owner May 10, 2025 03:42
@johnnesky johnnesky requested review from maribethb and removed request for a team May 10, 2025 03:42
testSetup,
} from './test_setup.js';

suite.only('Insert test', function () {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops!

Would need a separate run step for CI vs local to sanity check this but might be worth it.

mochajs/mocha#5299

@RoboErikG
Copy link
Contributor

#512 should fix the build errors you're seeing.

@RoboErikG RoboErikG merged commit c9d8689 into RaspberryPiFoundation:main May 12, 2025
10 of 11 checks passed
@johnnesky johnnesky deleted the nesky_fix_field_tests branch May 13, 2025 23:05
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

Successfully merging this pull request may close these issues.

3 participants