Project

General

Profile

Quality management » History » Revision 6

Revision 5 (Detlef Hühnlein, 10/22/2015 12:33 PM) → Revision 6/9 (Detlef Hühnlein, 10/22/2015 01:06 PM)

h1. Quality management 

 The quality management consist of two big parts. The first part is covered by the [[Developer Guide]] which contains the rules regarding to the code quality, code style, etc. The second part is a description of test which ensure have to be completed before a new version of the Open eCard App is released. 

 h2. Quality Assurance Process 

 ISO 9000 defines quality assurance as a "part of quality management [...] focused on the providing confidence that quality requirements will be fulfilled." [ISO05]. In this sense quality assurance is a process targeting the objective to guarantee that a product works as intended. This task is mostly done by specifying tests which may be automated or not. The Open eCard project uses a mixture of manual and automated tests in the form of Continuous Integration and acceptance tests where automation is not feasible. 

 h3. Continuous Integration  

 The Open eCard team uses Jenkins as tool for this task. The Jenkins server builds the complete project after a new version has been uploaded to the main Git repository after that all unit and integration tests available and enabled are performed. If an error occurs while this procedure the responsible release manager and if contact information are available the developers are informed. In the case that are all test successfully executed the release manger has to decide whether to accept or reject the changes. 

 h3. Acceptance Testing 

 The main focus of the acceptance testing is the compliance to the technical guideline BSI-TR03124 part 2 and the practical usability with 
 existing services, services which accept the "supported cards":https://www.openecard.org/ecards/.  

 Therefore the acceptance tests currently comprise include the following areas: 
 following: 

 # *eID-Client-Test-Suite* 
 The conformance is tested with the latest available version of the official "test suite": test suite issued by the BSI. This is a specialized test which ensures that the Open eCard App works as described in BSI-TR03124 part 1. So it covers just the functionality of the German eID card but there are general parts, which are also usable for other cards like the directions regarding error messages, information to display on the UI e.g retry counters of a PIN, etc. 
 # *Services which accept the German eID Card* 
 An important requirement is that the Open eCard App works with existing services, services which accept the German eID. 
 # *Services which accept cards with TLS-Client-Authentication* 
 Finally Another Besides the Open eCard App user interface testing for other cards which is meant currently restricted to be used for TLS-Client-Authentication at corresponding services, which accept the supported cards.   

 The policy for performing acceptance tests PIN entry dialog there is as follows: 

 # The set a need to test the card possibilities like creation of required acceptance tests depends on a electronic signature or creating a random number. Currently there is just the implemented changes since procedure of testing an TLS authentication where the last accepted version. 
 # At least card signs a challenge by performing the tests corresponding operation @Perform Security Operation Digital Signature@ or @Internal Authenticate@ (according to ISO/IEC 7816 part 4). This includes also some more smart card related methods to select and read the affected module (cf. Figure 3 in "[NHHW15]":https://ecsec.de/pub/OID_2015_QMS.pdf specific files containing required certificates and Figure 1 in "[WHP+13]":http://www.ecsec.de/pub/2013_OID_Platform.pdf) MUST be tested completely. 
 # Additionally there MUST be a reasonable number of randomly chosen additional samples, separate applications which are selected in a way which makes it extremely likely that all requirements are indeed fulfilled. 
 # The execution of may contain the tests and the corresponding test results MUST be documented in a conclusive manner. 









 signing key. 











 ISO05: ISO. 9000:2005 Quality management systems Fundamentals and vocabulary. ISO 9000:2005, International Organizations for Standardization, 2005.