Parashuram N axemclion

## article.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              2 stars
            
          
                axemclion
                / article.md
            
            
              Last active
              January 4, 2016 12:19
            
              
                Article for HTML5rocks.com
              
          
    Automating Web Rendering Performance Measurement

Ensuring that your web pages are delivered to the user as quickly as possible, results in a great user experience. However, users spend more time interacting with the page than waiting for it to download. This makes the smoothness and responsiveness of the site even more critical. Janky page scrolls, disjointed animations or delayed visual cues in a page are just as bad as a site that takes time to load.
Most modern web browsers have tools that can help determine the various performance bottlenecks during typical user interactions. Excellent tutorials have also been written about performance workflows. Despite this, rapid development and deploy cycles make it hard to implement regular performance audits. Tools like [PageSpeed Insights](http://updates.html5rocks.com/201

  
## untitled.png

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                axemclion
                / untitled.png
            
            
              Last active
              January 2, 2016 01:09
            
          
## gist:6357083
npm = require('npm')
npm.load({
  argv: {
		remain: [],
		cooked: ['test'],
		original: ['test']
	}
}, function() {
	npm.commands.test([], function() {});
});

## Gruntfile.js
  grunt.registerMultiTask('publish', 'Publish the latest version of this plugin', function() {
		var done = this.async(),
			me = this,
			npm = require('npm');
		npm.load({}, function(err) {
			npm.registry.adduser(me.data.username, me.data.password, me.data.email, function(err) {
				if (err) {
					console.log(err);
					done(false);
				} else {

## index.android.js
'use strict';

var React = require('react-native');
var {
    AppRegistry,
    StyleSheet,
    Text,
    View,
    NativeModules,
    TouchableHighlight,

## A sample Grunt Task file using Grunt-SauceLabs-QUnit
/* global module:false */
module.exports = function(grunt){
	grunt.initConfig({
		pkg: '<json:package.json>',
		meta: {
			banner: '/*! <%= pkg.name %> */'
		},
		server: {
			base: '.',
			port: 9999

## jquery-indexeddb-test.html
<html>
    <head>
        <title>Sample title</title>
    </head>
    <body>
        <h3><a href = "javascript:schema()">Create Schema - Run this first</a></h3>
        <h3><a href = "javascript:list()">List data in DB</a></h3>
        <h1>Test cases</h1>
        <ul>
            <li>

## filtereffects.js
 var secret = "7e58cceaf";

            var params = {
            	api_key: "c92a196a2",
            	app_version: "1.0",
            	backgroundcolor: "",
            	calltype: "render",
            	cellheight: 300,
            	cellwidth: 300,
            	cols: 1,

## QueuedUnit.js
/**
 * Ideally unit tests should be independent, but there are some cases where you really want those tests to be executed one after the other
 * Here is some code that does exactly that - a wrapper on top of QUnit.
 *
 *  Usage
 *  Instead of asyncTest, call queuedAsyncTest (same params)
 *  Instead of module(), call queuedModule
 *  After a test is over and the next test has to run, call nextTest()
 */
(function(window, console, undefined){

## index.js
var perfjankie = require('perfjankie');
var browserperf = require('perfjankie/node_modules/browser-perf');
perfjankie({
    'url': 'http://localhost:8080',
    'browsers': [{
        'browserName': 'chrome'
    }],
    'selenium': 'http://localhost:9515',
    'couch': {
        'server': 'http://localhost:5984',
	npm = require('npm')
	npm.load({
	argv: {
	remain: [],
	cooked: ['test'],
	original: ['test']
	}
	}, function() {
	npm.commands.test([], function() {});
	});
	grunt.registerMultiTask('publish', 'Publish the latest version of this plugin', function() {
	var done = this.async(),
	me = this,
	npm = require('npm');
	npm.load({}, function(err) {
	npm.registry.adduser(me.data.username, me.data.password, me.data.email, function(err) {
	if (err) {
	console.log(err);
	done(false);
	} else {
	'use strict';

	var React = require('react-native');
	var {
	AppRegistry,
	StyleSheet,
	Text,
	View,
	NativeModules,
	TouchableHighlight,
	/* global module:false */
	module.exports = function(grunt){
	grunt.initConfig({
	pkg: '<json:package.json>',
	meta: {
	banner: '/! <%= pkg.name %> /'
	},
	server: {
	base: '.',
	port: 9999
	<html>
	<head>
	<title>Sample title</title>
	</head>
	<body>
	<h3><a href = "javascript:schema()">Create Schema - Run this first</a></h3>
	<h3><a href = "javascript:list()">List data in DB</a></h3>
	<h1>Test cases</h1>
	<ul>
	<li>
	var secret = "7e58cceaf";

	var params = {
	api_key: "c92a196a2",
	app_version: "1.0",
	backgroundcolor: "",
	calltype: "render",
	cellheight: 300,
	cellwidth: 300,
	cols: 1,
	/**
	* Ideally unit tests should be independent, but there are some cases where you really want those tests to be executed one after the other
	* Here is some code that does exactly that - a wrapper on top of QUnit.
	*
	* Usage
	* Instead of asyncTest, call queuedAsyncTest (same params)
	* Instead of module(), call queuedModule
	* After a test is over and the next test has to run, call nextTest()
	*/
	(function(window, console, undefined){
	var perfjankie = require('perfjankie');
	var browserperf = require('perfjankie/node_modules/browser-perf');
	perfjankie({
	'url': 'http://localhost:8080',
	'browsers': [{
	'browserName': 'chrome'
	}],
	'selenium': 'http://localhost:9515',
	'couch': {
	'server': 'http://localhost:5984',