Details
Description
SAL v3.9 contains two new features
- RPM packagaing
- Combined interface modules
This task covers the effort required to update the tests for these new features.
There is also a desire to improve/increase the level of Java testing at the SAL layer. This task also covers some time to work on this.
Attachments
Activity
Additionally, there is now interest in running the PyTest unit tests as part of the build. This will add another story point, at least, to this effort.
The MTMount Java library generation fails, see DM-18229. This prevents the creation of the Java library, so the Lib and RPM steps fail. Figure out a way to not run those tests for the MTMount.
I was unable to get the HTML files onto https://project.lsst.org/ts/sal_objects/ due to restrictions on getting data off the AWS Jenkins servers. In principle, once we figure out how to get the data off the servers, the actual work is quite trivial. I just need to scp the files. I created a ticket to track the work to figure this out, DM-18484.
I did get the Unit Tests to run, see https://github.com/lsst-ts/robotframework_salgenerator/blob/master/SAL_Unit_Tests.robot for the test suite and https://ts-ci.lsst.codes/job/ts_sal/863/robot/report/jenkins_log.html#s1-s64 for an example of an execution.
I added DM Jira ticket tags to the MTMount failing test cases, so they still run, but are marked as non-critical.
Looked over the test results on Jenkins. The robot test framework appears to be executing russels SAL unit tests. They do show that they are failing, however Rob explains in the comments that this task was to get the test running and that getting them to pass is not part of this task.
Most of the work for this task is complete. The outstanding work is tracked by other Jira tickets.
As part of the build process, we should export the generated HTML to the current server location for public consumption of the interface definitions.