From 59264f154ea416f60f6192c36003c68470051b9d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jurica=20Zuanovi=C4=87?= Date: Wed, 16 Jan 2019 14:18:20 +0100 Subject: [PATCH] Fixing word spelling (#27807) Fix "potentiual" to "potential" --- guide/english/agile/continuous-integration/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/english/agile/continuous-integration/index.md b/guide/english/agile/continuous-integration/index.md index 1549213c54..fafe60e320 100644 --- a/guide/english/agile/continuous-integration/index.md +++ b/guide/english/agile/continuous-integration/index.md @@ -3,7 +3,7 @@ title: Continuous Integration --- ## Continuous Integration -At its most basic, continuous integration (CI) is an agile development methodology in which developers regularly merge their code directly to the main source, usually a remote `master` branch. In order to ensure that no breaking changes are introduced, a full test suite is run on every potentiual build to regression test the new code, i.e. test that the new code does not break existing, working features. +At its most basic, continuous integration (CI) is an agile development methodology in which developers regularly merge their code directly to the main source, usually a remote `master` branch. In order to ensure that no breaking changes are introduced, a full test suite is run on every potential build to regression test the new code, i.e. test that the new code does not break existing, working features. This approach requires good test coverage of the code base, meaning that a majority, if not all, of the code has tests which ensure its features are fully functional. Ideally continuous integration would be practiced together with full Test-Driven Development.