Piston Test Coverage
Jorge Cardona
I added a test environment with tox to piston, in which we can test it
in python 2.6 and 2.7 with django1.2 and 1.3. I'm using the already
used application for tests, and it has 64% coverage of piston, I'm
planning to up that number myself in the near future, but if someone
want to do it please fork and create a pull request. Right now there
is one test that has an error, one with a failure, and one that fails
in 2.7.
All this is in the branch test_with_tox of
https://github.com/django-piston/django-piston
(https://github.com/django-piston/django-piston/tree/test_with_tox)
After have a good coverage of piston we need to merge some repos that
has good features. There are 160 forks in bitbucket, and 17 in github.
I will order them by most number of followers, in bitbucket first:
- https://bitbucket.org/prencher/django-piston/overview
- https://bitbucket.org/yml/django-piston/overview
- https://bitbucket.org/jespern/django-piston-oauth2/overview
- https://bitbucket.org/jespern/django-piston-oauth10a/overview
- https://bitbucket.org/joestump/django-piston/overview
- https://bitbucket.org/Josh/django-piston/overview
- https://bitbucket.org/ionelmc/django-piston-ext/overview
- https://bitbucket.org/ephelon/django-piston/overview
- https://bitbucket.org/liberation/django-piston/overview
- https://bitbucket.org/joeb/django-piston/overview
- https://bitbucket.org/codysoyland/django-piston-emitter-refactor/overview
- https://bitbucket.org/jricketson/django-piston/overview
- https://bitbucket.org/ionelmc/django-piston-api-auth/overview
I will be able to read some of them in order to prioritize the added
features in all of them, but I think that as a community we can work
together in this part.
I hope more of you help me to increase the actual coverage of piston
at least to 90%, and to set up a list of features as milestone for a
new version of piston.
Bye
--
Jorge Eduardo Cardona
jorgee...@gmail.com
jorgeecardona.blogspot.com
github.com/jorgeecardona
------------------------------------------------
Linux registered user #391186
Registered machine #291871
------------------------------------------------
Jorge Cardona
Hi, I just want to have a new version of Piston and not a code from
two years ago, I have been looking for the 0.3dev code, I only see
version "0.2.3rc1" in bitbucket.
I don't have problems with bitbucket and github, I'm just more used to
git than hg, but I can move the code to Bitbucket. But the problem is
that seems that jespern is pretty busy lately, and I don't mean that I
will be the maintainer, I just want to help to keep alive this project
which seems to have a lot of users.
The community decide where the code goes, but I think that in order to
start to merge all the code around a testing infrastructure is needed
to reduce the risk of break anything, that's what I want in the near
future, to have a good coverage of piston, and I can add it to
But in general I just want to help to keep alive this project, which
has also save my life in many ways.
PD: I just check the repo of django-piston-oauth2 and that the 0.3dev
version updated 2 months ago. Maybe I can fork from it and start to
add coverage testing to that version.
On Wed, Jun 22, 2011 at 5:01 PM, Jason Skicewicz <jsk...@gmail.com> wrote:
> Hi Jorge,
>
> I'm sort of confused. Has it been decided that the official branch of
> django-piston is moving to github? Personally, I look to Jesper's
> repository to better understand what is happening with the project. Are you
> taking over as the new maintainer of the project? I know there was some
> discussion on the list related to whether to move to github or to keep the
> project on bitbucket, but wasn't sure that anything had been decided. I
> have been running Piston 0.3dev in production for close to 4 months now
> without any problems, and am also wondering if there will be an official 0.3
> release, and if so, where will it be hosted?
> Wouldn't it have made more sense to have kept the project on bitbucket?
> Seems like merging all of those repos from bitbucket to github is sort of a
> waste of time. When a project is stored all over the place, and branches are
> not merged into some main tracking repo along with periodic releases, it's
> near impossible to keep track of where to find the stable branch. I'm
> hoping this is not what is going to happen to this project. This project
> has really made my life so much easier, and has basically worked for me
> right out of the box. A big thanks for that!
> Hopefully you can clear up some of my confusion here.
> Thanks,
> -Jason
>> --
>> You received this message because you are subscribed to the Google Groups
>> "django-piston" group.
>> To post to this group, send email to django...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-pisto...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-piston?hl=en.