Open rogers492 opened 7 years ago
@rogers492 : Have any actions been taking on this? If no, perhaps we need to get ED involved to get this resolved?
@solson-nws : This refers to the original testing of OpenWIS v3, most of which was done manually. Check with @woollattd for what happened historically. I would also question whether we want to do this based on the tests done in the past (who is asking for it? Auditors?). Maybe we should just factor this in as a task for the next maintenance upgrade? I would discuss with Dom.
I produced a test report back in Oct 2016 which was passed to everyone on the TC. This report provided the results of testing OpenWIS v 3.14.5 against the Use Cases for the WIS 1.0 techspecs.
Dom:
Not sure I saved that. Can you repost again.
Thanks!
Steve
On Thu, Jun 14, 2018 at 8:41 AM, Dom Woollatt notifications@github.com wrote:
I produced a test report back in Oct 2016 which was passed to everyone on the TC. This report provided the results of testing OpenWIS v 3.14.5 against the Use Cases for the WIS 1.0 techspecs.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OpenWIS/openwis-documentation/issues/195#issuecomment-397279832, or mute the thread https://github.com/notifications/unsubscribe-auth/APAjUewXHLU-omeMebl7w7jIgy7gMTlkks5t8loEgaJpZM4MuLbQ .
no probs. just emailed you a copy
From an automated perspective, the work that Giorgos did on a unit test reporting plugin added to the Cloudbees installation. A description of how this was added to cloudbees can be found here: https://github.com/OpenWIS/openwis-deploy/wiki/OpenWIS-Cloudbees-Testing-Configuration
Suggest we fold this in as part of our ability to automate the creation of a test report. Thoughts from others?
@woollattd : Can you check to see if this plugin has been added to CI environment already?
Per Technical Committee of September 2018 (minutes here - http://openwis.github.io/openwis-documentation/minutes/2018-09-18-OpenWIS-Technical-Committee-2018-Sep.html) - @solson-nws to check with @6a6d74 on what the testing and audit requirements of WIS2 is (or is likley to be) to inform publication of test results.
Suggest revising this after we formalize and document the CI/CD process, establish the ability to perform builds, update documentation regarding releases. Then we can revisit this.
@SungsooDO @remy-gibault @wqu-bom @mvisa @kuldeep-sri @StephanSiemen : Thoughts?
Please track with #578
This needs to remain open. With the new CI/CD environment and tool chain, it's possible we can automate the process for gathering test report results and posting to openwis website.
@solson-nws and @benjaminsaclier - please add a target completion date to enable monitoring and tracking
Publish test results to demonstrate that OpenWIS is fully compliant with Tech Specs for WIS 1.0