describe('state', function() {
var stateName ='app.classified';
var $state;
var h;
beforeEach(function() {
module('unitTestTemplates');
module('helpers.unit.state');
#!/usr/bin/python2.7 | |
"""Quick hack of 'modern' OpenGL example using pysdl2 and pyopengl | |
Based on | |
pysdl2 OpenGL example | |
http://www.arcsynthesis.org/gltut/Basics/Tut02%20Vertex%20Attributes.html | |
http://schi.iteye.com/blog/1969710 | |
""" | |
import sys |
# Hello, and welcome to makefile basics. | |
# | |
# You will learn why `make` is so great, and why, despite its "weird" syntax, | |
# it is actually a highly expressive, efficient, and powerful way to build | |
# programs. | |
# | |
# Once you're done here, go to | |
# http://www.gnu.org/software/make/manual/make.html | |
# to learn SOOOO much more. |
from sqlalchemy import create_engine | |
from sqlalchemy.orm import Session | |
from myapp.models import BaseModel | |
import pytest | |
@pytest.fixture(scope="session") | |
def engine(): | |
return create_engine("postgresql://localhost/test_database") |
title | slug | createdAt | language | preview |
---|---|---|---|---|
Unit testing Angular.js app with node.js, mocha, angular-mocks and jsdom |
unit-testing-angular-js-app-with-node |
2015-07-05T18:04:33Z |
en |
Majority of search result about unit testing Angular.js apps is about how to do it by using test frameworks that run the tests in a real browser. Even though it's great to be able to test your code in multiple platforms, in my opinion it creates a lot of boilerplate code and makes it hard to run the tests in, for instance a CI-server. |
Lean unit tests with minimal setup
require 'rbvmomi' | |
require 'pry-byebug' | |
require 'socket' | |
require 'openssl' | |
require 'digest/sha1' | |
require 'io/console' | |
def get_thumbprint(vc) | |
ssl_context = OpenSSL::SSL::SSLContext.new | |
tcp_client = TCPSocket.new vc, 443 |
It sometimes happen you need change code on a machine from which you cannot push to the repo.
You’re ready to copy/paste what diff
outputs to your local working copy.
You think there must be a better way to proceed and you’re right. It’s a simple 2 steps process:
1. Generate the patch:
git diff > some-changes.patch
The good news: you can get it running on the free tier (with a tiny instance).
The bad news: it's stuck on Elasticsearch 1.5.2 and dynamic scripting (Groovy) is disabled.
http://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/aes-limits.html
Authentication: the safest option is to create a brand new IAM user (using the tool at https://console.aws.amazon.com/iam/home?region=us-east-1 ) with its own access key and secret key. Then when you create the Elasticsearch instance you can paste in the following IAM string: