Skip to content

Projects' Technical perspective

Julian Reyes Escrigas edited this page Feb 21, 2017 · 6 revisions

Projects' Technical perspective

A set of techniques to keep projects on good shape and trying to keep the technical debt at minimum (at least we try)

Linting

Code linting is a type of static analysis that is frequently used to find problematic patterns or code that doesn't adhere to certain style guidelines

This utility allow check code based on a set of rules, there's some ways to defined rules for a specific project but often we'll use .eslintrc files, files within the following content

{
    "rules": {
        "semi": ["error", "always"],
        "quotes": ["error", "double"]
    }
}

We can also reuse prefined set of rules (previously packaged by someone) like

{
    "extends": "eslint:recommended"
}

Testing

Testing involves the execution of component or the whole system to evaluate one or more propecties of interest like

  • Meets the requirements that guided the design and development
  • Response correctly to all kinds of inputs
  • archivies the general result its stakeholders desire
  • Performs its functions within acceptable time

Test coverage

Is a measure to describe the degree to which the source code is executed when a particular test suite runs, measured as a percentage, highter values suggest it has a lower chance of containin undetected bugs

Build

the process of building, it coordinates and control the correct order of execution of the phases to run a project in the desired environment

Clone this wiki locally