Allow local testing

[matthewhughes934]

• Move integration testing to run locally

  And not in Docker. This patch is to prove things work, so I've just
  moved one test across (though most of the changes are in test setup that
  can be re-used across tests). If this gets tractions, more tests could
  be moved across. Reasons for this approach:

  • Simplicity: tests have no external requirements besides git
  • Debugability: running locally you can spin up a debugger (or just
    sleep in tests) and inspect the running environment. This is possible
    with Docker, but more of a hassle
  • Reproducibility: tests are decoupled from the user's environment, so
    failures should be reproducible

  This is achieved via:

  • Using git's worktree's[1] to run things like git commit without
    modifying the working repo
  • Having the tests build a strongbox binary that we can then configure
    git with (built once per run)
  • Adding some test setup with actual keys etc. rather than relying on the
    user having keys define

  For posterity, the commands to setup the keys etc

    go run . -identity-file ./testdata/.strongbox_identity -gen-identity test-key
    grep --only-matching --perl-regexp '(?<=# public key: ).*' ./testdata/.strongbox_identity > ./testdata/.strongbox_recipient
  

  Link: https://git-scm.com/docs/git-worktree [1]

• Add run of local tests in GitHub

[george-angel]

This is really awesome - love it. If you are happy to move all tests, will merge 👍

[asiyani]

yes, this is good. I think we should also use TestMain to set defaults, so that we do not override users config while running this or any future tests.
We could also create temp home and set GIT_CONFIG_GLOBAL and STRONGBOX_HOME to that in TestMain?

[matthewhughes934]

yes, this is good. I think we should also use TestMain to set defaults, so that we do not override users config while running this or any future tests.

Could you elaborate on this? For clarity: At the moment all the config setup is handled by the configureGit function, which touches the user's local (i.e. in this repo) config just to set extensions.worktreeConfig, then all other configuration updates are limited to the worktree created by the test (i.e. all in a temporary directory).

We could also create temp home and set GIT_CONFIG_GLOBAL and STRONGBOX_HOME to that in TestMain?

Is the a reason for preferring this over the current approach? Currently the files used by STRONGBOX are static and just stored under testdata

[asiyani]

current approach is individual test will do its own initialisation and config. where as I was suggesting to share some of it between tests using temp home and TestMain.
I am not opposing current approach so if you guys think this is better then its fine by me.

[george-angel]

Matt can correct me - but I think this is the case because PR is a POC and we'd move this logic to main in full PR.

[matthewhughes934]

current approach is individual test will do its own initialisation and config. where as I was suggesting to share some of it between tests using temp home and TestMain. I am not opposing current approach so if you guys think this is better then its fine by me.

👍 I moved the config to be a file under testdata (saves having to configure worktree stuff locally) 3087ce9

[matthewhughes934]

This is really awesome - love it. If you are happy to move all tests, will merge

do you want all tests in one PR, or happy to merge this as a starting point and then I can move some more tests on top of this?

[george-angel]

I would be happy to merge this and have another PR to move the other tests 👍

[george-angel]

👏