[cgl_discussion] configurable requirements - are they specified
mika at osdl.org
Tue Oct 8 06:51:55 PDT 2002
Errr... the definition of "configurable" is that the feature needs to
be active when the testing is made, but it can be _after_ that
deactivated using normal configuration and recompilation (changing
the source code is not allowed) to allow end-user to "configure out"
those features they do not want to use.
So given the definition above, I do not understand your
question/request, as from the testing point of view, there is no
difference between core and configurable features. You might want to
test the impact of configuring one or several of these "configurable"
features out, but IMHO that job should be left to the distribution
On ma, 2002-10-07 at 17:22, Craig Thomas wrote:
> I was looking over the Requirements Definition version 1.1 document
> and I counted 45 requirements that are classified as configurable.
> This includes all priority 1, 2 and 3 requirements.
> My question is: Has someone put together the actual specification
> for the names of these configurable variable names and the possible
> values (OK, I realize they would be '=y' or '=n', in a config file, but
> I'm stating this for completeness)?
> Some of these are set as a boot command option, so these names and
> values would be helpful as well.
> If someone has this information on a single cheat sheet, I would
> appreciate a copy of it. Furthermore, I would think that this is a good
> thing to add to the Requirements Definition document under each
> configurable requirement.
> Craig Thomas phone: 503-626-2455 ext. 33
> Open Source Development Labs email: craiger at osdl.org
> 15275 SW Koll Pkwy, Suite H
> Beaverton, OR 97006
> cgl_discussion mailing list
> cgl_discussion at lists.osdl.org
More information about the cgl_discussion