14 posts in this topic
Recently Browsing 0 members
No registered users viewing this page.
By Richard Jedlička
Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.
See example or see usage in a real project.
How to use?
1. Install it:
composer global require uiii/tense 2. Create tense.yml config:
tense init 3. Run it:
For detailed instructions see Github page: https://github.com/uiii/tense
This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
I'm using GitLab CI for continuous integration right now. Other people might use something like Travis CI. For the frontend part things are pretty easy:
image: node:6.10.3 cache: paths: - node_modules/ build: script: - npm install - node_modules/.bin/gulp build Now I could extend my setup to run tests or whatever I want. It just works.
In this post I'm not interested into finding out how I could go about testing and stuff. I just want to know how I could accomplish the equivalent to the above setup task for ProcessWire. It doesn't seem to be too easy to me since the installation process is running in the browser asking you a lot of stuff. How could I go about it using the CLI?
That's what I currently have:
git clone firstname.lastname@example.org:processwire/processwire.git cd processwire mv site-blank site rm .gitignore git submodule add -b develop email@example.com:path/to/MyModule.git site/modules/MyModule From here on I'm stuck.
The only possible solution I see is maintaining a super repository including a database dump that has it's module dependencies defined in a .gitmodules file. This could then be installed using:
git clone --recursive git@... Once that's completed all that needs to be done would be to create the database using the dump.
Probably that's a pretty solid solution but it adds the overhead of having to maintain an additional repository + database dump. I'm trying to find an alternative that's using the original processwire repository. That way I could just rerun my build once a new version get's merged into master and see if everything would be still working as well.
I'm looking forward to your replies. Thanks!
Hi fellow Processwirers (?),
I was wondering if anyone here uses PHPStorm in conjunction with PhpUnit?
In particular, I'm trying to get it to work with Processwire so I can incorporate the Pages & other intrinsic Processwire objects into the testing.
Any example or real life configuration examples would be most welcome.
Thanks in advance.
I'm a newbie and I'm trying to learn more about Processwire so I've setup XDebug + PHPStorm to get some real time debugging happening.
I've noticed that no matter where i put a breakpoint in any of my php modules, it seems to return the following error.
Error: __debuginfo() must return an array (line 55 of /Users/FrancisChung/site/Test/templates/head.inc)
This error message was shown because you are logged in as a Superuser. Error has been logged.
I was wondering if fellow Processwire users have a similar setup, and was successful in getting debugging going.
I've also read this forum post:
I'm also aware there's an issue with XDebug and Processwire: