The main format that this tool aims to support (BCH) have a bunch of different version that are not totally compatible with each other. I usually don't manually test each different version after a possibly breaking change because this is time consuming. Theres also other formats to take into account, and as new features are added, this becomes less and less feasible.
So, adding tests for different BCH and CGFX versions is desirable, and also tests to ensure that the conversion between those formats and the "common" formats like DAE, OBJ and SMD works properly too. The tests can live on a separate CLI project that run all tests in a batch and returns status for each tests, and also overall status (passed or failed). Ideally, we should also integrate those tests with the CI system, so every new commit go through the testing phase automatically.
The main format that this tool aims to support (BCH) have a bunch of different version that are not totally compatible with each other. I usually don't manually test each different version after a possibly breaking change because this is time consuming. Theres also other formats to take into account, and as new features are added, this becomes less and less feasible.
So, adding tests for different BCH and CGFX versions is desirable, and also tests to ensure that the conversion between those formats and the "common" formats like DAE, OBJ and SMD works properly too. The tests can live on a separate CLI project that run all tests in a batch and returns status for each tests, and also overall status (passed or failed). Ideally, we should also integrate those tests with the CI system, so every new commit go through the testing phase automatically.