On 05/27/2011 05:52 PM, Adam Williamson wrote:
On Fri, 2011-05-27 at 16:54 +0000, Athmane Madjoudj wrote:
[...
SNIP ...]
That's fine: it's always good to write up test procedures even if they
require advanced knowledge or tools to actually complete. The benefits
don't go away - it's still good to have the procedure documented so we
know it will be performed consistently, and categorized so we know what
test cases relate to what apps. Of course, you should note the
appropriate requirements to perform the test case in the description
and/or setup steps :)
OK, I need time to get some mediawiki skills (I've never worked with
wiki beside Trac)
> 2. I've noticed that ABRT is not included in Security Lab
spin, which
> make life harder to report bugs, especially for non-experienced.
That's interesting, maybe it could be added for future releases? For now
you could probably put this in the setup steps too. I'm fond of using
wiki templates in test cases: it's neat and easy. You can just create a
template page with the contents:
[... SNIP ...]
Yes, but Security Lab spin is supposed to be 100% functional from live
media (CD/USB etc...) especially when disk forensics is involved.
--
Athmane Madjoudj