Title: Improving Testing Experience in neutralinojs-cli

[Resham0007]

Let's Discuss! Hey everyone, I hope you're doing well! I wanted to kick off a discussion here regarding the testing experience in neutralinojs-cli. Recently, we've noticed that when running npm test, a folder named testNeuCli is created. However, if a test fails, the folder persists, requiring manual deletion before running new tests. This can be inconvenient and lead to clutter over time. I believe we can enhance the testing experience by implementing a cleanup mechanism within the testing script. After running the tests, the script could check for any failures. If a test fails, it could log the detailed error message and then automatically delete the testNeuCli folder to ensure a clean slate for future tests. Additionally, we should consider the balance between convenience and debugging. While retaining the test folder may aid in bug identification, we could provide users with an option to manually or automatically clean up the folder after a certain period. I'd love to hear your thoughts on this issue and any ideas you have for improving the testing process in neutralinojs-cli. Please feel free to share your experiences, suggestions, and feedback. Let's work together to make the testing experience smoother and more efficient for all users! Looking forward to your input!
So I saw someone raising this question so I thought to give my thoughts on it and feel free to share your opinion on my discussion.