Floyd,
On Thu, Sep 30, 2010 at 6:12 AM, Floyd Fuh <floyd_...@yahoo.de> wrote:
> Hi Andres, Javier, Taras,
>
> Is it planned to introduce something like unit tests? Maybe
> add a rule to the developer guide about that.
I'm not sure if community contributors (mostly web application
pentesters, university students, etc.) will write unit tests. I don't
want to close the doors to our contributors, I want to open them as
wide as possible. On the other hand, I would love to see this as an
optional thing for community contributors but a MUST HAVE for paid
developers :)
> Javier, I think it was much easier for you to integrate [1],
> because some tests were included, right?
>
> I'm currently reading [2] and I can really recommend that book.
>
> [1] http://sourceforge.net/apps/trac/w3af/ticket/160064
>
> [2]
> http://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882
>
>
> floyd
>
>
>
> -----
> http://www.floyd.ch
>
>
> ----- Ursprüngliche Mail ----
> Von: Taras <ox...@oxdef.info>
> An: Andres Riancho <andres.rian...@gmail.com>
> CC: w3af-develop@lists.sourceforge.net
> Gesendet: Montag, den 27. September 2010, 23:10:45 Uhr
> Betreff: [W3af-develop] [SPAM] Re: Playing with python-gtksourceview2
>
> Hi all and sorry for late answer :)
>
> ...
>> > it is not enough to solve problem of release stability. This tester will
>> > find
>>a lot of bugs after new code will be added to the trunk and then we will need
>>to
>>fix them on RC stage. It is bad
>> > practic to add new features on RC stage.
>>
>> I think that we should follow the scrum methodology, in which each
>> sprints delivers a piece of software / enhancement that's ready to
>> ship and adds value to the product. With this in mind this is how it
>> will work:
>>
>> - Sprint starts
>> - Developers think how to solve the problem
>> - Tester thinks how to test the developers solution
>> - Developers create code
>> - Tester creates tests
>> - Developer commits code to the trunk (or a branch if the change is too big)
>> - Tester gets the code from the trunk and runs scans against his test pages
>> - Tester gets the code from the trunk and runs regression scans
>> - Developer fixes regressions and bugs
>> - Sprint ends [2 weeks after starting]
>>
>> > New code especially when it touches the core or simply has a lot of lines
>> > in
>>most
>> > cases will bring bugs. It is the bad truth of development.
>>
>> I think that if we really stick to the above procedure, we shouldn't
>> have any issues :)
> Hmm, ok. Let it will be SCRUM :) It will be interesting to see how it
> will work with open source project.
>
> --
> Taras
> http://oxdef.info
> ----
> "Software is like sex: it's better when it's free." - Linus Torvalds
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> W3af-develop mailing list
> W3af-develop@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/w3af-develop
>
>
>
>
>
--
Andrés Riancho
Founder, Bonsai - Information Security
http://www.bonsai-sec.com/
http://w3af.sf.net/
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
W3af-develop mailing list
W3af-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/w3af-develop
