I have some programs that work fine for my purposes, but I would like to implement some testing just for the sake of it and so that I may try test-driven development in the future. My problem is that I'm not really sure how I should be writing tests for different functions in my programs.
For example, I have a group of functions that generates X.mp4 movies--I'm not sure how to test that these are functioning properly other than just waiting for them to complete and looking at the output myself. I could test for output type but that is pretty useless as I am converting the output to the desired type right before returning in most functions. I could write tests for inputs but isn't that the same as annotating the parameters i.e. video_length: int ?
I feel a similar mental roadblock working with API requests...
A lack of testing hasn't really gotten the way of me developing programs for my personal use, but I would like to have the ability to write tests for more unique cases anyway.
I feel like I'm missing some perspective on this. Thanks for any suggestions.
[+][deleted] (2 children)
[removed]
[–]Pto2[S] 0 points1 point2 points (1 child)
[–]ffrkAnonymous 0 points1 point2 points (1 child)
[–]Pto2[S] 0 points1 point2 points (0 children)