Continuous integration: Difference between revisions
From LimeSurvey Manual
(→Parts) |
(→Parts) |
||
| Line 9: | Line 9: | ||
== Parts == | == Parts == | ||
# | # Syntax check | ||
# PSR-12 | |||
# Type check | |||
# Unused variables | |||
# Tests | # Tests | ||
## Unit tests | ## Unit tests | ||
## Functional tests (with fixture) | ## Functional tests (with fixture) | ||
## Integrity tests (with scripted browser) | ## Integrity tests (with scripted browser) | ||
Todo: | |||
* Metrics | |||
* Test coverage | |||
* Code duplication | |||
== Tools == | == Tools == | ||
Revision as of 23:54, 10 October 2021
Continuous integration (CI) is the concept of running tests and checks on each push, to reduce different risks related to the development cycle.
Motivation
- Be proactive rather than reactive
- Identify hotspots
- Reduce the risk of bugs and regressions
Parts
- Syntax check
- PSR-12
- Type check
- Unused variables
- Tests
- Unit tests
- Functional tests (with fixture)
- Integrity tests (with scripted browser)
Todo:
- Metrics
- Test coverage
- Code duplication
Tools
todo
Metrics
todo