Make the integration test not dependent on version

[jonasgeiler]

I was building supercronic locally and ran the integration tests and noticed this little annoyance. I don't think the integration test should check the exact version it expects, just whether the version is unset or not.

I am open for discussion, though.

P.S.: I just submitted the supercronic, supercronic-bin and supercronic-git packages to the AUR and will be maintaining them as long as I can.

[UserNotFound]

The test is seemingly important because it ensure a version number is actually returned. In what scenario for local testing does this cause an issue?

[jonasgeiler]

@UserNotFound wrote: The test is seemingly important because it ensure a version number is actually returned. In what scenario for local testing does this cause an issue?

While writing the AUR packages I wanted to verify that everything is working by running the integration tests after build. But I seemingly could not get it to pass this version test. I have also not seen a successful GitHub Actions workflow run for the test workflow in a while, so maybe the test is actually outdated?

Edit: I think I just figured out that the integration test is not supposed to be run on a release build, but only on a special test build, built with a VERSION=v1337 environment variable. I completely misunderstood your usage of this integration test. My bad.

Although I do think the integration test should be written to still pass, even when not hardcoding the version to v1337...