From a3f537adbb9a3049d929af68288a3bdbcbd75eb0 Mon Sep 17 00:00:00 2001
From: Paulo Meirelles <paulo@softwarelivre.org>
Date: Fri, 17 Nov 2017 22:25:29 -0200
Subject: [PATCH] Improving Automated Tests section

---
 ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 33 ++++++++-------------------------
 1 file changed, 8 insertions(+), 25 deletions(-)

diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index 1498cd6..d6b420d 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -181,31 +181,14 @@ https://www.openhub.net/p/mailman
 
 ### Automated Tests
 
-<!---
-No final do contexto, adicionar um parágrafo final falando que geramos o SPB de forma a integrar 5 sistemas e manter mais de 30 pacotes.
-Os 5 projetos são: Colab, Noosfero, Gitlab, MailMan, and Mezuro.
-
-The SPB portal is a system-of-systems with 5 integrated software projects.
-
-To do this, we leveraged our choice of Colab (www.github.com/colab) as the
-orchestrator in the SPB. Colab is a systems
-integration platform for web applications based on a plugin architecture. In
-SPB, we developed specific plugins
-for each portal software component, such as Gitlab (www.gitlab.com) and
-Noosfero (www.noosfero.org).
--->
-
-The SPB portal is a system-of-systems, each
-of them had to be tested with its own test suite.  This was not enough,
-however: we also had to test the platform as a whole. Given that the plugins
-also have their own test suites, these suites assume a double role as both
-plugin tests and as integration tests.
-
-Both unit and integration tests provided us the performance and security needed
-to guarantee the stability of components and the platform. If any test suite
-failed, by either a test error or coverage reduction below a certain threshold,
-the process stopped. Only when all tests passed, the pipeline proceeded to the
-step of release preparation.
+Each integrated system had to be tested with its own test suite. This was not
+enough, however: we also had to test the platform as a whole. Given that the
+plugins also have their own test suites, these suites assume a double role as
+both plugin tests and as integration tests. These tests provided us the
+performance and security needed to guarantee the stability of components and
+the platform. If any test suite failed, by either a test error or coverage
+reduction below a certain threshold, the process stopped. Only when all tests
+passed, the pipeline proceeded to the step of release preparation.
 
 ### Preparing a New Release
 
--
libgit2 0.21.2