adding ByteTrack unit tests

[rolson24]

Description

This PR adds unit tests for ByteTrack. They do not all pass because of a bug introduced in the last PR, but I have tested them
on the current release of supervision and they pass correctly. They also pass after making the 1 line bug fix.
I chose the test cases to be the ones that I have encountered to be edge cases so far, as well as adding edge cases that I can imagine being problematic.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

How has this change been tested, please provide a testcase or example of how you tested the change?

I tested this change, by first running these pytests on the 0.18.0 release version of supervision to ensure they all pass. I then used them to validate my other changes to ByteTrack to ensure the changes still function correctly. I also tested the current develop branch, and 1 test failed due to a small bug in how update_with_detections handles no valid tracked detections. (added here)

Any specific deployment considerations

Need to make sure they tests will autorun on PR.

Docs

• Docs updated? What were the changes:

[Itayflymingo]

n

[LinasKo]

Hi @rolson24 👋

We've been discussing internally on how to test composite tools such as the ByteTracker. In many respects it's a collection of functions that should rest on a thorough foundation of unit tests. On the other hand, it could be seen as more suited for integration tests.

I liked how your tests are implemented, but we'd prefer to lay a broader foundation for ByteTracker, covering many more cases, rather than adding a few fixtures and iterating later.

[SkalskiP]

Hi @rolson24! 👋🏻 Although we decided not to merge this PR, thank you very much for the time and effort you put into the development of supervision.