Add end-to-end tests for CLI commands

[antoineco]

Feature request summary

There is a lot to be done in terms of testing. For a start, we could focus on high level "e2e" tests and execute each command of the CLI tool against a sample unikernel project.

We could start with one project + one test case per command, then expand as we see fit.

This doesn't provide a feedback loop as quick as unit tests, but would already allow us to catch major regressions in the CI.

E2E tests

Beta Give feedback

1. Test kraft pkg #811
   priority/low +1
   
2. Test kraft build #810
   priority/low +1
3. Test kraft pkg pull #809
   priority/low +1
   
4. Test kraft pkg ls #808
   priority/low +1
   
5. test(e2e): add initial CLI tests #392
   area/test kind/test +2
   
6. test(e2e): add CLI test for pkg update #405
   area/test kind/enhancement +2
   
7. Test kraft pkg source #812
   +0
   
8. Test kraft pkg unsource #813
   +0
   
9. Test kraft net for macOS #840
   priority/none +1

[antoineco]

I think our next focus should be on kraft build.

It would be very nice to have an initial test that just

• initializes a temporary project from a few fixture files (helloworld.c might even be enough?)
• writes a kraft.yaml in that project
• pulls the dependencies
• builds a few targets

That would cover several subsystems at once. An ideal case for an e2e test.