Re: On Demand Nmap Build Testing

[jrf <jay.fink () gmail com>]

Agreed. Although I don't know about the exact method (e.g. make test
etc.) it would undergo the current process. That is we could get
something together, send it to the list for interest/inclusion as some
later date.

Right now what I need to know is what do we think are some core tests
for all platforms and are there any per platform particulars.

I can't possibly iterate through every single nmap general operation
but I am sure there is a well known common set of options we like to
use (I for one almost always use -sV on a first pass).

In the meantime, I can work on building out the script to not just do
build but add on testing, then tack on what everyone thinks we should
as I go along.

On Wed, Jun 02, 2010 at 09:16:31AM -0500, Daniel Miller wrote:
> It'd be great if the common tests were distributed with the source. Perl  
> packages ship with tests that can be run with `make test`. This would  
> make it easier for anyone compiling from source to run some basic tests  
> and send back the results if it breaks.
>
> Dan
>
> On 06/02/2010 05:54 AM, jrf wrote:
> > Sounds close to regression testing.
> >
> > Yes dovetailing that right onto builds would be a great move.
> > No reason to wait until next year. I can bang around with this in my
> > spare time and it isn't exactly a high priority item so there is
> > zero pressure.
> >
> > Could we enumerate some common tests then maybe OS specific ones?
> > What I would do is for an initial pass write a script (or many) then
> > hopefully get it to the point where it is something we can all use and
> > easily adapt.
> >
> > Perhaps if a script turns out not to be good enough, a full blown
> > harness could be a project for next summer of code.
> >
> > On Tue, Jun 01, 2010 at 05:30:44PM -0400, Michael Pattrick wrote:
> >    
> > > It's a good idea, especially with how practically any modern computer
> > > can handle many simultaneous VMs with ease. But I would suggest
> > > integrating tests into the mix; bugs that break builds are easily
> > > identified. More useful would be if we could detect when a change
> > > makes OS detection less accurate, or if FIN scan stops working on
> > > NetBSD.
> > >
> > > Maybe something for next SoC...
> > >
> > > -M
> > >
> > > On Tue, Jun 1, 2010 at 9:50 AM, jrf<jay.fink () gmail com>  wrote:
> > >      
> > > > All,
> > > >
> > > > I thought I would share this with everyone in case anyone else was
> > > > interested in doing something similar. Last week I setup some very
> > > > simple scripts to do the following with virtual machines:
> > > >
> > > > start a screen session and logit
> > > > power on a vm
> > > > ssh to a vm and execute a script which then does:
> > > >   svn up of nmap
> > > >   rm -rf previous build (ran into problems running clean)
> > > >   cp -R nmap nmap-build
> > > >   cd nmap-build
> > > >   configure&&  make
> > > > power off vm
> > > > mv the screenlog
> > > >
> > > > Then I repeat the process for the next vm. Right now I am only doing
> > > > two, NetBSD-current (as of 2 weeks ago) and FreeBSD-current. I do
> > > > periodic updates and builds manually on my physical debian and mac
> > > > systems anyhow.
> > > >
> > > > At this point I am just about ready to automate building on NetBSD,
> > > > FreeBSD and Linux (the mac not so much as I use it for work :)
> > > >
> > > > Anyhow, just something I thought everyone might be interested in. So
> > > > far the only *problem* I have come across is the subshell on NetBSD is
> > > > kind of a pain so I switched the build user to bash from pkgsrc.
> > > >
> > > > Regards,
> > > >   j
> > > > _______________________________________________
> > > > Sent through the nmap-dev mailing list
> > > > http://cgi.insecure.org/mailman/listinfo/nmap-dev
> > > > Archived at http://seclists.org/nmap-dev/
> > > >
> > > >        
> > _______________________________________________
> > Sent through the nmap-dev mailing list
> > http://cgi.insecure.org/mailman/listinfo/nmap-dev
> > Archived at http://seclists.org/nmap-dev/
> >
> >    
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/