Feature Request: Threaded Support for Fossil Test

[dreamer-coding]

Is your feature request related to a problem? Please describe.
Fossil Test lacks proper support for testing multithreaded code. This makes it difficult to validate the behavior of concurrent applications, particularly for issues like race conditions, deadlocks, or thread safety. I’m often frustrated when I have to write manual scripts or use external tools to test multithreaded logic, which can lead to inconsistent or incomplete coverage.

Describe the solution you’d like
I would like Fossil Test to include built-in support for testing threaded code, providing features such as:
• Automatic detection and reporting of common threading issues like deadlocks, livelocks, and race conditions.
• Tools to simulate thread scheduling randomness for stress testing.
• Synchronization primitives (e.g., mock semaphores, locks) that can be tested under different scenarios.
• Hooks for testing thread lifecycle events, including creation, execution, and termination.
• Support for defining and running tests in parallel to evaluate performance and concurrency.

Describe alternatives you’ve considered
• Using external debugging tools like Valgrind or thread sanitizers, but these can be cumbersome to integrate and are not tailored for Fossil Test.
• Writing custom thread-related tests, which is labor-intensive and often doesn’t cover edge cases effectively.

Additional context
Threaded support in Fossil Test would allow developers to confidently test complex multithreaded applications. This feature could also include debugging tools like stack traces for thread crashes and logs for synchronization events, making it easier to identify and resolve threading issues.