[Chore] Add Meter palette tests (Beginner & Advanced)

[vanshika2720]

This PR expands the Music Blocks test suite by adding structured tests for the Meter palette, covering both Beginner and Advanced blocks.

What’s included

Meter palette (Beginner)

New action block tests validating basic meter configuration:

• set meter with common time (4/4)
• set meter with triple meter (3/4)
• set meter with compound meter (6/8)
• Verification of beats per measure and note value per beat

These tests focus on core time-signature behavior without tempo changes or polymeter.

Meter palette (Advanced)

New action block tests covering advanced meter features:

• pickup to validate anacrusis handling
• tempo to verify BPM changes in meter context
• polymeter to confirm independent meters across voices

Each test isolates a single advanced concept to keep behavior explicit and easy to debug.

Organization

• Tests are organized into separate action blocks for Beginner and Advanced Meter palettes
• Action blocks are attached to the start block following the existing test suite pattern
• No pitch, ornament, or tone logic is included in this PR

Scope

This PR is limited to the Meter palette only. Other palettes (Pitch, Intervals, Tone, Ornament, Drum) will be addressed in separate PRs to keep changes reviewable.

Testing

All tests follow the structure of existing Music Blocks test suite examples and run within the current test framework.

• Tests

Closes

• [Chore] Music Blocks test suite project #5607

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[vanshika2720]

@walterbender

[walterbender]

Seems really broken. How did you test this?

[vanshika2720]

@walterbender yes,I tested the changes locally, but after reviewing again I found that something is not working correctly in the test suite. I’m currently fixing the issue and will push an updated commit once everything runs without errors.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[walterbender]

Sort of kind of the right idea. Your test for beats per minute works, as does your test for current meter. Not sure what the 3rd start block is for. But these tests should be in an action block, not individual start blocks. And the action block should be called from the original start block as per the others.

No idea what all the js code changes are for.

[vanshika2720]

@walterbender The third start block was originally added to isolate the initialization for the time signature listener, but I’m still working on this and refining the structure. I agree it doesn’t need to live separately, so I’ll move the BPM, meter, and related checks into a single action block and have it triggered from the primary start block, consistent with the existing pattern.

I’ll update the structure accordingly once that’s in place.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.