Sahoo wrote:
> I agree with Marina. Don't use QL as a vehicle to remind people that
> they have an open bug. I suggest people not to turn any test in QL
> that is known to fail.
+1
>
> Thanks,
> Sahoo
>
> Marina Vatkina wrote:
>
>> Anissa Lam wrote:
>>
>>>
>>> I will say no. Why do you want to turn off the test ?
>>
As you all know, it is always good to have many tests to run against our
product. In future, we will be running entire SQE test suites on Hudson
against trunk build. But, if you are adding a test that is for sure
going to fail anyway, what is the point? When tests that pass are
added to the codebase, it would forms a base line to refer to when the
same test fails. Based on that we know, what worked before, compared
to now in the timeline.
Please consider our trunk as a production system that is evolving
continuously. Testing the system that is known to show fail will not
make any to sense to several others and in fact confuses and takes up
their time. The right approach is, to develop as many test as
possible in your own module area/ ws, and then integrate them into the
trunk, when the developer/ you think(s) the sourcebase is ready for
taking such tests to run. (I'm not referring to unit tests for a given
module here. They are important too.)
This also brings up another interesting question... are we going to
make our quicklook to a longlook going forward? That might discourage
some developers running the QL itself because, it now takes a longer
time to run. May be we should have QL with absolute basic functionality
tests and in another maven profile, we should add as many tests as
possible.
Skipping tests is also easy with maven:.
http://maven.apache.org/plugins/maven-surefire-plugin/examples/skipping-test.html
thanks..
>>
>> So that others can easily see if they cause any regressions?
>>
>>
>> It is a valid
>>
>>> test and the system is indeed has problem. There is no way to bring
>>> up the admin console now.
>>
>>
>> That's why we have an open bug. But having a QL that is guarantee to
>> report failures is very confusing...
>>
>> thanks,
>> -marina
>>
>> Jan is looking into the issue and think that
>>
>>> may be related to the Grizzly integration.
>>>
>>> thanks
>>> Anissa.
>>>
>>> Marina Vatkina wrote:
>>>
>>>> Anissa,
>>>>
>>>> Can we turn off Admin Console QL until you find the fix?
>>>>
>>>> thanks,
>>>> -marina
>>>>
>>>> Anissa Lam wrote:
>>>>
>>>>>
>>>>> Thanks to Jason, Admin Console QL is now turned on. If you
>>>>> update your workspace, your QL run will also include admin
>>>>> console QL.
>>>>> As of now, admin console QL is failing because there is problem
>>>>> in the system. We can't access the login page and thus cannot
>>>>> bring up the console. It sure does the job :)
>>>>>
>>>>> An issue has been filed,
>>>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=6131
>>>>> Hopefully we will be able to catch this kind of issue sooner now
>>>>> that the test is in place.
>>>>>
>>>>> thanks
>>>>> Anissa.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>