-
Autotesting is the key in open-sourced project, people can not worry about if their pull request will break the app or not. They will already know the answer.
-
A couple of automated functional tests can be added for the existing markdown inputs in the tests/ directory.
-
Introduce an abstraction for getting time (instead of using System.currentTimeMillis()) directly in RTTV.
Build on top of this to add automated tests, especially around scheduling the UpdateTimeTas…
-
The basic structure is there, but we need more tests.
* [x] Materials
* [x] Motion blur
* [ ] Lights
* [ ] World
* [ ] Textures
* [ ] Objects
* [ ] Linked objects
* [ ] Particles
* [ ] Duplis…
-
The project needs a test suite of some kind that builds all of the possible flavors of this project.
-
Recent commits broke the integration tests on master (handling the fix off list). In order to make those tests a little more useful, would it be possible for buildbot to run them on a regular interval…
-
Add links for common speed tests. (google pagespeed API?)
-
-
Create automated tests for both root-based and non-root-based deployments (see Pull #15).
-
Investigate https://github.com/charmbracelet/vhs for this: https://www.youtube.com/watch?v=dtVezRX8OEM