Christian,
Did you review the changes in the w3af package? What can we
improve? Could you test the package in a vanilla Kali?
I believe that running all tests is not an option for testing the
deb package, running all packages simply takes a lot of time. We could
write one or two tests, with a target of a local webserver, and run a
simple scan against that... but as with everything I'm doing these
days, I would like it to be automated. The tool to use in this case
seems to be auto-pkg-test: any experience with that?
[0] http://packaging.ubuntu.com/html/auto-pkg-test.html
Regards,
On Thu, Apr 3, 2014 at 9:27 PM, Christian Heinrich
<christian.heinr...@cmlh.id.au> wrote:
> Andres,
>
> The w3af "nose" tests, etc should be executed within the
> ./DEBIAN/rules file i.e.
> https://github.com/andresriancho/w3af-kali/blob/master/debian/rules.
>
> As far as I am aware there is no Continuous Integration (CI) for Kali
> Linux however CI should be possible with Tox and Jenkins. You have
> also raised Tox in the past within
> https://github.com/andresriancho/w3af/issues/1048
>
> On Fri, Apr 4, 2014 at 1:33 AM, Andres Riancho <andres.rian...@gmail.com>
> wrote:
>> How do you believe we can improve the package? Could you run some
>> tests over it to make sure it works well? Do you believe we could add
>> some type of automated build + test to the process to make sure it
>> doesn't break?
>
>
> --
> Regards,
> Christian Heinrich
>
> http://cmlh.id.au/contact
--
Andrés Riancho
Project Leader at w3af - http://w3af.org/
Web Application Attack and Audit Framework
Twitter: @w3af
GPG: 0x93C344F3
------------------------------------------------------------------------------
_______________________________________________
W3af-develop mailing list
W3af-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/w3af-develop
