joshdover

class Albedo.GaugeView extends Batman.View
  @option 'title', 'max', 'min', 'value', 'better'

  @::on 'appear', ->
    @makeGauge()

  makeGauge: ->
    node = $(@get('node'))
    node.attr 'id', @get('title')

joshdover

source "https://rubygems.org"

gem "rspec"
gem "capybara"
gem "headless"

joshdover

<!-- Include Mixpanel and init before this. -->

<!-- Place at the bottom of your layout (ex: app/views/layouts/application.html.erb) -->
<% if content_for :mixpanel %>
  <%= javascript_tag(yield :mixpanel) %>
<% end %>

joshdover

# Helper for tracking mixpanel events, allows for declaritve events. Usage:
#   <a href="http://google.com" data-mixpanel="name: 'clicked link'">Google</a>
#   <a href="http://cows.com"   data-mixpanel="name: 'clicked link', data: { animal: 'cow' }">Cow</a>
#   <li data-mixpanel="'clicked list element'">I am not a link!</li>
$(document).on "click", "[data-mixpanel]", (event) ->
  options = eval "({" + $(this).attr("data-mixpanel") + "})"

  # If event is bound to a link, add delay to ensure event is tracked.
  if event.currentTarget.href?
    options.data = {} if !options.data?

joshdover

describe('Controller: MyCtrl', function () {
  beforeEach(module('MyApp'));
  var scope;

  // Initialize the controller and a mock scope
  beforeEach(inject(function ($controller, $rootScope) {
    scope = $rootScope.$new();

    startController = function() {
      $controller('MyCtrl', {

joshdover

new MozActivity({
  name: 'send',
  data: {
    type: 'text/plain',
    text: 'Hello Android, I am a web app!'
  }
});

joshdover

Idiomatic React Testing Patterns

Testing React components seems simple at first. Then you need to test something that isn't a pure interaction and things seem to break down. These 4 patterns should help you write readable, flexible tests for the type of component you are testing.

Setup

I recommend doing all setup in the most functional way possible. If you can avoid it, don't set variables in a beforeEach. This will help ensure tests are isolated and make things a bit easier to reason about. I use a pattern that gives great defaults for each test example but allows every example to override props when needed:

joshdover

import { Modifier, EditorState, RichUtils } from 'draft-js';
import getCurrentlySelectedBlock from './getCurrentlySelectedBlock';

export const ALIGNMENTS = {
	CENTER:  'center',
	JUSTIFY: 'justify',
	LEFT:    'left',
	RIGHT:   'right'
};

joshdover

Install python-flamegraph into your project:

pip install git+https://github.com/evanhempel/python-flamegraph.git

Record a profile around a bit of code:

import flamegraph
thread = flamegraph.start_profile_thread(fd=open("./profile.log", "w"))

joshdover

--- config.cc   2018-06-01 22:18:19.000000000 -0500
+++ config1.cc  2018-06-01 22:18:02.000000000 -0500
@@ -3258,7 +3258,7 @@

     fprintf(fp, ", biosdetect=%s", SIM->get_param_enum("biosdetect", base)->get_selected());

-    if (SIM->get_param_string("model", base)->getptr()>0) {
+    if (SIM->get_param_string("model", base)->getptr() != 0) {
         fprintf(fp, ", model=\"%s\"", SIM->get_param_string("model", base)->getptr());
     }