I’m still setting up for BDD testing. All the basics are already there (see previous post).
I spoke quickly about setting up WPBrowser: WordPress specific set of extensions for Codeception. Here’s what to do (from the Readme):
The added bonus, if you’re using PhpStorm is that you will also get the related auto-complete package. And there’s plenty of functions that really speed things up.
Next for me was setting up MailCatcher
MailCatcher runs a super simple SMTP server which catches any message sent to it to display in a web interface
You need mailcatcher if you’re testing sending email out from the site. Here’s what I used:
\curl -sSL https://get.rvm.io | bash
source /etc/profile.d/rvm.sh
rvm install 2.2.2
rvm default@mailcatcher --create do gem install mailcatcher
rvm wrapper default@mailcatcher --no-prefix mailcatcher catchmail
You also need to add the following in /etc/php5/apache2/php.ini:
sendmail_path = /usr/local/rvm/wrappers/default/catchmail -f some@from.address #
(and restart apache after that)
Next you need to install the codeception mailcatcher module using composer
"captbaritone/mailcatcher-codeception-module": "1.*"
And set the configuration inacceptance.suite.yml
You might get by with only that, but I had trouble with mail being routed through special plugins we use at work, so I had to install the ‘mailcatcher’ plugin
After that it was smooth testing …
I started working on automating testing ( BDD style ) a few weeks ago, and it took me a while to go over the available tools and options. The obvious starting point was cucumber. Which then led me to Behat, which then took me to Codeception.
When someone tells you it works out of the box, you should always take that with a pinch of salt. Of course, if you follow the quickstart page, it will take you through the different steps that you would take to unwrap the shrink around the box, open it up, take the protective foam bar out, … You get my drift.
Turns out you would need a few more ingredients before you could start testing. Here’s what I needed:
Of course if you’re using the PhpBrowser for testing (no Javascript with that sorry), Â you could get started faster. So no nagging please.
And, if you’re like me, going to test WordPress sites themes and plugins, you might find the WPBrowser very useful.
Here’s a list of the steps I took locally on an Ubuntu 15.10 machine (that already had Google Chrome installed)
If you didn’t have Chrome (or installing on a server):
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb dpkg -i google-chrome-stable_current_amd64.deb apt-get install -f # dirty shortcut to get apt to install dependencies for you! wget http://goo.gl/rQhaxb -O /opt/selenium-server-standalone.jar sudo apt-get install xvfb alias run_selenium="DISPLAY=:1 xvfb-run java -jar /opt/selenium-server-standalone.jar" wget -N http://chromedriver.storage.googleapis.com/2.20/chromedriver_linux64.zip unzip chromedriver_linux64.zip chmod +x chromedriver sudo mv -f chromedriver /usr/local/share/chromedriver sudo ln -s /usr/local/share/chromedriver /usr/local/bin/chromedriver sudo ln -s /usr/local/share/chromedriver /usr/bin/chromedriver
A couple of parting notes:
[morris type=”Donut” element=”donut-div” xkey=”” ykey=”” labels=””] {label: “Download Sales”, value: 12}, {label: “In-Store Sales”, value: 30}, {label: “Mail-Order Sales”, value: 20} [/morris]
[morris type=”Bar” element=”bar-div” xkey=”y” ykeys=”‘a’, ‘b'” labels=”‘Series A’, ‘Series B'”]{ y: ‘2006’, a: 100, b: 90 }, { y: ‘2007’, a: 75, b: 65 }, { y: ‘2008’, a: 50, b: 40 }, { y: ‘2009’, a: 75, b: 65 }, { y: ‘2010’, a: 50, b: 40 }, { y: ‘2011’, a: 75, b: 65 }, { y: ‘2012’, a: 100, b: 90 }[/morris]
[morris type=”Line” element=”line-div” xkey=”y” ykeys=”‘a’, ‘b'” labels=”‘Series A’, ‘Series B'”]{ y: ‘2006’, a: 100, b: 90 }, { y: ‘2007’, a: 75, b: 65 }, { y: ‘2008’, a: 50, b: 40 }, { y: ‘2009’, a: 75, b: 65 }, { y: ‘2010’, a: 50, b: 40 }, { y: ‘2011’, a: 75, b: 65 }, { y: ‘2012’, a: 100, b: 90 }[/morris]
[morris type=”Area” element=”area-div” xkey=”y” ykeys=”‘a’, ‘b'” labels=”‘Series A’, ‘Series B'”]{ y: ‘2006’, a: 100, b: 90 }, { y: ‘2007’, a: 75, b: 65 }, { y: ‘2008’, a: 50, b: 40 }, { y: ‘2009’, a: 75, b: 65 }, { y: ‘2010’, a: 50, b: 40 }, { y: ‘2011’, a: 75, b: 65 }, { y: ‘2012’, a: 100, b: 90 }[/morris]
One of our customers was experiencing very high load today. Checking his logs showed too many IPs trying to hack at the wp-admin.php login page. Here’s a snapshot of what I saw:
# tail -f /var/www/vhosts/*/statistics/logs/*_log
==> /var/www/vhosts/example.com/statistics/logs/access_log <==
10.0.1.169 - - [03/Oct/2013:05:50:17 -0500] "POST /wp-login.php HTTP/1.0" 200 4479 "example.com/wp-login.php" "Mozilla/5.0 (Windows NT 6.1; rv:19.0) Gecko/20100101 Firefox/19.0"
10.1.1.206 - - [03/Oct/2013:05:50:21 -0500] "POST /wp-login.php HTTP/1.0" 200 4479 "example.com/wp-login.php" "Mozilla/5.0 (Windows NT 6.1; rv:19.0) Gecko/20100101 Firefox/19.0"
10.0.2.197 - - [03/Oct/2013:05:50:23 -0500] "POST /wp-login.php HTTP/1.0" 200 4479 "example.com/wp-login.php" "Mozilla/5.0 (Windows NT 6.1; rv:19.0) Gecko/20100101 Firefox/19.0"
10.0.55.117 - - [03/Oct/2013:05:50:24 -0500] "POST /wp-login.php HTTP/1.0" 200 4479 "example.com/wp-login.php" "Mozilla/5.0 (Windows NT 6.1; rv:19.0) Gecko/20100101 Firefox/19.0"
That went on forever!
The first thing I did was use the fail2ban filter I found here.
Unfortunately this did not work as the attack was widely distributed. Fail2ban is ineffective against such attacks. So the next thing I tried was password protect that page. I added a few lines in the apache configuration for that VirtualHost for basic authentication. That worked and the load instantly dropped to normal.
In case the files got lost or misplaced here's the gist:
There are so many of them!
Latest plugin installed is WPGPlus. Let’s see if it actually posts the new blog…
not working so far!
I installed the official Facebook Plugin and set up the app per https://developers.facebook.com/apps. Not sure if it’s working yet. the comments and like buttons are working
Bookmark this category
How it’s done. I started out with a bash function as described earlier. The function code is below:
function blog() { echo "$2" | mail -s "$1" address@example.com; }
Then I noticed I would need more freedom to write longer text, without leaving the shell. So here goes the “blog” bash script. I’m using the postie wordpress plugin on the server side, so things are a bit more manageable. I may add more to this later if I get time.
#!/bin/bash
if [ -n "$2" ]; then
BODY=$2
else
vi tmpfile; BODY=`cat tmpfile`; rm tmpfile
fi
if [ -n "$1" ]; then
SUBJECT=$1
else
echo -n "Subject:"; read SUBJECT
fi
echo "$BODY" | mail -s "$SUBJECT" address@example.com