Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TEAM Engine code sprint at OSGeo Code Sprint in Bonn, Germany (2018-03-20) #322

dstenger opened this issue Mar 15, 2018 · 1 comment


Copy link

@dstenger dstenger commented Mar 15, 2018

Hi all,

We would like to invite you to a TEAM Engine code sprint at OSGeo Code Sprint in Bonn, Germany on 20th of March 2018.

Everyone interested in TEAM Engine (from user to developer) is invited to participate. This will be a great opportunity for you to get involved and improve TEAM Engine and to get to know this tool better.

We plan to work on a selection of following topics:

  • Improve testing strategies for TEAM Engine and/or test suites (#318).
  • Implement display of hierarchies in new HTML report of TEAM Engine (#319).
  • Introduction of teamengine-statistics project (opengeospatial/teamengine-statistics#11).

Also, you are welcome to bring in your own ideas.

The referenced issues can be used to have discussions about single topics prior to the code sprint.

Instructions about how to get there and how to register can be found here:

If you would like to participate, please write me an short email. By that, it is easier to find each other and to organize workplaces for everyone.
Of course, it is also possible to participate spontaneously. Just look for us in Basecamp then.

We are looking forward to improve TEAM Engine with you together!

Copy link

@lgoltz lgoltz commented Apr 11, 2018


We discussed the test strategies for test suites (described in #318 (comment)) and enhanced the existing tests for ETS WFS 2.0.

Furthermore we worked on issue #319 and enhanced the transformation from the CTL log to the EARL report by mapping undefined hierarchies. In addition some bugs was fixes in the transformation. See #319 (comment)

Some interesting conversations gave some new ideas for enhancements:

  • Signation of test results to make the validation result more official
  • Logging via SSH key to ensure that only authorized 'workers' can execute a validation.
    In general TEAM Engine could be interested for data provider who wants to validate the generated data before providing or using them. The step of validation is usually not done by a person in this case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants