Hey all,
I'm trying to fuzz new and experimental features as soon as possible. The
speed at which we are adding new features makes it hard for me to track what
we are adding and write fuzzers for each new feature. However, I have been
working on fuzzers that should be able to find and test these new features
without me even knowing about them, but looking at the source code. However,
if these new features need to be abled through a command-line switch, my
fuzzer will try to fuzz a disabled feature and waste time.
So, I was wondering how feasible it is to create an
"enabled-all-experimental" switch. Each new feature could still be disabled
by default and continue to have a seperate switch to enable it specifically,
but all these new and experimental features should also be enabled when
the "enabled-all-experimental" switch is supplied. That way, I wouldn't have
to worry about which features we are working on but are still disabled by
default.
Unles anybody objects, I will get this implemented, but it would of course
require future experimental features to also check for this switch, or it
will become useles pretty quickly. So, I will need everybody's cooperation.
Thanks!
BJ
Berend-Jan Wever (skyli...@google.com) | Security Software Engineer
Google Netherlands B.V. | Reg: Claude Debussylaan 34, 15th floor 1082 MD
Amsterdam
34198589 | NETHERLANDS | VAT / Tax ID:- 812788515 B01
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
To unsubscribe from this group, send email to
chromium-dev+unsubscribegooglegroups.com or reply to this email with the words
"REMOVE ME" as the subject.
