 Your new post is loading...
Your new post is loading...
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.
No comment yet.
Sign up to comment
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!
Now, we'll create data flows between multiple components. And, the components we'll build are:
It may not be obvious right now, but the container is essential. Every React component must return a single element. In order for us to display both the Input and the Output components, they need to be inside another component.
Scoop.it!
The absolute best AngularJS tutorial videos on the Internet
Scoop.it!
Agenda * Introduction * WebSocket and Node.js *WebSocket using JSR 356 * Server * Client * Securing WebSocket * Embedded WebSocket * Load Balance WebSocket * Pub/Sub over WebSocket * STOMP over WebSocket * MQTT over WebSocket * REST and SSE * Scalability * Debugging * Production Tips
Scoop.it!
We just rewrote our dashboard using Facebook’s React.js framework and the Flux application architecture. Here are some things we learned along the way.
Scoop.it!
In this post we will have a look at what's included with the starter kit and changing some setup and configuration stuff.
Scoop.it!
Have questions about the strategy for Angular 2.0? This is the place. In the following article I'll explain the major feature areas of Angular 2.0 along with the motivations behind any changes. Following each section, I'll provide you with my own opinions and insights into the design process including important areas where I think the design still needs improvements. Contents: 1. Performance
Scoop.it!
Ember-React adds a new helper {{react}}, which can be used to easily include a react component inside of a handlebars template.
Jan Hesse's insight:
Scoop.it!
React-widgets offers a set UI widgets, built from scratch with React. The suite is based on the excellent work done by Kendo UI Core, and jQuery UI, but built as true components, and not library wrappers. By building each widget entirely in React, it can leavage all of the benefits of the React ecosystem and philosophy .
Scoop.it!
Scoop.it!
Scoop.it!
I recently had an interesting conversation with some very smart colleagues on the topic of UI component reusability on modern web frontend applications. This led me to spend a few hours on a lazy Sunday afternoon clarifying my thoughts on the status quo - and the road ahead - of web frontend architectures. Specifically, I find it interesting how the short-term future seems to somewhat contradict the assumed long-term future.
|
Scoop.it!
Just like Protractor is the end to end test case runner for AngularJS to check for functional regressions, this project is a way check for performance regressions while reusing the same test cases.
Scoop.it!
The real question is: When can we use this new features? Now!? Browser vendors are working hard to implement this and the latest browsers are shipping big parts of the specification already. This website tracks the progress of the latest browsers. You can see a lot of red in this table – that’s why Traceur (compiles ES6 to ES5) comes to the rescue. –> So that your code will work in all modern browsers! In this talk, Erik from the AngularJS Team explains, which additional features of ES6 will be used in Angular 2.0 and how Traceur works. There is also a Chrome extension named “ES6 transpiler based on Traceur” where you can try out your latest ES6 code
Scoop.it!
I decided to write this article since I couldn't find any source that clearly stated how to integrate both projects. I recommend reading it completely (including references) before coding but then again, that’s your call. Before we start I’m assuming that you have some previous node-webkit and SailsJS knowledge so I’ll focus in the basic integration rather than explaining how to work with them.
Scoop.it!
This session will introduce the concept of Reactive Programming as it has developed over the decades and how it addresses the demands of modern architectures by making more efficient use of a relatively small number system threads by not blocking them but by instead providing ways to respond to events. The community project called Reactive Streams will be introduced. Reactive Streams is an engineering cooperative between a number of industry leaders to define and implement a standardized asynchronous contract to build reactive applications that benefit from non-blocking backpressure to provide predictable performance characteristics and low latency for high-volume applications.
Scoop.it!
There is still a ton of boilerplate involved to adhere the Flux architecture, and that’s usually where a library comes along to bring some level of abstraction and convenience. Assuming a prior knowledge of Flux’s inner workings, here’s a comparison of the following Flux libraries that have been developed by the community:
Scoop.it!
Compiled templates for the Browser, and NodeJS Paperclip is a reactive template engine designed for the DOM. It works by compiling templates to document fragments, then clones them whenever they're needed. Paperclip doesn't make any assumptions about your codebase. Easily use paperclip in Backbone, Angular, or Ember-based applications.
Scoop.it!
Writing performant code is absolutely critical. Poorly written JavaScript can significantly slow down and even crash the browser. On mobile devices, it can prematurely drain batteries and contribute to data overages. Performance at the browser level is a major part of user experience which is part of the 10up mission statement. Contents: * Performance
Scoop.it!
A (not so) short introduction on front end pagination. Your application needs to be responsive and try to deliver the best experience for your user, so why are you trying to load all those several thousands of records at once? Specially because most of those records will never be shown to the user, as most likely your user will use some sort of filter/search to find only the records that matters for him at the moment when he access your application.
Scoop.it!
A CSS Framework and a Set of React Components that Implement Google's Material Design
* Buttons * Dialog
Scoop.it!
When writing ReactJS apps, it is enormously helpful to use Facebook's Flux architecture. It truly complements ReactJS' unidirectional data flow model. Facebook's Flux library provides a Dispatcher, and some examples of how to write Actions and Stores. However, there are no helpers for Action & Store creation, and Stores require 3rd part eventing. McFly is a library that provides all 3 components of Flux architecture, using Facebook's Dispatcher, and providing factories for Actions & Stores.
Scoop.it!
Git can support your project not just with version control, but also with collaboration and release management. Understanding how workflow patterns can help or hinder a project will give you the knowledge to evaluate and adapt your project’s Git processes effectively. Throughout this article I will isolate patterns found in common workflows. Knowledge of these will help you find a direction when joining, creating or growing a development team. The pros and cons for certain types of projects or teams will be highlighted within the themes we explore, so that you can pick and choose what might work well for your scenario.
Scoop.it!
React turned out to disappoint me in multiple ways, mainly through a poorly designed API which induces the programmer to createcomplex state machines and to mix multiple concerns in one component. I decided to replace React with the great virtual-dom library, and to build a Reactive MVC alternative heavily based on RxJS. This pattern turned out to be successful and I applied it to other web apps. One of these is a customer project we are glad to say has worked out very well. The combo React/Flux is clearly inspired by Reactive Programming principles, but the API and architecture are an unjustified mix of Interactive and Reactive patterns. Keep reading and I'll explain what this means, and how we can do better.
|
