Divyanshu gautam

@Cioppolo14 Please assign me this issue

@palisadoes @varshith257 If these tests share dependencies or resources, running them concurrently could lead to race conditions, flakiness, or incorrect results due to interference. Instead, it might be more beneficial...

@palisadoes I think we should focus on fine-tuning pool options. ,  Currently we use     `"test": "vitest run --pool forks --poolOptions.forks.singleFork --coverage",`,  I tried using other options, but some test cases...


@palisadoes and resources for this are very limited, nothing clearing explains, it depends on different codebases.

@varshith257 What do you think?

@AdityaRaimec22 Fix the linting errors

I will create a PR after completing items.

@palisadoes @Cioppolo14 please assign me this issue

working on this issue