Sparrow project highlights


It seems Sparrow project is getting stabilized with version 0.1.*, I don't think I am going to change API radically in the future ... The same for Outthentic which accordingly hit version 0.1.* as well.

So to sum things up:

Interlude 2, in which I write more about the release pipeline

The author tests in my module publication pipeline are only one part of the task. The other tasks are actually running the checks, making sure that my public Github repositories are updated with each release and actually pushing the distribution file out onto CPAN. Of course, I have these steps automated.

Selenium Webdriver using Perl

use Selenium::Remote::Driver;

#Input capabilities
my $extraCaps = {
"browser" => "IE",
"browser_version" => "8.0",
"os" => "Windows",
"os_version" => "7",
"browserstack.debug" => "true"

my $login = "USERNAME";
my $key = "ACCESS_KEY";
my $host = "$login:$key\";

my $driver = new Selenium::Remote::Driver('remote_server_addr' => $host,
'port' => '80', 'extra_capabilities' => $extraCaps);
print $driver->get_title();

Whenever screening automation turned the newest tendency, there are various takers for this. Currently, most of the software development firms favor assessment automated and information tests is gradually becoming a factor of prior.

Though there are many testing tools offered, Selenium leads the group using many consumers throughout the world. Selenium webdriver training is free and open source rendering it fiscally viable. Next, it could be run-on any platform and compatible with any visitor. Using all these attributes, more and more application designers and evaluators are getting regarding Selenium training instead of every other screening automatic resource.

The Secret Life of Acronyms

Years ago I wondered intensely about why some acronyms jarred, and not just government-issue ones either. Let me explain my conclusions.

I'm posting this now because of the push to rename the just-finished QA Hackathon, which personally I feel was marvellous value-for-money.

Why I try to avoid Perl's punctuation variables

Over on Perlmonks I wrote that you should probably use this:

say join '', @array[2,4];

Instead of this:

local $" = '';
say "@array[2,4]";

And my reasoning being:

Why is that better? Because nobody knows what $" is, but everyone knows what join() is. Always write your software to be as readable as possible :)

I received a couple of upset replies along the lines of "Perl devs should be allowed to write Perl!" While I generally agree with that sentiment -- I had no problem with the array slice, for example -- I think the replies came, in part, because I had answered too quickly. I clarified what I meant, but I thought I should explain it here, too, because too many people reach for those punctuation variables.

Brutally Solving a Logic Puzzle with Perl 6

Every now and then, I enjoy solving logic puzzles (or attempting to). Recently I came across this one:

|    |  3 | 17 |
|  5 |    |    |
| 13 |    |  7 |

There are five prime numbers in a 3x3 grid, and the goal is to fill in the empty cells with four other prime numbers, so that the sum of every row, every column, and both diagonals is also a prime number, less than 100. Each number can only be used once, and this applies to the numbers in the grid as well as to all the sums. Lastly, the sum of all these numbers must be a prime number as well (greater than 100, obviously).

I took me quite a while to find a solution — but when I finally did, I had not one, but (at least) two solutions. The puzzle description didn’t mention anything about multiple solutions, so I thought I made a mistake along the way. However, having triple-checked all the math, I couldn’t find any errors. I decided it was time to use the force (I couldn’t miss the opportunity to use this phrase, considering the date when I’m posting this) — namely, the brute force.

Strawberry Perl released

Strawberry Perl is available at

More details in Release Notes:

I would like to thank our sponsor Enlightened Perl Organisation for resources provided to our project.

Check your licences: The FSF has a new physical address

Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

I can't actually say when they moved, but Petr Pisar has kindly informed me it is so, and he's fastidious about such things.

And, yes, here in Australia we really do spell licence as, er ... well, licence.

About is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is hosted by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.