Add in-memory BlockDevice implementation for automated tests

[ashishsinghbora]

Problem Statement

Many FlashCore storage components currently depend on a real storage device for testing.

This makes tests slower, harder to reproduce, and unsuitable for some CI environments.

Proposed Solution / Enhancement

Implement a MemoryBlockDevice that stores sectors in memory and follows the existing BlockDevice interface.

The implementation should support:

• Configurable sector size
• Configurable number of sectors
• Read operations
• Write operations
• Flush
• Bounds checking

Use this device for automated tests involving:

• MBR
• GPT
• FAT32
• Partition operations
• Read/write logic

Architectural Layer Impacted

Block Device Layer / Testing

Alternatives Considered

Using physical USB devices for these tests would make the tests unreliable and unsuitable for normal CI execution.

[vd63866]

Hi @ashishsinghbora,

I’d like to take ownership of this issue and implement the MemoryBlockDevice for FlashCore’s storage/testing layer.

The proposed scope matches the issue well: implementing the existing BlockDevice interface with configurable sector size and sector count, read/write operations, flush support, and strict bounds checking, then integrating it into the relevant MBR, GPT, FAT32, partition, and read/write tests.

I can also make sure the implementation remains CI-friendly, deterministic, and well covered with automated tests so that it can replace unnecessary physical-device dependencies in the test suite.

Could you please assign Issue #3 to me? I’d be happy to work on it and submit a focused PR with the implementation and tests.

Thanks!