M2:Dev

Test Levels and Test Types are two angles to think about different tests.

Test Level

There are generally four recognised levels of tests: unit testing, integration testing, system testing, and acceptance testing.

Test Type

Installation testing

Compatibility testing

Smoke and sanity testing

Regression testing

Acceptance testing

Alpha testing

Beta testing

Functional vs non-functional testing

Destructive testing

Software performance testing

Usability testing

Accessibility testing

Security testing

A/B testing

If an object is declared with retainable object owner type, but without an explicit ownership qualifier, its type is implicitly adjusted to have __strong qualification.

As a special case, if the object’s base type is Class (possibly protocol-qualified), the type is adjusted to have __unsafe_unretained qualification instead.

Here is a template originally written by Tim Pope at tpope.net and mentioned in the Pro Git book

Short (50 chars or less) summary of changes

More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase can get confused if you run the two together.

Further paragraphs come after blank lines.

- Bullet points are okay, too

- Typically a hyphen or asterisk is used for the bullet, preceded by a single space, with blank lines in between, but conventions vary here

From Documentation/SubmittingPatches in the Git repo: