search

google-code-export / mb-unit

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

Report paging does not work correctly in Gallio.Utility rev 3.3 build 300 #835

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Execute a huge test suite (Our NightlyTests.xml is 22MB)
   Enable report paging, we set HtmlReportSplitPageSize=100
2. Run Gallio.Utility.exe FormatReport /rt:html NightlyTests.xml 

What is the expected output? What do you see instead?
- Expected output is that each page contains max 100 tests, and that links on 
the summary page are correct
- Observed result is that the first 10 pages are correct, but content for pages 
11 and up are added to page 10, and pages 11+ are not created.

Directory content after Gallio.Utility.exe completed:
     117.831 NightlyTests.html       
   3.933.945 NightlyTests.Page1.html 
  10.932.913 NightlyTests.Page10.html
   3.528.708 NightlyTests.Page2.html 
   3.233.882 NightlyTests.Page3.html 
   2.974.088 NightlyTests.Page4.html 
   2.804.225 NightlyTests.Page5.html 
   3.837.679 NightlyTests.Page6.html 
   3.837.068 NightlyTests.Page7.html 
   3.954.071 NightlyTests.Page8.html 
   3.925.025 NightlyTests.Page9.html 
  22.617.678 NightlyTests.xml        

What version of the product are you using? On what operating system?
  Windows XP-32bit
  Gallio Utility - Version 3.3 build 300
  (NightlyTests.xml file was generated Gallio Echo - Version 3.2 build 744)

Please provide any additional information below.
  We are using TestLog features quite heavily - so the size of each test vary significantly - some have _very_ large log sections - this may be related to provoking this bug

Original issue reported on code.google.com by espen.al...@gmail.com on 13 Apr 2011 at 9:12

GoogleCodeExporter commented 9 years ago 
Sorry, I can't reproduce the problem. I just tried to format a report with 
6000+ tests and got 31 well-formed HTML pages (page size = 200) as expected.

1. Could you please try again with the latest binaries of Gallio (maybe it was 
a side-effect of a bug which was fixed in the mean time)
2. If not confidential, could you please provide the XML report that causes the 
problem (or you might send it directly at yann dot trevin at gmail. So I can 
have a look)

Regards,
Yann

Original comment by Yann.Tre...@gmail.com on 30 Apr 2011 at 11:23

GoogleCodeExporter commented 9 years ago

Original comment by Yann.Tre...@gmail.com on 19 May 2011 at 5:29

GoogleCodeExporter commented 9 years ago 
Just upgraded to the release version (Gallio 3.3.422) - and the problem still 
persists.
The report xml file is a merged report - and it contains a _significant_ amount 
of text in the Log sections.

The xml is unfortunately confidential, I will see if I can reproduce the issue 
with a "non-confidential" test suite.

Original comment by espen.al...@gmail.com on 5 Oct 2011 at 12:54

GoogleCodeExporter commented 9 years ago 
Yes Espen, I can now reproduce the problem. I'm going to see what happens 
exactly. 
Yann.

Re: Tried to update the issue, but looks like code.google.com is down for 
maintenance.  The attached testfixture reproduces the problem. 2000 tests are 
created, and the XML file contains all, xml file is attached. I also notice 
another bug – the Summary section does not contain the StaticTestFactory test 
cases. I hope you can reproduce this issue on your side…
Regards 
Espe

Original comment by Yann.Tre...@gmail.com on 5 Oct 2011 at 5:32

GoogleCodeExporter commented 9 years ago

Original comment by Yann.Tre...@gmail.com on 5 Oct 2011 at 5:33

GoogleCodeExporter commented 9 years ago 
Fixed. There was an inconsistency between the way step runs are indexed and the 
criterion of visibility in the VTL report.

The summary section does only show the parent test nodes. In your sample 
report, the parent of the 1000 tests made by data factory is "PagingTest" which 
is visible in the summary. But the 1000 other tests generated with the static 
test factory are created directly in the scope of the test fixture itself 
(TestLogPagingTest), like any other regular test method. So it's not a bug ;) 
it's just by design.

Original comment by Yann.Tre...@gmail.com on 5 Oct 2011 at 8:49

GoogleCodeExporter commented 9 years ago 
Excellent - when can I download a new Gallio version with the issue fixed?
(Looks like the gallio CCNet server is still crunching an old build...)

Original comment by espen.al...@gmail.com on 6 Oct 2011 at 8:15

GoogleCodeExporter commented 9 years ago 
Yeah, the build server is a bit unhappy at the moment :(

Once we can get it unstuck, it should be in 3.3.450.

Original comment by grahamr...@gmail.com on 6 Oct 2011 at 8:41

GoogleCodeExporter commented 9 years ago 
Please try build 3.3.452

http://ccnet.gallio.org/Distributables/

Original comment by grahamr...@gmail.com on 10 Oct 2011 at 4:36