Trevor Parscal writes:
> I don't know where this landed, but I wanted to point out that system
> testing might be a better name for out use of Selenium, Acceptance
> testing has more of a "customer is accepting a product" connotation.
During our discussion last Friday, Marcus, Priyanka and I d
On 8/9/10 11:27 AM, Mark A. Hershberger wrote:
> Dan Nessett writes:
>
>> For unit tests the tester directly accesses the code and so has direct
>> access to LocalSettings. For selenium testing, we originally had a
>> configuration file called SeleniumLocalSettings.php, but that was
>> abandoned
Dan Nessett writes:
> For unit tests the tester directly accesses the code and so has direct
> access to LocalSettings. For selenium testing, we originally had a
> configuration file called SeleniumLocalSettings.php, but that was
> abandoned in favor of putting the configuration information in
>
On Sat, 07 Aug 2010 23:30:16 -0400, Mark A. Hershberger wrote:
> Dan Nessett writes:
>
>> I don't think walking through all the extensions looking for test
>> subdirectories and then running all tests therein is a good idea.
>> First, in a large installation with many extensions, this takes time
On Sun, Aug 8, 2010 at 6:47 PM, Platonides wrote:
> Anyway, I don't think you could do that. If the extension isn't
> installed, you won't pass whatever extension behavior it is testing,
> would it?
It should be possible to run unit tests in some cases even if the
extension isn't actually install
Mark A. Hershberger wrote:
> Dan Nessett writes:
>
>> I don't think walking through all the extensions looking for test
>> subdirectories and then running all tests therein is a good idea. First,
>> in a large installation with many extensions, this takes time and delays
>> the test execution.
>
On Fri, Aug 6, 2010 at 2:27 PM, Trevor Parscal wrote:
> I think /tests/unit and /tests/acceptance would be reasonable places
> to put things, and if they are both within maintenance or in the root
> doesn't really matter to me.
>
> Remember Selenium is a framework for doing acceptance testing, no
On Sat, Aug 7, 2010 at 3:35 PM, Trevor Parscal wrote:
> I'm not /totally/ opposed to breaking away from the standard terminology
> of unit/integration/acceptance testing... We could call it something
> more descriptive than system though - perhaps "client"...
Going with names like "unit" and "c
Dan Nessett writes:
> I don't think walking through all the extensions looking for test
> subdirectories and then running all tests therein is a good idea. First,
> in a large installation with many extensions, this takes time and delays
> the test execution.
Globbing for extensions/*/tests/Test
Trevor Parscal writes:
> Remember Selenium is a framework for doing acceptance testing, not unit
> testing.
Right. They can also serve as (I hope) regression tests — which is what
I'm mostly concerned with here.
Mark.
--
http://hexmode.com/
Embrace Ignorance. Just don't get too attached.
>
> KIT - University of the State of Baden-Wuerttemberg and
> National Research Center of the Helmholtz Association
>
> -Original Message-
> From: wikitech-l-boun...@lists.wikimedia.org
> [mailto:wikitech-l-boun...@lists.wikimedia.org] On Behalf Of Trevor Parscal
&
to:wikitech-l-boun...@lists.wikimedia.org] On Behalf Of Trevor Parscal
Sent: Friday, August 06, 2010 8:27 PM
To: wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] Testing Framework (was Selenium Framework - Question
on coding conventions)
I think /tests/unit and /tests/acceptance would be
I think /tests/unit and /tests/acceptance would be reasonable places
to put things, and if they are both within maintenance or in the root
doesn't really matter to me.
Remember Selenium is a framework for doing acceptance testing, not unit
testing. I don't quite see the purpose of specifying
On Fri, 06 Aug 2010 12:38:39 -0400, Aryeh Gregor wrote:
> On Thu, Aug 5, 2010 at 6:47 PM, Mark A. Hershberger
> wrote:
>> Can I suggest that the framework can see that an extension has tests
>> simply by the presence of the /tests directory containing
>> a *TestSuite.php file?
>
> IMO, the way p
On Thu, Aug 5, 2010 at 6:47 PM, Mark A. Hershberger wrote:
> Can I suggest that the framework can see that an extension has tests
> simply by the presence of the /tests directory containing a
> *TestSuite.php file?
IMO, the way parser tests do it is smarter. When you install the
extension, it ad
On Thu, 05 Aug 2010 18:47:58 -0400, Mark A. Hershberger wrote:
> Markus Glaser writes:
>
>> 1) Where are the tests located? I suggest for core to put them into
>> maintenance/tests/selenium. That is where they are now. For extensions
>> I propse a similar structure, that is /tests/selenium.
>
>
On Thu, Aug 5, 2010 at 6:47 PM, Mark A. Hershberger wrote:
> Markus Glaser writes:
>
>> 1) Where are the tests located? I suggest for core to put them into
>> maintenance/tests/selenium. That is where they are now. For extensions
>> I propse a similar structure, that is /tests/selenium.
>
> Sound
Markus Glaser writes:
> 1) Where are the tests located? I suggest for core to put them into
> maintenance/tests/selenium. That is where they are now. For extensions
> I propse a similar structure, that is /tests/selenium.
Sounds fine.
In the same way, since maintenance/tests contains tests that
18 matches
Mail list logo
