Add support for CI

[elpie89]

Adding features is becoming more and more complex, we should add some sample scene and implement a proper Test-Driven development pipeline

[Drigax]

I completely agree. I think we can quickly get some meaningful test coverage via an integration testing approach (Similar to our CI pipeline for Babylon.JS):

• [ ] Itemize functionality and create individual test cases (3dsMax & Maya scenes) for functionality

• [ ] Create harness for batch export of test scenes

• [ ] Create library of per-testcase validation images

• [ ] Create harness for loading export in trusted viewer and performing per-pixel comparison with validation image

• [ ] Create harness for invoking 2 & 4 per test case

Eventually:

• [ ] Setup the Exporters Azure Pipeline to invoke 5 as a CI gate

[deltakosh]

Up?

[deltakosh]

Removing 4.2 and flagging it as future

[Drigax]

I definitely think this should be a long-term goal of this project. via #969 we're starting to run into more concerns about regressing behavior, and without some regression testing solution, we'll never know if our changes are breaking some known behavior.