Category: TikiTests

Hi:

I've set up an R script (.Rmd: with R markdown to be run through Knitr) to check the application of all Tiki Profiles (the ones available in the Profiles Wizard since Tiki12, at least) on several tiki branches on your own localhost, to search for error messages, and aggregate that information for easy monitoring. It can be extended to send an email when regressions show up, etc.
I developed that over the weekend from home, and even if in beta stage, it currently works.
See: https://github.com/xavidp/TikiProfilesTester

However, I cloned the git repo at work, where we are behind a proxy, and console.php cannot apply profiles from there through the commandline. Through the GUI I always have to add the proxy info to Tiki first in order to be able to list profiles and apply them , etc.

{CODE()}
root@pentinella:/var/www/html/trunk# php console.php p:a Voting_System
Profile not found.
root@pentinella:/var/www/html/trunk#
{CODE}

proxy info seem to be defined at ./trunk/lib/tikilib.php (line 185 onwards)

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

At https://tiki.org/Demo
The Demo instances for 16x and 9x are no longer available.

16x shows Internal Error 500
9x shows url no longer available.

The module tiki_tests does not seem to have a purpose. When you enable feature_tikitests you can add the module. But the module does nothing except for displaying to links, /tiki_tests/tiki-tests_list.php and tiki_tests/tiki-tests_record.php.

Both do nothing. If you click on them, nothing happens. If I copy the link targets and open them in a new browser tab, I get the advertising of my ISP (which is the protective default behaviour if a file cannot be accesses. But FTP shows that the path and filename are correct, so I guess those files are either protected or lack the necessary flags so PHP won't touch them.

Because of the label "test" I would assume that is on purpose so admins do no harm to their installation, but if that's case I would suggest a meaningful error message instead. Or some way of circumvention.

Suggested message if PHP5 is not detected:

^
__TikiWiki 3.0 requires PHP 5.x__

Your currently detected PHP version is: (versionnumber)

Please contact your web host to request an upgrade. If there is no way you can have PHP 5.x, please use Tiki 2.x instead. Some features in Tiki 2.x, such as profiles and TikiTests require PHP5, but all the other hundreds of features work perfectly with PHP 4.1+

For more information:
http://www.gophp5.org/
http://tikiwiki.org/
^



(9:59:42 AM) marclaporte: turning on TikiTests crashed by site :
(9:59:42 AM) marclaporte: Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /home/profiles/public_html/tiki_tests/tikitestslib.php on line 59
(9:59:53 AM) marclaporte: I suspect because I don't have php5
(10:00:01 AM) marclaporte: http://profiles.tikiwiki.org/