Integrating JUnit tests inside a PHPUnit+Selenium test suite

I’ve spent some time recently integrating the OSLC open source test suite (from the OSLC open source support project)into the FusionForge test suite.

FusionForge‘s test suite uses PHPUnit to drive Selenium (RC) “end user” like tests. Selenium is a tool that makes such tests possible by piloting an instance of FireFox browsing the Web interface of the forge, in a controlled environment.

The OSLC test suite consists in a series of JUnit tests, which is driven by Maven (initially started from inside Eclipse, then also from command-line after I found the nasty command line parameters and changes in the pom.xml file that were required ;).

The whole of the test suite may not pass for our implementation of OSLC-CM in FusionForge, so some tests fail, but I don’t bother too much as this is “normal”, and all we’re caring for at the moment is mainly non-regression. There seemed to be no way to exclude some of the tests from the suite for the moment, but fortunately, that doesn’t matter, since the way I have integrated both test suites happens to allow the verification of only success on some of the tests.

So, the way they are integrated is through execution of the JUnit suite during one of the test cases of the Selenium suite (using a system( ) PHP call), which generates an HTML report (using the Maven SureFire reports plugin), which can then be viewed in the Web pages of the tested forge, so that Selenium + PHPUnit assertions can verify the content of the test report.

This is a bit hackish, but all in all suites our needs so far. Next step is to see if it works in other people’s test environments, including the automated executions in Hudson.

My presentations at fOSSa 2010

I’ve delivered 2 presentations at fOSSa 2010 in Grenoble, about :

  • Bug tracking at large scale, reporting on some of our efforts in project HELIOS (see details here)
  • Summer of code-like programs for involvment of students in FLOSS projects, replacing Albert Cohen who couldn’t make it (see the slides here)

The conference wasn’t a big event, but gathered very interesting talks, so it was an enjoyable event. Looking forward for the next edition. And thanks to the organizers for the good time.

Quick report from OSLC meetup in Paris last week

Last week, as part of the COCLICO project‘s efforts to work on forges interoperability issues, we invited partners and contacts for a short meetup in Paris, with a special guest, Steve Speicher, lead of the OSLC-CM domain work-group.

Steve was in Paris to speak at the Open World Forum 2010 in the forges interoperability track. As time slots at OWF were quite short, we proposed to have this meetup a few days earlier to be able to have more detailed discussions and demos.

Steve has presented the following slides : OSLC Specifications for Interoperability and a screencast of AJAX interaction between an OSLC-CM server and a consumer.

On our side, we made a quick demo (a screencast actually) of our Mantis add-on for OSLC-CM.

We have discussed several technical aspects of OSLC, and also the community of actors working on the specifications. Regarding the french speaking community, there doesn’t seem to be an urgent need to have a specific structure setup so far, but we will nevertheless probably continue sharing content in french whenever we have some time.

I’ve been very glad to meet Steve, and hopefully, there are gonna be other times for new meetups. Why not a formal OSLC conference some day ?

In the meantime, feel free to tell us if you’d like to discuss OSLC and forges interoperability.

COCLICO project’s efforts towards better forges interoperability (long)

Abstract

I’ve given a talk in the recent Open Forges Think Tank track of Open World Forum, which was organized by Christian Rémy from Bull, also a partner in the COCLICO project (btw, thanks Christian, this was a great track, with several interesting presentations and a great panel).

I’ve had the privilege to speak on behalf of the whole COCLICO project, in the afternoon session which was focused on forges interoperability.

This article will somehow be a transcript of what I’ve said (or intended to say), with the accompanying slides available here.

In this quite long piece, I’ll first recap some of the context elements about the COCLICO project. Then I will describe the interoperability issues that I’ve tried and focused on in my presentation, including the issues of project lock-in in the forges. I’ve tried also to describe the current ideas we’ve elaborated in the project to address these issues of interoperability (including our plans for open standards elaboration for forges interoperability). I finally conclude with a proposal to join the PlanetForge community for all interested parties.

Unfortunately, not all of these ideas are currently yet properly documented on the COCLICO website, so I hope this article will serve as a useful reference for what COCLICO is doing, still being a subjective piece of my own views, not necessarily representing those of other COCLICO participants, nor a precise description of what we’ll manage to achieve in COCLICO or PlanetForge.

Continue reading “COCLICO project’s efforts towards better forges interoperability (long)”

My presentation about COCLICO and forges interoperability at OWF 2010

I’ve given a talk on Friday 1st of October at Open World Forum 2010 (OWF) in the (not necessary all so much) Open Forges Think Tank track on behalf of the COCLICO project and some of our (or mine) ideas on forges interoperability.

I’ll try and prepare a more detailed textual version of all these ideas (worth adding to the project deliverables maybe ?), but here’s already a link to the slides (attention: 5 Mb). Actually I’ve slightly modified them after my speech before posting them, as I added some more comments in last minute that may have deserved a bullet of their own. EDIT: I’ve finally posted a textual version of my ideas.

Here’s also a crappy preview online, as it seems slideshare doesn’t like the fonts used by this beamer presentation :

Coclico project – Forges Interoperability (OWF 2010)