Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Distributed testing framework based on ECF RFC 119 D-OSGi
Project Lead: Markus Alexander Kuppe (IRC: lemmy)
Mentor: Scott Lewis
This project is part of the Google Summer of Code 2009
Contents
Abstract
The goal of this project is to plan, design and setup a distributed testing framework for ECF. Furthermore it is about implementing (additional) tests as well as completing the current incarnation of ECF's version [2] of distributed OSGI (RFC 119) [3] specified in R4.2 by the OSGi Enterprise Expect group due this summer [3].
On top of that I intent to identify requirements and architectural design possibilites to extent well known testing tools like JUnit to better support distribution scenarios. The second part will later be used in my M.Sc. studies at University of Hamburg at the "Distributed Systems and Information Systems" department [4].
[1] https://ecf2.osuosl.org/hudson/
[2] https://bugs.eclipse.org/249240
[3] http://www.osgi.org/download/osgi-4.2-early-draft.pdf
[4] http://vsis-www.informatik.uni-hamburg.de/
Ping me on IRC or Jabber for details, question, comments or criticism. :-)
Timeline
Here is a complete list of the milestones and release candidates planned for this plugin.
Milestone | Date | Planned items |
---|---|---|
M1 | Week 1-3 | Research, Requirements gathering |
M2 | Week 4-6 | Complete missing ECF build parts and move to git, Setup distributed scheduler (Hudson), Configure machines and network (VPN...) at OSU to support discovery mechanisms |
M3 | Week 7-9 | Add missing distribution and discovery tests, Fix bugs that arise from better test coverage :-) |
M4 | Week 10-12 | Documentation, General requirements and design specifications, Lessons learned |
Community Involvement
Getting the source
The code will be available from the regular ECF repo at dev.eclipse.org
Open issues
TBD
New ideas
Do you have a great idea for this project? Just open a new feature request.