You see what I mean? I had no idea about this thing... And that is after about a full week's worth of time of research. This is very telling I think, and is exactly my point.
I hate to be the 'nagging' persona here, but really, my problem is not about 'working out a solution". My problem is the wild-west reality I have been facing while researching this. Is web2py.test in the book? Where should I have 'stumbled' upon it? How is it that I have managed to miss it completely? I ran searches in the book, in this group for the keywords "nose", "pytest" "py.test", "testing", and the like, as well as some google searches, and meticulously read through almost all of the search-results that came up in all cases - and now, by sheer serendipity, you are presenting me with this thing that I somehow have managed to miss entirely... Does this sound like a nice learning experience to you? This is the issue at hand - it's a documentation/organisational issue, not a technical one. I wouldn't know what to answer about the technical stuff - I would expect there to be much more knowledgeable people than me on these issue that would have much better answers than what I would be able to come up with... I just would like to have had such people oriented towards documenting this, or at the very least have some topic, or even a 'mention' about this in this user-group. If nothing else, so people would know that there is something in the works, and not be working independently on their own implementation, completely blind to what is going on with this. The lack of exposure about this is generating a acumen out of which duplication-of-efforts emerge - this is inefficient. The same goes for research-resources that are duplicated and wasted - I'm sure I am not the only one who has gone through this research. There needs to be better management and effort-synchronization, as well as better transparency about "things that are in the works", and a centralized 'go-to' place for looking such-things up. A section in the main web2py website, for example, a news-feed, an rss, a mailing-newsletter, I don't know, "something"... The book is awesome but it's a reference-manual, and it's already way too long - more than 600 pages on a PDF... And it is not updaed as often as things come-up - it's the wrong tool for the job - there needs to be more kinds of documentation-options, some-of-which should be much more frequently updating. On Sun, May 19, 2013 at 10:23 PM, Vinicius Assef <[email protected]>wrote: > On Sun, May 19, 2013 at 8:48 PM, Arnon Marcus <[email protected]> > wrote: > > > > Where is the "ggod stuff"? > > The "good stuff" is in our hands and heads. We can join together to > help make it happen. > That's the beauty of open source. Join us and help us develop this > kind of thing, if what exists today doesn't fit your needs. > > > > Where is the "best-practice"? > > There's no Web2py "best-practice" concerning this subject, yet. > As Niphlod wrote: we're working on it and web2py.test [1] is a path. > > > > Where is the "batteries-included"? > > They're not "charged" neither "installed" yet. > > > But, what have you tried until now? > Did you try web2py.test? > Have you had some success? Some problem? > Do you have some suggestion to improve it? > Do you have some advice? > How can you help us to evolve this WIP? > > [1] http://github.com/viniciusban/web2py.test > > -- > Vinicius Assef > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "web2py-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/web2py/CHfZTr5xHso/unsubscribe?hl=en. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
