Open GoogleCodeExporter opened 9 years ago
Original comment by jeff.br...@gmail.com
on 6 Jan 2008 at 7:07
Original comment by jeff.br...@gmail.com
on 6 Apr 2008 at 2:22
Another use for profiles is be to leverage XML processing instructions in the
test
assembly configuration file.
eg.
<?if TEST?>
<config for test environment>
<?endif?>
Original comment by jeff.br...@gmail.com
on 11 Oct 2008 at 6:09
Original comment by jeff.br...@gmail.com
on 19 Nov 2008 at 11:58
Could enable additional properties to be passed in besides profiles. Perhaps
let
individual test frameworks decide how they want to consume these options. So
MbUnit
might consume a Profile property (and possibly other options as well) but a
different
framework might use other things.
One neat trick would be to allow test frameworks to expose the set of
properties they
can use, possibly based on the results of initial test exploration. In
particular,
it would be neat if they could publish well-known values for those properties.
So for integration testing someone might use an "Environment" property to
specify the
target environment. Its allowed values might be "Dev", "Test", "Stage",
"Prod". The
property and its values would be declared using a config file or
framework-specific
attributes.
This mechanism might also enable a data-driven test to be executed with specific
values bound to its parameters by the user, given appropriate framework support.
Original comment by jeff.br...@gmail.com
on 20 Mar 2009 at 10:02
Original comment by jeff.br...@gmail.com
on 23 May 2009 at 1:52
Original comment by jeff.br...@gmail.com
on 29 Jun 2009 at 8:33
Original comment by Yann.Tre...@gmail.com
on 18 Jul 2010 at 8:09
Original comment by Yann.Tre...@gmail.com
on 14 Jun 2011 at 5:53
Original issue reported on code.google.com by
jeff.br...@gmail.com
on 10 Dec 2007 at 9:54