secure-electron-template VS testfixtures

That's a common refrain I hear that Electron apps aren't secure. It was more true in the past and less-so now. I've been maintaining a secure Electron template for 2 years that's got traction in the community, if you are interested - https://github.com/reZach/secure-electron-template.

You'd specify the valid IPC channels in preload.js, and as long as you don't create a "getSuperSecretInfo" channel that responds with sensitive data, a malicious script in the renderer process won't have access to said data. This writeup may answer some of your questions: https://github.com/reZach/secure-electron-template/blob/master/docs/secureapps.md

Started from secure-electron-template

I'm the author of https://github.com/go-testfixtures/testfixtures, a library written to make it easier to write tests with a real database and test data. You might want to use it together with docker-compose, for example.

To solve the problem we will use testfixtures. Create a folders fixtures и fixtures/storage and put a file users.yaml inside:

A lot of good suggestions here, I would also take a look at go-testfixtures which allows you to create some simple yaml-based fixture data to use with unit testing. It's quick and easy, but yes can get unwieldy the more you add.

I built an alternative to Make written in Go that is simpler to use and cross-platform: https://taskfile.dev/

Also, a library to write tests with databases for Go: https://github.com/go-testfixtures/testfixtures