#464 Need for some way to test the oxygen-tei package before release

[Martin Holmes]

Since the new plugin update system in Oxygen means that people are likely to update their TEI frameworks in Oxygen quite rapidly, it would be very useful to have a small test suite that somehow checks that the latest integration of a P5 release and a Stylesheets release actually works OK before unleashing it on the world. I don't know exactly what we would test or how yet, though...

[Martin Holmes]

• Description has changed:

Diff:

--- old
+++ new
@@ -0,0 +1 @@
+Since the new plugin update system in Oxygen means that people are likely to update their TEI frameworks in Oxygen quite rapidly, it would be very useful to have a small test suite that somehow checks that the latest integration of a P5 release and a Stylesheets release actually works OK before unleashing it on the world. I don't know exactly what we would test or how yet, though...

[James Cummings]

Putting Martin as owner for now. Seems relatively uncontroversial but changing to RED since we need at least some guess at how to do this. (As a side note we need to document the oxygen-tei auto-update and how to set it up more clearly.)

[Syd Bauman]

Two suggestion arose during discussion at Council meeting:
1) make backing out the framework that is auto-updated a very easy process
2) have a beta version available where we put the framework a week before real release, so we can test it ourselves. (Just suggesting that we test it basically work, not test every feature.)

[Martin Holmes]

Setting this to amber now that https://sourceforge.net/p/tei/feature-requests/526/ is complete. We still need to discuss what form the tests should take; I imagine an Oxygen project file with a bunch of ant tasks which create files from templates, do transformations, validate etc., which people could run manually, but we could probably also create some automated tests which run as part of the Jenkins job.