Skip to content

Testing

Benjamin Orozco edited this page Oct 27, 2015 · 17 revisions

Testing & Quality Assurance

Test-driven Development (TDD)

Software development process that relies on the repetition of a very short development cycle:

  1. First the developer writes an –initially failing– automated test case that defines a desired improvement or new function
  2. Then produces the minimum amount of code to pass that test
  3. Finally refactors the new code to acceptable standards

Source: Wikipedia

Jasmine

Jasmine is a behavior-driven development framework for testing JavaScript code. It does not depend on any other JavaScript frameworks. It does not require a DOM. And it has a clean, obvious syntax so that you can easily write tests.

Jasmine website: jasmine.github.io

Testing Levels

Unit Testing

Software testing method by which individual units of source code are tested to determine whether they are fit for use.

Source: Wikipedia

Integration Testing

Software testing method by which individual software modules are combined and tested as a group.

Source: Wikipedia

Code Coverage

Measure used to describe the degree to which the source code of a program is tested by a particular test suite. A program with high code coverage has been more thoroughly tested and has a lower chance of containing software bugs than a program with low code coverage.

Source: Wikipedia

Services

  • coveralls.io

Continuous Integration & Delivery

Continuous integration (CI) is the practice, in software engineering, of merging all developer working copies with a shared mainline several times a day.

Source: Wikipedia

Continuous Delivery (CD) is a software engineering approach in which teams keep producing valuable software in short cycles and ensure that the software can be reliably released at any time.

Source: Wikipedia

Services & supported databases

Articles

Clone this wiki locally