cpanparty is over
Well, it was a great party but .. It seems everybody needs to get home, as home is better place than being a guest somewhere ... as Russian would say ;)
But to be serious I am going to close cpanparty project as:
I don't have much time to write new test cases for existed CPAN module and it seem nobody wanted to join this process
My initial idea behind sparrowhub was to create a repository of reusable test / monitoring suites to match various life practical cases. CpanParty is a bit different - this is specification by example / test descriptions of existed CPAN modules. Still thinking that idea is quite interesting I am going to remove cpanparty plugins from sparrowhub to keep it clean and dedicated to initial purposes so not to confuse user asking how can I use test cases for Dancer2 or Mojlicious or other great web frameworks in my daily test/monitoring tasks?
So farewell for CpanParty!
- cpanpatry plugins will be removed from sparrowhub index
- plugins source code will remain on my github repos though
- let'me know if for some reasons you want to resurrect or start new cpanparty tests for some CPAN distributions ....
Before you shut it down, just a feedback. Even at a second look, I did not understand what the purpose of cpanparty is and what problem it aims/aids to solve.
You might want to add something about *why* anyone would want to use it, and make this info very easy to reach from the head of the home page (and possibly every page). Otherwise, I fear that you might have a gem that is still buried in the ground.
Hi Flavio! There was a post explaining what cpanparty is. To say in short words here - it was an attempt to start a repository of blackbox testing for some existed cpan modules, a bit latter I came with idea of thinking about this with focus on specification examples, like people could easily start using a given module just _looking_ at cpanparty report for it, which in TDD manner explain what module is. Well time passed and decided to stop this project, for the reasons in this post explained ... I don't blame anybody at all ;) I just started to feel like it is going to be too hard for me to maintain and add new stuff without anybody helps. But ... if someone still interested in the idea, ok we could talk more about this - github / email / chat ;)
Hi! I'm a bit slow, but I still think that the idea might be great and maybe most people (me included) just don't realize it.
I read the article you pointed to, but really didn't make much out of it.
Just before giving up, I'd suggest to write an article where you explain the problem, the solution an possibly provide a step-by-step example of how different users might benefit.
Or... just move on to your next project, and good luck!!!
Hi Flavio! Thanks for suggestion. Will think about it ... But in general I wanted this:
* given we a have some CPAN module, let's say Dancer2 web framework
* often module documentation is quite fine, but after user read the documentation ( of before this ) he could *take it for a spin* using a sample code snippets to understand on practice what this module look like
* ok, CPAN party probably has such a code snippets ( aka sample code ) for given CPAN modules, so user could gain all he needs to realize how some module works in practice:
1. ( optional but very useful if exists ) - informal description of test case
2. sample code
3. input data ( http request parameters and verbs in case of web application framework )
4. output data ( http status code and http body )
That is it. This is specification by example. This is _somewhat_ similar to cucumber feature approach when one writes a unified test case:
And finally what is very important such a test case is real, mean it is executed on CPANParty server, so user could rely on it, as it SHOULD work.
As an example for such approach you may take a look at different CPANParty reports , f.e. - http://swatpm.org/cpanparty/swat-dancer2.html for Dancer2