Download as
Browse Code »

Commit 5d459f2656a205f8d7ebe178d0cb93941cf44e3b

Authored by Melissa Wen
1 parent a7fe3919
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[i3eSW] Reviewing automated tests

Showing 1 changed file with 14 additions and 12 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @5d459f2
... ... @@ -103,18 +103,20 @@ more new code.
103 103  
104 104 ### Automated tests
105 105  
106   -Each one of the Portal's software components had their own test suite. The
107   -development teams were required to maintain and expand them if possible. The
108   -communication of all these software is orchestrated by Colab, which is based on
109   -a plugin architecture. Every component integrated into the Portal had a
110   -specific plugin developed by us. For instance, we developed integration
111   -plugins for Gitlab and Mailman. Plugins had their own test suite that
112   -served as integration tests.
113   -
114   -Both the unit and integration tests provided us the necessary speed and trust
115   -that guaranteed both component and platform stability. If any test suite failed,
116   -either by a test error or coverage reduction below a certain threshold, the
117   -pipeline stopped. Only after all tests passed we moved to prepare the release.
  106 +The SPB portal consists of more than 10 integrated software projects and each
  107 +of them, as well as the entire platform, had to be tested. These software
  108 +components had their own test suite, maintained and expanded by the development
  109 +team. Communication between all components is orchestrated by Colab, a systems
  110 +integration platform for web applications based on a plugins architecture.
  111 +Therefore, specific plugins have been developed for each portal software
  112 +component, such as for Gitlab and Mailman. Each plugin had its own test suite
  113 +and this set also worked as integration test.
  114 +
  115 +Both unit and integration tests provided us the performace and security needed
  116 +to guarantee the stability for components and the platform. If any test suite failed,
  117 +by either a test error or coverage reduction below a certain threshold, the
  118 +pipeline stopped. Only when all tests pass, the pipeline proceed to the step of
  119 +preparing the release.
118 120  
119 121 ### Preparing a new release
120 122  
... ...