is there a way to limit size of .html log pages? HTML files are too big to load
Hello,
I was curious if there is a way beside breaking up .fftc's to not have so much.... if there was a nice way when saying "save to .html" if it could be broken up into parts?
Reason being is that I have .html files that are > 1mb and they take for-ever to load or open in firefox... OR if they're really big... say 5-10+ mb for big test casees I have... then they dont open at all...
and when I try to share with developers issues that I have found with in... the files are not too user friendly...
maybe if there doesnt exist the option, in the future have the option for the files to be exported in parts with an index file... so they dont get too big? ...
thanks in advance for your help
Message Edited by jus4kikz on 08-05-2009 05:53 PM Message Edited by jus4kikz on 08-05-2009 05:53 PM
This is a great suggestion for improvement. We currently do not provide any way to break the HTML exports into smaller documents.
There are a few workarounds which you may want to try:
1. Use the "text" version to share. These do not have rendering limitations as an HTML file would have.
2. You can edit the HTML XSLT to reduce the amount of information being exported. You can make your own copy of this XSLT if you do not want to change the standard one.You can also change this XSLT to produce multiple files with a top file which links to other files.
3. You can buy iTest Personal licenses and "float" them so that developers can use them for reading and running your testcases. This way you do not have to export any files and they can use the actual testcase files and they can also run them :-)
Message Edited by KumarS on 08-05-2009 06:16 PM
ok...
I like #3 the best, but sadly due to the learning curve and such it has been our responsability to put as much info into the filing of issues and how to reproduce them... I have been lucky a few times where developers will run the automation we create, but typically thats not the case...
I like the level of detail that the reports expose, so I dont think I'd want to cut back on them... so I guess until there is an "indexing" method available for the html I'll have to try the .txt option...
or have to re-run the automation in such a manner that I comment out all the other things that are not being exposed..
thx
Message Edited by jus4kikz on 08-05-2009 06:31 PM
The next release of iTest will use an XSLT 2.0 compliant processor for generating test reports. This supports <xsl:result-document> which can be used to create multiple outputs. Attached is a sample script which uses this to create a HTML page for each step, indexed via the main page.
