Testing? (E2E)

[wadabum]

Hi, is there any testing code for this / would you mind adding it to the repo?

Otherwise I may contribute some myself (but no promisses ;D)
If I do, it would likely just be some very rough bash-based 'end-to-end' exercising,
with some wrapping it in docker/vagrant(for windows) to "make sure it cant be accidentialed to rm -rf /*" or so...

[andrewmcwatters]

Yes! I have some internal test cases that weren't ready to push to main, but I will try and clean these up and release them.

[andrewmcwatters]

I'm going to also note here that my unit tests are just using unittest right now, but since we do perform filesystem operations, using Vagrant or Docker here for testing is a great idea. So we'll move forward with that!

[andrewmcwatters]

Hi @wadabum!

Thank you for mentioning testing. I've started my unit tests over from scratch and will slowly build up all of the subcommand and argument test cases over the next few days until all of the cases are saturated. Then we can all have confidence tinkering with it!

Since the command only has a few subcommands, I'll keep this open until the cases are all filled. I'm hoping it won't take very long to fill all of the test cases. Or, optionally, you can close this at any time.

[andrewmcwatters]

OK. The critical path has been implemented for now.

git fetch-file add <repository> <path> and git fetch-file pull are in the unit tests. These should never break. We'll add arguments as we go. This process actually uncovered some misbehaving temporary directory behavior, so thank you!

[wadabum]

nice! added a few micro-tweaks on that here #9

On the bigger picture, I dont even want to call it that, but I was thinking more in the "fuzzy" direction of testing
to see how badly it can break (or get broken by someone "holding it wrong") and what fallout that may do ;D