Agile regression system testing

Abstract: This report describes the work on automating the testing of nodes at CCS (Common Control System) in Ericsson. The goal was to every three hours configure nodes with the latest build and run the tests. This process is to be fully automatic without user in-put. The existing configuration tool CICC (Core Integration node Control Center) is to be used for configuration. Before work started fault reports were analyzed and creating a usecase for testing restarts should reduce some faults.The first step was to make the configuration tool CICC automated. To schedule the test-ing the continuous integration tool Jenkins was used. But Jenkins can’t by itself run CICC nor interpret the result. Therefore a wrapper layer was implemented. When the wrapper is finished it stores the results of the configuration run in a XML (eXtensible Markup Language) file, which Jenkins reads. Results can then be seen in Jenkins through web interface. If there were any failures during configuration or testing the failed step will have an error message.The project shows that automation is possible. Automating the testing reduce the time for correcting errors because they are more likely to be found early in the process. Be-fore implementing this project in production some improvements should be made. The most significant improvement is making the configuration and testing of each node par-allel with each other, in order to make the time limit for configuration and testing less of an issue.