skaliber / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

RowTest and Timeout attributes do not play well together. #674

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Have a RowTest test with a timeout defined such that one individual test 
will not trip the timeout, but the cumulative duration of all rows will be 
longer than the defined Timeout.
2. Run the Tests

What is the expected output? What do you see instead?
Should not see a Timeout since the individual tests are less than that the 
defined Timeout - instead, once the cumulative duration passes the defined 
Timeout, the rest of the Rows fail with the Timeout exception.

What version of the product are you using? On what operating system?
Gallio Icarus 3.1 build 397
MbUnit v3 3.1.0.0
MbUnit.dll - v3.1.397.0

Windows XP Pro sp2

Please provide any additional information below.

The original details I posted to the User Mailing list follow:

I setup a test with 3 rows, and on the test itself set the timeout to 900
seconds,

        [Test, MultipleAsserts]
        [Timeout(900)]
        [Row("estore_sc1")]
        [Row("estore73")]
        [Row("estore_sp1")]
        public void xRowTest(string sLoginName)  {<snip the actual code of
the test itself>}

 then ran it - here's the feedback I got - but the cumulative set timed out
after 900 total seconds for all 3 rows - not 900 per row:

Duration: 900.449s, Assertions: 49.

   - xRowTest
   Duration: 900.408s, Assertions: 49.
     After Test Instance
   The test timed out after 900 seconds.
   - xRowTest("estore73")
      Duration: 506.265s, Assertions: 31.
      - xRowTest("estore_sc1")
      Duration: 275.559s, Assertions: 11.
        An exception occurred. <snip an exception in the test itself>

      - xRowTest("estore_sp1")
      Duration: 118.546s, Assertions: 7.
        Execute
      The test timed out after 900 seconds.

You can see from the duration of the individual rows that it was to total of
all 3 rows that exceeded 900 seconds when the 3rd row timed out, NOT the
individual row. 

Original issue reported on code.google.com by Drogo...@gmail.com on 18 Jun 2010 at 7:37

GoogleCodeExporter commented 8 years ago
ref. 
http://groups.google.com/group/gallio-user/browse_thread/thread/697f27b731a84d58
/918653391d2b332f

Original comment by Yann.Tre...@gmail.com on 12 Aug 2010 at 6:24

GoogleCodeExporter commented 8 years ago

Original comment by Yann.Tre...@gmail.com on 14 Jun 2011 at 5:53