Open tomkralidis opened 7 years ago
Can we postpone this until I can (finally) finish the stuff from the RFC to move to pytest? I agree it would be nice to have CITE tests baked into our CI. I'd just like to finish this pending stuff first. I'll be tackling it from now too, so hopefully it won't take much longer
@ricardogsilva sounds good. Refs:
Issue: #428 RFC: http://pycsw.org/development/rfc/rfc-8.html
Should be renamed to point to GH Actions.
Note that there is discussion in OSGeo about creating shared infrastrucrture/services to provide CITE CI capability to a number of projects.
As a result, this will be an item of discussion/implementation at the forthcoming OSGeo OGC Committee, which pycsw will be able to leverage.
cc @jodygarnett @mbernasocchi @tfr42
This should be implemented using the approach put forth in https://github.com/OSGeo/ogc-cite-action cc @ricardogsilva
Description
Part of release packaging includes performing OGC CITE testing. Given pycsw is an OGC Reference Implementation, CITE testing is a critical piece of compliance.
The pycsw CITE testing task is currently manual and time consuming given we run CITE tests against CITE production and beta for both CSW 2.0.2 and 3.0.0. In addition, we usually run CITE tests for Python 2.7 (thereby skipping our other supported Python versions [2.6, 3.4]).
It would be valuable to run CITE testing as part of Travis to ensure we alway pass CITE across different CSW and Python versions.
Environment
Steps to Reproduce
NA
Additional Information