The CEF QA process currently leverages highly automated testing to cover
the majority of the scenarios that might break or suffer from regression
using unit testing (mostly implemented for C# layers, in process for
Middle layers - Angular, etc.), UI testing (in progress) and other forms
of automated testing mechanisms. The below outline will highlight the
layers of testing currently in place and provide links to dive into more
detail for each.
The unit testing layer details are here (link coming).
The Dev Master QA test plan, which will be performed and signed off on
before an RC pull request will be approved, consists of a roughly 30
minute long, cursory review of the Dev Master site. The idea is to get
at least 85-90% coverage of the core functionality of the platform
within a 30 minute period. An assigned QA team member from the QA
approved team must sign-off that a successful run of the cursory review
was completed.
Click
here
to view more details on the Dev Master QA process.
The RC QA test plan, which will be performed and signed off on before a
Master pull request will be approved, consists of a detailed 2.5 hour
long, granular review of the RC site. The idea is to get at least
98-99.5% coverage of the core functionality of the platform within a 2.5
hour period. An assigned QA team member from the QA approved team must
sign-off that a successful run of the cursory review was completed.
Click here to view more details on the RC QA process.