Hi all,

Maybe you know this site:
http://www.freepascal.org/testsuite/cgi-bin/testsuite.cgi with the results of the automatic testruns for each night.

I've made a new version, using the webdesign package. You can see the result here: http://www.freepascal.org/testsuite/cgi-bin/testsuite.cgi

Source: http://www.freepascal.org/~joost/testsuiteweb_20100530.tgz

I don't like the layout, though. Especially not for the (single) testrun page. But I'm not a designer, so I thought that maybe someone else had a better idea...

Joost.

Looks like the old one ;)

Yeah, I made a perfect copy. ;)

Sigh: http://www.freepascal.org/~joost/wwwroot/testsuiteweb.cgi

Joost.

joost, nice work. I love the filters below the header in the grid, what did you use for that? some jQuery component?

Leonardo M. Ramé
http://leonardorame.blogspot.com

Leonardo M. Ramé wrote

joost, nice work. I love the filters below the header in the grid, what did you use for that? some jQuery component?

Yes, I used jqGrid: http://www.trirand.com/blog/

The webdesign package has a component for it.

Joost.

Joost van der Sluis wrote

Maybe you know this site: http://www.freepascal.org/testsuite/cgi-bin/testsuite.cgi with the results of the automatic testruns for each night.

Both look the same (because they are the same link).

More worrying is that not a single test run listed produced 0 errors. :-/

page. But I'm not a designer, so I thought that maybe someone else had a better idea...

I would immediately suggest tagging the various parts of the HTML output with <div id="xxx"> tags. This would allow a web designer or somebody skilled with CSS to easily improve the look with little effort. Look at the FPCUnit test output which uses XML + CSS. Or you can transform the XML via XSLT to pre-generate HTML and CSS for the final result.

Here is an example of pre-generated HTML+CSS from the XML output using XSLT processing.
http://opensoft.homeip.net/tiopf/fpcunit/index64.html

Op 2010-05-30 21:33, Joost van der Sluis het geskryf:

Sigh: http://www.freepascal.org/~joost/wwwroot/testsuiteweb.cgi

The new one looks very nice.... Some pointers on things I noted (hope you don't mind):

* once you view the details of a test run, there is not Back button or Main button to get back to the main screen.

* On the main screen I have no idea what date format is used? Maybe use the ISO 8601 (international date/time) format to stop any possible confusion.

* In your initial post you mentioned that it is tests run each night. Yet all the tests listed on the first page you see are (I think - that's if I am interpreting the date format correctly) 2003-11 and 2003-10. That's rather long ago, and I don't really see the point in keeping such a archive for daily tests runs. Surely the daily results is all you want to see, or a maximum of say last 7 days.

* Failure details. On the main screen it says the one test run caused 33 failures. I click on that row which opens the details. Page 1 or 66!
1) Maybe that could be reduced to some summary/collapsed view first.
2) How do I get a listing of only the 33 tests that failed? I don't want to scroll 66 pages looking for them.

* In the test listed below, which was a test run for 2003-10-31, there is a test result dated 2007-01-28?? See attached image. So somewhere your details query is pulling wrong data, or the data is corrupt.

http://www.freepascal.org/~joost/wwwroot/testsuiteweb.cgi?action=testrun&TestRunID=103

Regards,
- Graeme -

While showing the latest testsuite results by default is a good idea (just like the current testsuite page), it is useful to have older testsuite results as well. Sometimes regressions are not fixed or noticed immediately, and in such a case it can be useful to go back further than 7 days to see where this happened. And as long as the database doesn't become prohibitively large, I don't see a problem with keeping them all.

Jonas

Graeme Geldenhuys wrote

More worrying is that not a single test run listed produced 0 errors. :-/

That's because the testsuite also contains tests for bugs that haven't been fixed yet, and for some features. And when support is added for a new platform, it seldom happens that the implementer keeps fixing bugs until all tests succeed that also succeed on other targets (e.g., one test checks support for gprof, and not everyone is interested in implementing support for that).

Jonas

Op 2010-05-31 10:18, Jonas Maebe het geskryf:

That's because the testsuite also contains tests for bugs that haven't been fixed yet,

OK, that makes sense. Thanks.

Regards,
- Graeme -

I have a really big one for that in my browser. But I'll see if that can be added.

* On the main screen I have no idea what date format is used? Maybe use the ISO 8601 (international date/time) format to stop any possible confusion.

Yeah, and the time-part is also included, so filtering on it will be difficult. Have to fix that.

Click on the date-column header, it will sort on the date in reversed order. But that should indeed be the default.

You can sort on the 'OK' column, but in that case you should filter out the skipped-tests. (Which is currently not possible)

I'll add a 'failed' column. And a way to filter tests.

* In the test listed below, which was a test run for 2003-10-31, there is a test result dated 2007-01-28?? See attached image. So somewhere your details query is pulling wrong data, or the data is corrupt.

Good question. That date is indeed wrong. (should be 8/10/03 according to the 'old' website.)

Joost.

Joost van der Sluis wrote

Sigh: http://www.freepascal.org/~joost/wwwroot/testsuiteweb.cgi

Looks good except for one rendering problem with my Firefox 3.5.9 on Linux, screen resolution 1280*1024.

The grid and other contents don't fit into the browser window and the browser creates scrollbars, both vertical and horizontal. However, there is another pair of scrollbars around the grid which makes it difficult to use. One pair would be enough.

Many columns in the grid are wider than its longest text. Normal HTML table would adjust its width but this is not a HTML table, this is a Javascript component jqGrid. Would it be possible to make it automatically adjust to browser window size?

Here is a screenshot:

http://koti.phnet.fi/juhamann/Lazarus/TestSuiteNew.jpg

I made the window smaller for screenshot but when it is maximized, the scrollbars need to move only little to show everything.

Regards,
Juha

In our previous episode, Joost van der Sluis said:

- reset button that resets all choices back to nothing (default)
- I pressed pg-down to scoll the page, but had to select the grid first. Can you give focus in a webpage? If so, please put focus on the grid ( or whatever drives the scrollers)

Hi

In the buttons the ALL selection (for example in cpu, os or version) selects none.

Screenshot of Safari: http://img338.imageshack.us/f/bildschirmfoto20100531u.png/

Mischi.

Hi, is it possible to call actions this way?:

http://host/cgi-bin/myprog/action1

instead of

http://host/cgi-bin/myprog?action=action1

I thougth that the designed behavior was to call any action by its name like:

http://host/cgi-bin/myprog/action1
http://host/cgi-bin/myprog/action2

But that won't work.

Leonardo M. Ramé
http://leonardorame.blogspot.com

Both should work. The second one should only work if the ActionVar property is set with the name of the query variable.

If the .../myprog/action1 is not working then either there is a new bug in fcl-web or something is not done properly.

What version of fpc/lazarus are you using?

AB

Both from svn trunk.

Leonardo M. Ramé
http://leonardorame.blogspot.com

Nevermind, after upgrading from svn it works as expected now.

Leonardo M. Ramé
http://leonardorame.blogspot.com