Hi! > I ask again, should I merge it? If so, tell me which branch and I'll > verify the code, apply some changes, let you know if I added/require > you to add more unittests, etc.
Andres, I have already answered you :) But let me try again. Code for repeated parameters names limit is in my branch [0]. It is ready to merge with trunk and only thing that we want is unittests for it. > I would love to remove branches; many branches mean lots of started > but not finished work; which sucks.- Exactly! I have also thought about it last time. I will review my branches soon. [0] http://w3af.svn.sourceforge.net/svnroot/w3af/branches/oxdef > >> >>>> On Fri, Jun 22, 2012 at 5:44 AM, Taras<ox...@oxdef.info> wrote: >>>>> >>>>> I also suggest to "branch" this task with tests and merge >>>>> fuzzRepeatedParams >>>>> into trunk without it. Because currently we are talking about >>>>> improvement of >>>>> tests code and not about fuzzRepeatedParams related code with doctests. >>>> >>>> >>>> I got lost here my friend, should I merge something into trunk? >>> >>> Some time ago I have implemented fuzzRepeatedParams option and related >>> code for _createMutantsWorker in my branch. I have also written doctests >>> for it. But you asked me also to code unittests inside >>> plugins/tests/test_xss.py for it before merging it with the trunk. >>> >> >> -- >> Taras >> http://oxdef.info >> GPG: C8D1F510 > > > -- Taras http://oxdef.info GPG: C8D1F510 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
