Richard Jedlička

  • Content count

  • Joined

  • Last visited

  • Days Won


Richard Jedlička last won the day on December 10 2016

Richard Jedlička had the most liked content!

Community Reputation

76 Excellent

About Richard Jedlička

  • Rank
    Jr. Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Czech Republic

Recent Profile Visitors

2,219 profile views
  1. It's done. I've considered the options and with @LostKobrakai's advice added beforeCmd config option allowing to run specified command after PW installation but before test suite execution. See more Currently on master branch only.
  2. I'd would like to implement the before_script option, but there are some things I'm not sure about. Your help is appreciated, see the issue:
  3. Hi, version 1.0.0 is released. The main changes are: project's name is changed to Tense (Test ENvironment Setup & Execution) Symfony/Console is used for colored output and arguments parsing config file uses YAML instead of JSON tense init command can be used for config file initialization waitAfterTests option renamed to pause
  4. Or instead of adding an option, you can, as I've written always check the name on page save if it corresponds to the title (according to settings) as a fallback to javascript.
  5. It would be great You, I can handle it myself, but the module handles also the conflicting page names, which is not trivial code.
  6. As I see it's used only when the page has no settings tab, which is not my case. I've tried changing the title using API but it didn't work.
  7. Hi @adrian, I've started to use you module, it is great when editing in admin, but it is useless when I change the title using the API. According to you code it uses javascript for it, which is good that is reflects the changes immediately. But could you consider checking the name on page save if it matches the title and change it if not (of course respecting the module settings)?
  8. You have probably a typo in field migration example $this->insertIntoTemplate('event', 'date', $f->name); should be $this->insertIntoTemplate('event', $f->name, 'date');
  9. Thank for your reply. One more question. What is the letter after the migration filename?
  10. Hi @LostKobrakai, I'm trying to use Migrations module, but I'm not sure how to start. What is you workflow when creating a migration? How do you test it before it is complete. Consider I have quite complex migration which adds a field (page reference type) and a tree of pages which references to. I think I'm not able to create the migration without bugs in one go. I would like to try it during development. The workflow which comes to my mind is I make a change, backup database, run migration, check admin changes, restore database, add other change to migration etc. Yes I should update the downgrade function simultaneously and instead of restoring the database restore the migration, but there is still high possibility of bugs during restore. What do you recommend? Thanks
  11. I've found the problem. There is a method getCoreBranches which returns the branches already loaded in session if the second parameter is false. But it is never called with the second parameter set to true: So I changed temporarily the call and it works now. But I gues it should be enough to relogin.
  12. Something must be wrong. I even deleted the cache folder, but nothing changed.
  13. Yeah, it is weird. I have a latest version (0.0.7) of a module but it doesn't offer me a PW version from processwire/processwire repo. Only devns branch from old repo which is version 3.0.33, i installed it and realized it later.
  14. Finally I've found out how to support PW 2.x and PW 3.x with one codebase. So here is a new version 1.1.2 compatible with PW 2.5+. I updated the tests as well, turned the script which runs tests against multiple versions of ProcessWire into standalone tool PW-Test.
  15. Tense 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: tense run For detailed instructions see Github page: 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.