Go gaga over Machine Learning

Considering how the testing world is now automating on both angular and polymer here is an excellent post about the future of web development: About a year ago in May 2013, Google launched  Polymer.js . So here we are, a year later. And the question is: Is it yet ready for prime time? Is it yet possible to create a production ready application using Polymer web development techniques? To answer this question, I took Polymer out for a test drive to develop a web application and to see how well it would behave. This article is about that experience and what I learned in the process. Polymer.js: The Concept Before we get into our Polymer tutorial, let’s first define Polymer.js, not for what it claims to be, but for what it actually is. When you begin to check out Polymer, you can’t help but immediately be intrigued by its self-professed unique world view. Polymer purports itself as taking a sort of back-to-nature approach that “puts elements back at the center of web d...

You didn't think it could be done, did you? Well, let me prove you wrong!  First, some terms: AngularJS : An MVC framework for JavaScript, allowing you to write web apps without relying on JQuery. Protractor : A test harness for Angular apps. Sauce Labs : A company providing cloud services to help you run E2E testing on your web app in any environment combination. Node.js : Package manager for JavaScript.  You’ll need this for installing all the dependencies to get this tool set working. Gulp : A build manager and mundane-task automator.  Competitor with the older, well-entrenched  Grunt , but gaining popularity by the hour.  Uses JavaScript syntax, but could theoretically be used as a Makefile or shell script replacement. Here is how: http://sauceio.com/index.php/2015/03/repost-angular-protractor-sauce-connect-launched-from-gulp-all-behind-a-corporate-firewall/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+SauceLabs+%28Sauc...

Here is a generic structure of a test automation tool like Selenium/Protractor/Capybara

"GC overhead limit exceeded" is what you see when you are trying to import a new project or when Eclipse just runs out of memory! Solution: Allocate more memory to your Eclipse instance.  How?: Locate the eclipse.ini file in your Eclipse's installation directory. The content would be something similar to the following: Change these: Restart your eclipse :)

If you are well versed with selenium then before going through the demo have a look at these slides: http://ramonvictor.github.io/protractor/slides/#/ Now straight to the demo: Prerequisites: Download and install Nodej Go to the  NodeJS home page Click install to download the .msi installer package Run it and follow the instrucitons, you now have NPM (node package manager) and Node.js installed Open the Node.js command prompt and type in the following command to install protractor globally. npm install –g protractor If you get the error enoent read this: http://go-gaga-over-testing.blogspot.com.au/2014/09/node-grunt-error-enoent-stat-roaming-npm.html?_sm_au_=iHV1HtWvt61rRqWs You are now ready for a Proof of Concept: Demo test application and protractor tests. Setup      git clone https://github.com/juliemr/protractor-demo.git  cd protractor-demo  npm install To run Get a selenium server running at localhost:4444.  j...