colthreepv

FROM alpine:latest

RUN apk update && apk upgrade && \
    apk add --no-cache \
    openssh

RUN mkdir -p /keys/web /keys/worker

CMD ssh-keygen -t rsa -f /keys/web/tsa_host_key -N '' && \
  ssh-keygen -t rsa -f /keys/web/session_signing_key -N '' && \

romainpiel

RecyclerViewInteraction.<Item>onRecyclerView(withId(R.id.recyclerview))
    .withItems(items)
    .check(new ItemViewAssertion<Item>() {
        @Override
        public void check(Item item, View view, NoMatchingViewException e) {
            matches(hasDescendant(withText(item.getDisplayName())))
                .check(view, e);
        }
    });

MariusBudin-zz

package com.ics.rxsamples

import android.app.Fragment;
import java.util.concurrent.TimeUnit;
import rx.Observable;
import rx.Subscription;
import rx.android.schedulers.AndroidSchedulers;
import rx.functions.Action1;
import rx.functions.Func1;
import rx.subjects.PublishSubject;

imminent

package your.package;

import android.app.Activity;
import android.os.Bundle;
import android.support.v7.graphics.Palette;
import com.squareup.picasso.Picasso;
import your.package.PaletteTransformation;

import static your.package.PaletteTransformation.PaletteCallback;

traviskaufman

Better Jasmine Tests With this

On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.

The old way

Up until recently, a typical unit test for us looked something like this:

describe('views.Card', function() {

jpardogo

public class ScaleToFitWidthHeightTransform implements Transformation {

        private int mSize;
        private boolean isHeightScale;

        public ScaleToFitWidthHeightTransform(int size, boolean isHeightScale){
            mSize =size;
            this.isHeightScale = isHeightScale;
        }