The Codeception blog (a BDD testing tool) has a new post on using their Locator class to create more complex tests based on XPath or CSS selectors.

In the latest Codeception 1.1.4 new Locator class was introduced. Basically it should simplify your life in writing complex XPath or CSS locators. Right now it has minimal, yet useful functionality.

The post shows how to combine more than one item for location with either a tag, CSS-based or XPath-based selector. It also shows how to use the "tabindex" method to simulate the movement through a page using the "Tab" key. Finally, there's a quick piece of code showing how to locate an item based on the "href" value. For more information on using Codeception, check out their documentation or the project's main site.

Amir Saied recently posted a handy little tool for the PEAR users out there - a bash script that handles tab completion for you.

Lately I've been playing alot with the PEAR CLI. The one annoying thing I noticed the most was its lack of tab completion that I'm used to from the shell. It turns out that this feature is very easy to add, in the bash at least.

It will finish off the PEAR commands for you and expand out the PEAR package names and discovered channels when it finds a match. You can download the package here.

For those PHPers out there that use the vi editor for their coding travels, Bjarte Karlsen has posted something that might help you out - two configuration files that he uses to work with PHP files in vim.

In a recent chat on #phpc we started discussing vim and talking about vim setups. Surripui posted a blog entry about this asking for setups. I promised that i would post my setup so here it is.

The two files are his:

• .vimrc
• .vim/ftpplugin/php.vim

Between the two of these, the editor is able to correctly handle PHP files, syntax check files and tab complete function names. There's also a mention of using gsnippets for working with code templates.

For those PHPers out there that use the vi editor for their coding travels, Bjarte Karlsen has posted something that might help you out - two configuration files that he uses to work with PHP files in vim.

In a recent chat on #phpc we started discussing vim and talking about vim setups. Surripui posted a blog entry about this asking for setups. I promised that i would post my setup so here it is.

The two files are his:

• .vimrc
• .vim/ftpplugin/php.vim

Between the two of these, the editor is able to correctly handle PHP files, syntax check files and tab complete function names. There's also a mention of using gsnippets for working with code templates.