- Automatically put fuselibs on a Fuse branch and run tests. These must be allowed to be red probably. Might need to take a concious choice about which branch to base the auto-branch on, or just take develop
- Run fuse preview of a project that can report a fact about itself. Then make a change and make the project report that it changed
- Run the fuse daemon and ask for code completion
- Get UserDataService tests to run on TC
- Create CLI parse tests
- Compiler tests for preview on Android, iOS, DotNet
- Make automated serialization / deserialization tests
- Make unit tests for runtime
- Make unit tests for code generator
- Build examples on all platforms with
fuse preview --compile-only - TC to build example apps so example team only has test functionality (save time wating for build)
- Test that we work on Android 4.1 etc
- Automated tests on devices in the cloud, then we can probably reduce the manual test app quite a bit.
- Start running --no-strip compilation tests for Android repo
- Write testsuite for Experimental.Threading Promise/Future class
- Install more build agents to cope with all of this
- Use the opportunity to standardise the OS X agent setup a bit
- Windows agents depend on Stefan to expand/standardise, so we might have to wait a bit with that
- Should monitor release-branches