This page (revision-34) was last changed on 23-Apr-2022 17:06 by Harry Metske

This page was created on 23-Apr-2022 17:06 by Harry Metske

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
34 23-Apr-2022 17:06 32 KB Harry Metske to previous
33 23-Apr-2022 17:06 32 KB Harry Metske to previous | to last
32 23-Apr-2022 17:06 32 KB Harry Metske to previous | to last
31 23-Apr-2022 17:06 32 KB Harry Metske to previous | to last
30 23-Apr-2022 17:06 31 KB Harry Metske to previous | to last
29 23-Apr-2022 17:06 31 KB Harry Metske to previous | to last
28 23-Apr-2022 17:06 31 KB Harry Metske to previous | to last
27 23-Apr-2022 17:06 31 KB Harry Metske to previous | to last
26 23-Apr-2022 17:06 27 KB Harry Metske to previous | to last
25 23-Apr-2022 17:06 27 KB Harry Metske to previous | to last
24 23-Apr-2022 17:06 24 KB Harry Metske to previous | to last 3.0.0-svn-80
23 23-Apr-2022 17:06 19 KB Harry Metske to previous | to last
22 23-Apr-2022 17:06 19 KB Harry Metske to previous | to last
21 23-Apr-2022 17:06 17 KB Harry Metske to previous | to last

Page References

Incoming links Outgoing links
JSPWiki JUnit test performance management
JSPWiki JUnit test performance management

Version management

Difference between version and

At line 6 removed one line
* Use the information created with every run of the tests task, each JUnit test produces an [XML format report|TEST-org.apache.wiki.TextUtilTest.xml] containing response times, see tab
At line 7 added 11 lines
The idea is to use the information created by the JUnit tests.
\\Every time you run an " ant tests", a ''reports'' directory is created containing a test report for each test.
each JUnit test produces an [XML format report|TEST-org.apache.wiki.TextUtilTest.xml] containing response times, errors and failures. (See the "Test Report" tab)
I wrote some code that gathers this information and stores it in an SQL database.
\\It takes two parameters :
* the name of the directory %%small (i.e. "/home/metskem/workspace/JSPWiki/build/tests/reports") %%
* a tag that identifies this test run %%small (i.e. "3.0.0-svn-17") %%
If we gather this information for each JSPWiki level that has significant changes, we could analyze if, and where performance differences occur, and also keep track of a lot of other things.
At line 379 changed one line
mysql> select tag,name,tests,errors,failures from testsuiteresult where errors>0 or failures > 0 group by tag,name order by name,tag;
mysql> select tag,name,tests,errors,failures from testsuiteresult
where errors>0 or failures > 0 group by tag,name order by name,tag;
At line 467 changed one line
mysql> select name,(max(time)-min(time))/avg(time)*100 as percdelta,min(time),max(time) from testsuiteresult where tag='3.0.0-svn-17' or tag='2.8.2-svn-13' group by name order by 2 desc limit 25;
mysql> select name,(max(time)-min(time))/avg(time)*100 as percdelta,min(time),max(time) from testsuiteresult
where tag='3.0.0-svn-17' or tag='2.8.2-svn-13' group by name order by 2 desc limit 25;
This page (revision-34) was last changed on 23-Apr-2022 17:06 by Harry MetskeTop