Discover gists

Чек-лист API тестов

This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].

We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.

Each commit message consists of a header, a body, and a footer.

REST API response format based on some of the best practices

https://api.example.com/v1/items

https://example.com/api/v1/items

	# See https://codeship.com/documentation/docker/browser-testing/
	FROM myapp:base

	# We need wget to set up the PPA and xvfb to have a virtual screen and unzip to install the Chromedriver
	RUN apt-get install -y wget xvfb unzip

	# Set up the Chrome PPA
	RUN wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub \| apt-key add -
	RUN echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list

	<div class="container">
	<div class="calculator">
	<div id="display" class="readout" ></div>
	<div class="keypad">
	<div class="clears">
	<button id="clear">C</button>
	<button id="all-clear">AC</button>
	<button id="back">←</button>
	</div>
	<div class="functions">

	<div id="wrapper">
	<div id="leftPanel">
	<div class="panelTitle">Input</div>
	<textarea id="editor"># H1 Heading

	## H2 Sub-heading

	[Link to Google](https://google.com)

	Here is some `inline code`.

	#!/bin/sh
	set -e

	vendor/bin/phpunit
	npm run prod

	git add .
	(git commit -m "Build frontend assets for deployment to production") \|\| true
	(git push) \|\| true