From 5d459f2656a205f8d7ebe178d0cb93941cf44e3b Mon Sep 17 00:00:00 2001 From: Melissa Wen Date: Mon, 31 Jul 2017 23:42:07 -0400 Subject: [PATCH] [i3eSW] Reviewing automated tests --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index 10adf50..0b2309d 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -103,18 +103,20 @@ more new code. ### Automated tests -Each one of the Portal's software components had their own test suite. The -development teams were required to maintain and expand them if possible. The -communication of all these software is orchestrated by Colab, which is based on -a plugin architecture. Every component integrated into the Portal had a -specific plugin developed by us. For instance, we developed integration -plugins for Gitlab and Mailman. Plugins had their own test suite that -served as integration tests. - -Both the unit and integration tests provided us the necessary speed and trust -that guaranteed both component and platform stability. If any test suite failed, -either by a test error or coverage reduction below a certain threshold, the -pipeline stopped. Only after all tests passed we moved to prepare the release. +The SPB portal consists of more than 10 integrated software projects and each +of them, as well as the entire platform, had to be tested. These software +components had their own test suite, maintained and expanded by the development +team. Communication between all components is orchestrated by Colab, a systems +integration platform for web applications based on a plugins architecture. +Therefore, specific plugins have been developed for each portal software +component, such as for Gitlab and Mailman. Each plugin had its own test suite +and this set also worked as integration test. + +Both unit and integration tests provided us the performace and security needed +to guarantee the stability for components and the platform. If any test suite failed, +by either a test error or coverage reduction below a certain threshold, the +pipeline stopped. Only when all tests pass, the pipeline proceed to the step of +preparing the release. ### Preparing a new release -- libgit2 0.21.2