Test command line usage

[nirs]

We need to test that using invalid options we fail with expected error code, and do not crash.

Example bugs caused by not having such tests:

• Changed error code with v1.2.0  #99
• client segfault with crafted arguments #73

This will also test options validation (e.g. failing for missing option or invalid values).

The tests are trivial and do not require any resources, so they can run on standard runners.

[saurabhraghuvanshii]

hi sir, I want to work on this but I need more explanation on it. to meet it in perfect way

[nirs]

Hey @saurabhraghuvanshii this is the way to work on this:

1. Reproduce the issue manually based on the report
2. Simplify the command to the minimal version reproducing the issue (using brew prefix is not nedeed)
3. Add a test running the failing command and failing if the command does not exit with exit code 1.

This test will fail with current code. The next step is to fix the code so the test does not fail.

[saurabhraghuvanshii]

Hi @nirs , I am able to produce this because It needed macos and I am using wsl2

socket_vmnet: macOS is required for this software.
Error: socket_vmnet: An unsatisfied requirement failed this build.

is there is way to test .

and on running these it show nothing

saurabh@MSI:~/open-source-web/socket_vmnet$ >/dev/null 2>&1
saurabh@MSI:~/open-source-web/socket_vmnet$ >/dev/null

[nirs]

It is possible but more challenging to fix this without macOS. Maybe it is better to find another task.

[saurabhraghuvanshii]

Ya , I see sorry about that sir