Comprehensive Unit Tests for Pitch & Tone Block Components

[PriyamvadaShah]

This adds comprehensive Jest test coverage for the Pitch and Tone block components, focusing on proper initialization, error handling, and integration behavior. The tests verify both individual block functionality and interactions between related blocks, ensuring that musical operations (key signature, scale, transposition, oscillators, and audio effects) work correctly.

PitchBlocks Tests:

• Key block validation with both valid and invalid musical keys
• Scale block functionality with different scale types
• Transposition block with semitone range verification
• Integration tests between key, scale, and transposition blocks
• Error handling for edge cases (null inputs, invalid signatures)
• State isolation between multiple turtles

ToneBlocks Tests:

• Oscillator configuration with various waveform types and partials
• Audio effect blocks
• Synthesis blocks
• Harmonic and partial handling for complex timbre creation
• Parameter validation and proper error messaging

Designed these in order to test that the PitchBlocks and ToneBlocks work as intended and cover all edge cases.

Kindly review this PR and suggest any changes, if required :)

[github-actions]

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

[walterbender]

Please add a license (see the other test files) to these files.

[github-actions]

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

[github-actions]

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

[omsuneri]

@walterbender this PR is not following our guide to add tests instead of mocking variables and function in the test itself it is creating an another mock.js file which is strictly prohibited as we get into trouble as someone did this in the synthutils i think @PriyamvadaShah you need to refactor your test looking at our adding test guide in js directory

[omsuneri]

@PriyamvadaShah also you are not following the actual nomenclature for the test file we are doing in MB again you are not supposed to edit the .json file please do follow the guide and refactor all the changes suggested according to that

[PriyamvadaShah]

@omsuneri Thank you so much for pointing these out. Will make changes to make sure I adhere to the guidelines!

[omsuneri]

@PriyamvadaShah also please mock the fun in the test itself only don't create another mock.js as it becomes very hard for debugging the failure of any test in future