Re: #39: Make atf-run | atf-report support user defined configuration variables

["atf trac notification" <nobody%julipedia.org@localhost>]

#39: Make atf-run | atf-report support user defined configuration variables
--------------------------------+-------------------------------------------
 Reporter:  ekamperi@...        |       Owner:  REPORTER
     Type:  enhancement         |      Status:  assigned
 Priority:  minor               |   Milestone:          
Component:  atf-run             |     Version:  HEAD    
 Keywords:                      |  
--------------------------------+-------------------------------------------

Comment(by anonymous):

 Replying to [comment:1 jmmv]:
 > Also, one more thing to consider is: you currently want to print
 command-line provided configuration variables; correct?  What about the
 ones in the system-wide configuration files and the test-suite
 configuration variables (those in the Atffile)?  Would it make sense to
 report them?  If yes, things get tricky because these depend on the
 "current test-suite", which can change on a directory basis. [...]

 I had in mind both atf-run -v variables and those that live inside
 Atffile. Personally I have 2-3 directories with test programs, and 1
 Atffile for each directory. There, I define some  configuration variables
 such as 'fuzzing' or 'iterations' which I want to affect all test programs
 within the current directory.

 I then run my suite with 'atf-run foo/ dir/ bar/' and thought that it
 would be useful to know with which variables each test-suite (=directory)
 ran. For example a fuzzing pass with 10M iterations has a different weight
 than one with 10K.

 Anyway, my use flow may be very special. And if it's too messy to
 implement, I can live without it ;)

 Cheers,
 Stathis

-- 
Ticket URL: <http://www.julipedia.org/projects/atf/trac/ticket/39#comment:2>
Automated Testing Framework <http://www.NetBSD.org/~jmmv/atf/>
Automated Testing Framework