Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
Let's look at how to test an AngularJS application with Protractor and Karma! Part 1 - In the first part we’ll look at unit tests, which ensure that small, isolated pieces of code (e.g., a unit) behave as expected. 
No comment yet.
Sign up to comment
Scoop.it!
The tips and tricks of using protractor for writing e2e tests with AngularJS
Scoop.it!
My team has been using Protractor for our end to end tests for a couple months now, and the amount of time the test suite takes to finish has grown as we add more tests. So we started looking for ways to speed our tests up. We already have a Selenium grid running with a few browser instances connected to it. Ideally we would like to split the tests out to be ran in parallel among the browser instances in the grid.
Scoop.it!
So what if at work you need to write an automated functional regression for non angular site? If you’re a lucky guy/gal you spend your days dealing with AngularJS and you have convinced your manager to use protractor to write the much needed automated functional suite. Now your manager comes back with a smile on his face asking you to create a new set of tests for this other non angularized web application. Some would be scared, somebody would run, not you! That’s because you know how this thing actually works. You know you can always get the webDriver instance and do some vanilla selenium things. That’s why they call you ‘The Selenium dude’ and sometimes other names which are outside the article’s scope.
Scoop.it!
When integrating node-webkit and angular, I found that I cannot run e2e test in the default chrome browser. It was because node-webkit allows us to use local node packages, which chrome does not support. After playing around these toys for a while, I think I have just figured out how to run e2e test in the context of node-webkit.
Scoop.it!
BDD (Behaviour Driven Development) and TDD ( Test Driven Development) has become cornerstone for modern Javascript app development but adopting these development strategies to SharePoint/Office 365 is not a trivial task. Few weeks back I was intrigued to discover #Protractor, an AngularJS testing framework. With client side MVC/MVVM frameworks getting popular among the developers, AngularJS is the premier framework to develop Office365/SharePoint 2013 apps. Integrating TDD methodologies to app development model will help developers to deliver maintainable, flexible and extensible solutions and interfaces. This presentation includes training videos to 1) Create AngularJS based SharePoint apps 2) Configuring NodeJS project for testing of AngularJS apps 3) Writing test specs using #Jasmine 4) End to end testing using #protractor 5) Links to online resources
Scoop.it!
This article is written for intermediate to advanced developers using AngularJS to build production applications, who would like to reduce some of the pain of testing. It is my hope that feeling secure in testing workflow will enable the reader to practice a TDD workflow and build a more solid app.
Scoop.it!
This is the first episode in a revised series of videos about using Protractor to perform end to end test for AngularJS applications. This episode covers what Protractor is and how to install it into your application. It also provides a simple hello world style demo showing how to configure a project to use protractor and phantomjs to write end to end tests.
Scoop.it!
From
savanne
This talk is split in two parts: unit testing and E2E testing (we'll get to the difference between those in a minute). There will be drinks in between. Each part is roughly: an introduction with a simple test scenario, how to get the tools up and running and then a bunch of tips & tricks for when it gets difficult. You'll need to supply your own drinks if you're reading this at home.
Scoop.it!
Going through the Protractor docs and getting started can still be a daunting task. My goal is to alleviate some of that by sharing my configuration and setup, as well as using the page object pattern for creating an API through which we’ll interact with our web pages. We’ll also be using the jasmine-given library to help clean up our specs.
Scoop.it!
For those of you who are already somewhat familiar with Protractor and Selenium and want to skip right to the end, you might take a look at my Vagrant VM for headless browser testing in Ubuntu, and Chef cookbook for the same. These set up a standalone server that can be used to run end to end tests of AngularJS sites in Chrome, Firefox, or PhantomJS, and address some of the issues that you will run into along the way.
Scoop.it!
A step-by-step presentaion on Protractor End-to-End Testing for AngularJS * Write your tests using Jasmine and WebdriverJS * Searching for elements on the page * Executing events * Maintanable Tests - Best practices to organize your tests * Bonus
Scoop.it!
From
gaslight
When it was announced that Protractor would be replacing the karma runner as THE end to end test framework for AngularJS, I’ll admit, I was a bit sad. While I didn’t have a deep love for the karma runner, it was crazy simple to setup and run, and my initial perusal of the Protractor docs was intimidating. After spending some time with Protractor though, I have come to enjoy using it in the same manner in which I would test a Rails application. Going through the Protractor docs and getting started can still be a daunting task. My goal is to alleviate some of that by sharing my configuration and setup, as well as using the page object pattern for creating an API through which we’ll interact with our web pages. We’ll also be using the jasmine-given library to help clean up our specs.
|
Scoop.it!
If you’ve ever used AngularJS, you’ll know that it has a pretty cool built-in testing setup - Karma for unit testing, and Protractor for end-to-end testing. I love Protractor, but recently ran into issues when trying to use it for a non-Angular project. Here’s how to get it working. If you’ve not encountered end-to-end testing before, you’re in for a treat. Unlike unit testing, which is designed to validate very small components, an end-to-end test can be used to simulate how a user will actually interact with your website. We can make it go to a page, click a link, check the right page gets loaded, give it some input, check it displays the correct output - whatever you want, really. Used in conjunction with other forms of testing, it gives us a really useful look at how our site’s working, and is great for helping us catch any sneaky regressions.
Scoop.it!
In this tip, I would like to describe how to perform E2E (End to End) Test using Protractor for an Angular JS page/site.
Scoop.it!
Tests take actions and make assertions about how the application should respond, but page objects encapsulate the details of how to perform those actions on a page. Protractor Page objects provide a helpful way to organize your end-to-end test code. While your actual tests take actions and make assertions about how your application should respond, page objects encapsulate the details of how to perform those actions on a page.
Scoop.it!
Now I love Behaviour Driven Development I love it for many reasons but my main reason is the way it completes my development process. TDD allows me to test how my code works to validate that the new function has been implemented correctly, to put me in the mindset of writing minimalist and well structured code and to give me confidence I am not breaking any existing code. It is not so great at describing behaviour that the system is supposed to exhibit and if you work with an Agile methodology it is a pretty terrible interface between the developer and the customer.
Scoop.it!
Protractor is an end-to-end test framework for AngularJS. The official version is built on Node.js and Selenium WebDriverJS. There is currently no way to integrate Protractor tests into Test Explorer (that I know of). Thankfully there is Protractor.NET, a .NET port of Protractor built on top of Selenium WebDriver for .NET. It allows us to write Angular UI tests using .NET testing frameworks such as NUnit, and arguably produces more readable tests because there’s no need to use promises.
Scoop.it!
In this blog post I plan to give you a taste of why you’d benefit from using Protractor for your JavaScript tests instead of using Selenium webdriver directly, even if your app has nothing to do with AngularJS. If you peek inside Protractor you’ll see the good old Selenium Web Driver (aka WebDriverJS aka selenium-webdriver). Protractor is essentially a wrapper for the JavaScript Selenium webdriver. Therefore – you get all the capabilities of the webdriver – along with a number of very useful additions.
Scoop.it!
From
medium
By splitting the development of the frontend and the Rails backend we could distribute the work over two development teams and keep the application as a whole very extensible. In my opinion this is the best approach when you split your frontend and backend however not everyone shares that opinion. In this blogpost I will cover why we believe that testing the apps separately and thus mocking the API requests is the way to go.
Scoop.it!
Theory only helps till a point with test automation (as with a lot of development practices). So in this article we're going to follow a practical approach to use Protractor. Following these 3 steps below, will give you sufficient hands-on practice to proceed further with Protractor.
Scoop.it!
Protractor: How to click a select option that has a given value Protractor: How to select a dropdown option to avoid ElementNotVisibleError Protractor: How to avoid UnexpectedAlertOpenError
Scoop.it!
A step-by-step presentaion on Protractor End-to-End Testing for AngularJS
Scoop.it!
In this post, we will see how to setup protractor and run a few E2E tests. First, We are going to scaffold an Angular application using Yeoman and then add Protractor tests to them. Contents: * Understanding Testing & Testing Scope
Scoop.it!
I AM A .NET Developer. Visual Studio is the trench that I dig every day. AngularJS is the primary weapon that I use in the frontend. I want to have Protractor as my first aid kit which doesn’t play nicely without Node.js. But it’s all right, I can tame it! Update: you might be interested in this sample project to dig in quickly. It contains a tiny AngularJS app and a few test cases.
|
Part 2:
http://mherman.org/blog/2015/04/26/testing-angularjs-with-protractor-and-karma-part-2/