[prev in list] [next in list] [prev in thread] [next in thread] 

List:       selenium-commits
Subject:    [Selenium-commits] [JIRA] Commented: (SEL-175) In TestRunner,
From:       "Alloni Kramer (JIRA)" <jira () public ! thoughtworks ! org>
Date:       2005-12-19 16:02:59
Message-ID: 98281018.1135008179221.JavaMail.oqa-j2ee () openqa01 ! managed ! contegix ! com
[Download RAW message or body]

    [ http://jira.openqa.org/browse/SEL-175?page=comments#action_12579 ] 

Alloni Kramer commented on SEL-175:
-----------------------------------

This was found to be true both in the 0.6.0 release and the latest revision (668).

> In TestRunner, running all tests and then rerunning a selected test causes \
>                 problems.
> ------------------------------------------------------------------------------------
>  
> Key: SEL-175
> URL: http://jira.openqa.org/browse/SEL-175
> Project: Selenium
> Type: Bug
> Components: TestRunner
> Versions: 0.6
> Environment: Windows XP, tested with both Firefox 1.5 and IE 6.0.
> Reporter: Alloni Kramer
> Priority: Minor

> 
> 
> If you run a test (either in the whole suite or individually), then re-run it \
> individually, the contents of the third column after running the entire suite don't \
> change after re-running the individual test when the test is successful, only if it \
> fails.   Thus, failed test results from the first run-through remain in the table \
> if they succeeded the second time, with the row colored green.  Worse, if the suite \
> is run and then the individual test is run, the third row values from the results \
> of the suite test get set as settings for things which use the third column.  \
> Finally, the results don't get "saved" - if you run all tests, then run an \
> individual test, click on another test to see the results of running that test in \
> the suite, then click on the name of the re-run test again, the results that show \
> up are those from the all test run, not the individual test run. I fixed the first \
> two issues by adding a few lines to reload the test frame before running the tests: \
> function runSingleTest() { addLoadListener(getTestFrame(), runSingleTest2);
> getTestFrame().contentWindow.document.location.reload();
> }
> function runSingleTest2()  {
> removeLoadListener(getTestFrame(), runSingleTest2);
> runAllTests = false;
> resetMetrics();
> startTest();
> }
> but that doesn't fix the third issue, which I'm still working on, and this fix \
> fixes the symptoms, not the problem.  The problem, I think, is that running one \
> test is being treated as something different from running all tests.  Running all \
> tests should be a sequence of run-one-test, rather than them having slightly \
> different run paths.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.openqa.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
Selenium-commits mailing list
Selenium-commits@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-commits


[prev in list] [next in list] [prev in thread] [next in thread]