Best Practices Archive - Blog

Cos4Cloud Wrap Up

March 6, 2023 by Henning Bredel Leave a Comment

Filed Under: 52°North, Best Practices, Citizen Science, Communities Tagged With: agile methodology, Citizen Science, Co-design, Cos4Cloud, STA, STA plus

52°North presents work done on agile methodologies

The Cos4Cloud project partners met February 2 -3, 2023 in Barcelona to discuss the results and further cooperation in a last project meeting. Over the last three years, we have been working intensively on methodologies and services to improve citizen science platforms (citizen observatories), which will boost the quantity and quality of citizen science data and ensure their long-term viability. Learn more about the H202 project at the Cos4Cloud web site. 52°North presented a wrap-up of the agile methodologies developed and refined during the course of the project.

more >

SPARQL Endpoint and Interoperability of enviroCar Data

May 28, 2015 by Deepak Nair Leave a Comment

Filed Under: 52°North, Best Practices, Citizen Science, Communities, enviroCar, GSoC Tagged With: 52°North, envirocar, GSoC, java, linked data

Linked Open Data (LOD) is a set of best practices for publishing raw data on the Web. It makes your data highly structured and very easy to incorporate with the other datasets.

The enviroCar platform has a large and varied amount of data describing different entities and can currently be served as Linked Open Data with a detailed API reference here. There are many entities involved, such as cars, people, speed, dates and so on. If these entities are served as Linked Open Data, they can be very easily connected to datasets which describe them, such as DBpedia.

more >

End-to-End Client-Server Integration Testing with Maven – Project Setup

March 7, 2013 by Matthes Rieke Leave a Comment

Filed Under: Best Practices, Geoprocessing, Sensor Web Tagged With: best practice, integration testing, maven, service, web service

Preliminary Remark: This blog post targets Open Source developers and will basically cover technical details.

Automated Integration Testing for Java Web Services is an important pylon to ensure the stability of a web service and in particular its internal workflows. It is a very convenient way to ensure that the server is reacting just as expected in a set of pre-defined situations in terms of responses to specific requests. An easy way of defining integration tests is to provide a certain set of fully-defined requests (POST, GET, …) and corresponding responses. However, if you also are maintaining a client framework or library dedicated to that service, you are in the sweet situation of being able to kill two birds with one stone:

End-To-End Client-Server Integration Testing.

This is the first of two blog posts on End-To-End Integration Testing. For now, I am focussing on the Maven project setup. The follow-up will provide some insights on the actual implementation of integration tests – the client side.

In the following I will try to provide a guide on how to incorporate an integration testing component into your existing Maven-3-managed web service. I will use the 52°North Sensor Event Service (SES, server component) and the 52°North OX-Framework (OXF, client library) as a hook for the following sections. Knowledge of the following topics is helpful for understanding the article:

We will cover all needed steps to enable integration testing in your web service project. In particular, details on preparing a temporary webapp, reserving network ports dynamically, bootstrapping a servlet container and the actual execution of the integration tests will be illustrated.

more >