Project Description
Keeping a consolidated view of a project's progress is a non-trivial endeavor. There are far too many moving parts from its inception, such as planning, issue tracking, development, and testing. All the while one must keep track of some form of metrics to ensure that there's progress, and that the progress is happening in the right direction (or whatever is considered the right direction at the moment).
Traditionally we have enough tools to keep track of a project's progress in terms of planning, work planned, and work finished. Issue trackers are ubiquitous, and we're all used to using them and obtaining rough metrics out of them. However, just because work gets done doesn't mean the work being done is the right kind of work.
At its infancy, the s3gw project is going through a turmoil of development: we know where we want to go, we have a good idea how we'll get there, but we know a lot of things are going to be broken while we're on the road to get there.
While issue trackers help us keep track of work being done, these are not the right tools to keep track of how much of an API has been covered, for instance, or what kind of performance we can get out of the software at any given point in time. Even though one can keep track of these things in the form of issues, establishing baselines for different metrics and comparing against them then becomes a laborious, mind-numbing manual task that often has to involve spreadsheets.
Instead, we are proposing a dedicated web-based tracker, focused on running coverage and performance tests against the project at several points in time, keeping a history of results against known baselines, that we can then rely on when making decisions going forward and to evaluate where we are and how far we've come.
Goal for this Hackweek
The scope of this project is a bit far too broad for a one week development cycle. Being reasonable in goal setting, by the end of this hackweek we intend to have basic testing functionality and result reporting via a web interface.
Resources
Project's repository: github
Demo: TBA
This project is part of:
Hack Week 21
Activity
Comments
Be the first to comment!
Similar Projects
Uyuni: add SLE-Micro acceptance tests by mbussolotto
Project Description
Uyuni: add SLE-Micro ...
OpenQA test list views improvement by mdati
Project Description
Create views of **Ope...
Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil
Join the Gitter channel! [https://gitter.im/uy...
Uyuni test suite improvements by dgedon
Project Description
Uyuni is the upstream...
How software creation process can save energy and CO2 emissions by acervesato
[comment]: # (Please use the project descriptio...
Build alternative spotify frontend and learn modern frontend dev on the way by mlauhoff
[comment]: # (Please use the project descriptio...
One of couple of Python projects (update M2Crypto) by mcepl
There are couple of projects I work on, which n...
OSSelot collaboration on legal reviews of community packages by lkocman
[comment]: # (Please use the project descriptio...
zypper plugin for discovering reverse dependencies by bzoltan1
Often when we test maintenance updates or when ...
Linux Immersive Learning System (LILS) by dgarcia
[comment]: # (Please use the project descriptio...
Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil
Join the Gitter channel! [https://gitter.im/uy...