...
- Linux script test system runs are currently performed from a folder named "linuxBin" in the test/script folder to avoid conflicts with the test/script/bin folder. The scripts used to test on Linux should be merged into the bin folder to simplify repository updates. (This has been tested and has no conflicts, but it's too close to release to do it until R2018a is out the door.)
- Still lots of test config changes after QA complete, not running nav tests we should run etc.. need to formalize how we verify that test system configuration is nailed down by QA complete. what folders should be run, review profiles spreadsheet etc. We made a lot of changes two day before Code Freeze .
- We need to check the Mac builds on any more recent operating systems we can try it on EARLIER in the process, not at the very end of the release process.
Start Doing
- Scrub the system for deprecated features and remove at least low hanging fruit... both code and tests.
- Save
- LibCInterface
- TrackingSystem
- StatisticsAcceptFilter
- StatisticsRejectFilter
- Always build the system and run smoke tests before committing and pushing code. (This includes when merging code from a branch into another branch.) This is particularly critical near system freezes (QA Complete, Visual Freeze, and especially Code Freeze.)
- Check sample missions on all platforms
- Currently, running samples is assigned to one person. We should modify the release process to assign it to one person per platform.
- Seriously consider adding the bundling shell scripts to the daily build script so that we create zip/installer every day and test against those...
- Include all of the plugin components when running smoke tests and system tests. We are looking for side effects as well as failures in the component being worked, so we need to watch for those everywhere.
- Raise and resolve test case failures as early as possible. The recent issue with Ephem_GMAT_Code500_ACE_OpsPrototype_v13 was thought to be a config issue, but there were other signs of a problem that we neglected.
- Some pushes to the central repository will not compile. That makes it difficult to track down when a change occurred. It would be useful to include a note on the commit message stating that the code does not compile, and why.
...