Two weeks ago I was invited to speak on the 121 Test Automation Day Conference Berlin about one of my most favourite topics – Software Quality in Web Projects.
It really was a nice audience and I received very good feedback on it. The slides can be found here: https://slides.com/carstenwindler/continuous-testing-and-beyond#/.
Looking forward to my next talk, wherever that will be 🙂
The waiting for PhantomJS 2.5 seems to have come to an end – unfortunately, it will most likely never be released.
According to a statement of Vitaly Slobodin, the current maintainer of PhantomJS, the further development has been stopped. This is particular sad as version 2.5 beta has been released already and a lot of effort has been put into this release.
But why? As reason, Vitaly states the release of Headless Chrome with Google Chrome 59. Fair enough, a few developers can’t compete with Google at all.
As a matter of fact, PhantomJS was pretty unique for quite some time. An amazing project which established headless browser testing on wide areas, so it has been a fundamental contribution to the testing world.
I think the actual, long anticipated release of Headless Chrome was just the final the straw that broke the camels back. Since the infamous ticket 546953 it was totally clear that it was worked on it, also conference talks of the developers talking about the technical background came up, so it was just a matter of time since it would show up. It was not really a surprise. So why not stop development of PhantomJS even earlier?
It pretty much feels to me that one of the main potential drawbacks of the Open Source Software movement was the main reason: only a few developers have to deal with the many bug reports and feature request of thousands of users which are all happy to use the tool day by day, but are not willing to contribute or even pay for it. If you can’t make a living from your Open Source project, there will be that one day when it is simply enough. Even the biggest enthusiasts have to pay their bills.
To be honest, over the past years I have been in some sort of Love / Hate relationship with PhantomJS. The many bugs (which are totally normal to happen) combined with the very slow release cycles (which were absolutely annoying, but again understandable) ended up in many, many hours or even days of looking for reasons why that particular test failed only in PhantomJS (e.g. my previous blog post File uploads not working with PhantomJS). On the other hand, I can only express my deepest respect and thankfulness to the developers involved. And yes, I am also one of the thousands of users who used PhantomJS without any contribution.
What will Chrome Headless bring us? I think chances are pretty good that it will be the new standard for Headless testing soon, and this is by no means an offense to the PhantomJS project. There will be a new ecosystem around it, which will make integration of Chrome Headless as easy as for PhantomJS.
On the other hand, we will loose an independent player on the field, and once again Google will gain more power.
However, being responsible for the future wellbeing of the projects I maintain as it is my profession, I will have to adapt to this change. I will have to change the project stacks in order to replace PhantomJS with Headless Chrome very soon. At least not taking it into consideration would be a huge mistake. Still the ecosystem around Chrome Headless as to evolve, but I actually have no doubt it will.
Luckily PhantomJS implemented the Remote WebDriver Wire protocol since version 1.8 (speaking of GhostDriver here, another project from the PhantomJS ecosystem which I didn’t even mention yet), so those projects which were not relying on the PhantomJS API will be lucky.
Just recently, ChromeDriver 2.30 which officially supports Chrome 59 has been released – one concern less!
So far no new maintainer of PhantomJS has been found. The burden might be too heavy.
Just a quick one today: when you struggle with writing Acceptance Tests for file uploads using PhantomJS (will version 2.5 ever come out? *sigh*), here are two possible solutions for you.
The first issue might be that the input field is hidden for obvious reasons. Luckily we can solve this issue without making your designer cry (and we don’t want to do this, don’t we?) by just tweaking the CSS using JavaScript.
In my case, the input field was hidden by using a very low opacity value, so I set it to 1 just before attaching the actual file:
// PhantomJS 2.1 workaround #1:
// Make input[type=file] visible
$I->executeJS(
'document.getElementById(\'input-field\').' .
'setAttribute(\'style\',\'opacity:1\');'
);
$I->attachFile('#input-field', 'test.jpg');
If this solves your problem – great! If not, I got one more.
While the first issue is somewhat understandable … well, maybe …, anyway, I found the second one just by good old trial-and-error: PhantomJS doesn’t like multiple uploads!
Now we don’t want to remove the possibility to upload multiple files just to please PhantomJS, so let’s do another tweak:
// Phantomjs 2.1 workaround #2: // Don't use multiple uploads $I->executeJS( 'document.getElementById(\'input-field\').' . 'removeAttribute(\'multiple\');' );
Of course we can’t test multiple uploads that way, which is a bit sad, but right now I’m afraid we have to live with that.
If you found these two little tips helpful, or if you have another nasty PhantomJS workaround at hand, please drop a comment below!