Mark

Great to hear. I will start working on it probably next week (currently in the middle of some other work). It seems best for the repo to be created under...

I'll try to get back on it within a similar time frame. I'd like to get it to a working state as it's crude and completely untested right now.

Update: started working on unit tests. Not the most fun to write but it's getting there. Will open a draft PR once I've finished at least one batch of tests....

It exists here https://github.com/algorithm-visualizer/tracers.py but is not really functional yet. Progress has stalled. I had a PR open which hasn't been merged yet and I moved onto other things. Sorry...

> can you retry it with putting the JSON in the `content` field of the body? Not sure what you mean. Like this? ```json { "content: [ commands here... ]...

Regarding the helper function, there are two approaches I can think of, roughly: ```python def assertCommandEqual( self, method: str, *args: Union[Serializable, Undefined], key: Optional[str] = None ): cmd = Commander.commands[-1]...

I don't know what the best way to do this is. I am not really familiar with best practices and methodologies for testing. I do agree there should be some...

Yes, I think some practical usage tests would be good to have. I think we could get away with random inputs if we just seed the RNG.

Could use ideas for how to write a test for [`get_url`](https://github.com/algorithm-visualizer/tracers.py/pull/4/files#diff-4f511d35d0a07a5cd8fc1adab42b36d8R26). I can test for the return type easily but not sure what else.

I think I came up with something decent by mocking some things. I didn't want to test that it returns 200 because that's effectively testing the API, which is out...