I'm upgrading my script from Watir to Watir-Webdriver and I'm wondering how to take advantage of headless-browser testing and grid testing. I've done some research into it but my sources don't seem substantiated, and tutorials are very thin on the ground right now, so has anyone done headless browsing or grid testing? How did you achieve it, and what did you learn that you wish you knew when you started?
I'm working on XP and MS Server '03 VM machines. If I make progress on this I'll try to keep the question updated with information.
I have written a post about how to run Watir-WebDriver heads headlessly using real web browsers in the cloud using Amazon EC2.
See: http://watirmelon.com/2011/08/29/running-your-watir-webdriver-tests-in-the-cloud-for-free/
Have a look at Watir grid https://github.com/90kts/watirgrid might be what you are after.
Related
I'm using Pupeeteer to automate some task on a website but there's Google's image captcha problem it appears after sometime.
I tried many things but can't solve this problem. Tried using chrome extension but puppeteer doesn't seem to work with that.
So I just wanna know is it worth using 'deathbycaptcha' service? Its paid but it looks like it will do the job.
We are looking to replace our Selenium approach to automated web data collection and have been recommended Puppeteer or Chromeless.
One of the things I like is the ability to go headless with chrome running on AWS lambda. That reason was sold as the main reason for going with Chromeless or Puppeteer. However, I see posts online indicating that the same can be done with Selenium. If that is true, what over advantages do Chromeless and Puppeteer offer over Selenium ?
We are going to be using NodeJS
Having used both Selenium and Puppeteer, these would be my observations as to why it's currently being recommended so highly:
Puppeteer is really easy to configure and execute. No setting specific drivers required. Just write your test scripts, point node towards your scripts and watch it go. Everything even runs in parallel!
It's a zero setup framework in that it comes bundled with the version of Chromium which it runs best with.
Another benefit is speed. Puppeteer is really fast since it uses headless Chrome.
It integrates very nicely with other popular test frameworks such as jest and mocha.
Using Puppeteers API is really straightforward. Everything is simple to write, easy to understand and basically allows for simple user interactions to be automated using a single line of code.
It's really easy to debug your automation scripts. Simply set headless to false and turn slowMo up from 0 to, say, 250 and you can easily see what's going on and fix any problems you may have.
It's easy to pick up and use no matter what your previous experience levels: on the team I'm working on, everyone (even those with no real automation test script writing experience) has found working with Puppeteer a really nice and relaxed experience. Everyone is getting the grasp of it within a few minutes of basic research and getting scripts running quickly and with no hassle or stress.
It should be noted that Selenium does do everything that Puppeteer does (and vice versa) but that's not the point of Puppeteer. Puppeteer allows for a team to build a large library of automation scripts very quickly using an easy to use API and get tests running now rather than having to deal with building ultra-robust test frameworks which work cross browser and / or cross device.
If you really must have cross browser testing then Selenium or perhaps InternJS (a personal favourite of mine) are still the choices to make.
Puppeteer only supports executing tests on Chrome but, at the end of the day, it's much better to have a lot of tests running (even if it's just on Chrome) as opposed to having none.
I am currently working on a Three.js based WebGL project and I need to get a screenshot of a given model quickly when needed.
I have implemented some JavaScript code that will render a 3D model then return a picture of it. But the problem is that the JavaScript code runs at client side, but I need it to make it server-side, so I can get the picture by a URL (such as example.com/get-screenshot.php?id=2) and serve it to my users.
I am wondering if there is a mechanism that will automatically trigger the job and return what I need. Besides the server that hosts my site, which is Azure website, I also have access to an Azure virtual machine with Windows Server or Ubuntu Server installed; I don't know if it helps.
Thanks in advance.
Your WebGL code needs a GPU to run; Amazon recently introduced a GPU instance to EC2, but Azure currently does not have that option.
The next release of the Verold platform gives you a full Three.js editor with hosting options for your web 3D desktop and mobile apps. You will be able to implement this usecase on our platform. Send an email to info#verold.com for details.
Ross
You can try use phantomjs with grunt and node to genarate those images.
phantomjs can simulate a full stack browser enironment, and can run on server side.
We've just started to used bugzilla and I found the web interface quite slow and not user-friendly.
I'm wondering if anyone have a suggestion for a client desktop or a browser add-on running under windows.
I found the following page: https://wiki.mozilla.org/Bugzilla:Addons
Which one of these clients (or any other) is the best ? Any other suggestions ?
I already tried Deskzilla Lite, which seem pretty good. However, there is a lot of field (edit bug) that we don't use (i.e. hardware, os, url, depends on, etc). Is there a desktop client that allow to remove and customize the field used in the bug entry form? On this one, please do not answer I can customize the bugzilla templates, we don't want to use the web interface anyway.
Well it depends on your Bugzilla Version. Since I updated to 4.0 I've got no alternative to Deskzilla since MyZilla is not running anymore. LiveProject looks pretty neat but I never tested it, so... Deskzilla lite. :/
Hello recently I've been a bit curious and wanted to make a browser. I'd like to use an existing engine though such as Gecko or Webkit. Are there any resources on the web for how to get started and any examples? Language choice doesn't really matter(but no VB please. That was the only example code I found)
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. This site contains design documents, architecture overviews, testing information, and more to help you learn to build and work with the Chromium source code.
Or study some applications using Webkit for example. Chances are, these projects are not as complex as chromium.
I'd recommend you build a browser in Java with Swing or SWT. They have all the components you'll need, so you need to put them together and start figuring out the tougher problems. The documentation is good, and you may even find tutorials that get you most of the way there.
I recently downloaded the code for Firefox or Chrome, and this seems like a much more difficult place to start. There's lots of setup and overhead to get a build working on your machine compared with a Java app.