1 / 22

Quality Assurance with ETICS – multi-node automated testing

Quality Assurance with ETICS – multi-node automated testing. M.Zurek, A. A. Rodriguez, A. Aimar, A. di Meglio, L. Dini. CGW 09. CERN. Krakow, 12 October 2009. Contents. ETICS Overview Multi-Node Testing Q & A. ETICS Overview. The Problem.

bunme
Télécharger la présentation

Quality Assurance with ETICS – multi-node automated testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Quality Assurance with ETICS – multi-node automated testing M.Zurek, A. A. Rodriguez, A. Aimar, A. di Meglio, L. Dini CGW 09 CERN Krakow, 12 October 2009

  2. Contents • ETICS Overview • Multi-Node Testing • Q & A ETICS Testing Tools

  3. ETICS Testing Tools ETICS Overview

  4. The Problem Distributed Computing, Distributed Development ETICS Online tutorials - Module 01

  5. The ETICS System • Continuous software build, test and QA verification system • Easily extensible with additional plugins • Scheduled or on-demand build and test jobs • User computers or remote distributed infrastructures • Built-in connectors to distribute build and test jobs on different types of infrastructures from standard job management systems to the grid • Open repository of configuration metadata, packages and build, test and QA reports • Support for standard package management systems like YUM • It’s multi-platform and independent from any specific language, build or test tool ETICS Testing Tools

  6. Architecture ETICS Testing Tools

  7. The Configuration Web Client ETICS Online tutorials - Module 01

  8. Command-line Client ETICS Online tutorials - Module 01

  9. The Repository Web Application ETICS Online tutorials - Module 01

  10. Examples of Plugins ETICS Online tutorials - Module 01

  11. ETICS Testing Tools Multi Node

  12. Multi-Node The ability to setup scenarios where multiple services are automatically deployed in multiple nodes. These services must be able to work properly as if they would be installed manually by a user performing any required operation in the required order. ETICS Testing Tools

  13. ChallangeService Synchronization ETICS Testing Tools

  14. ChallangeInformation Interchange ETICS Testing Tools

  15. ChallangeFlow Monitoring ETICS Testing Tools

  16. The ETICS Solution • ETICS-SETis used to publish key-value pairs or only keys to the central information system in order to make the information available to all the other nodes, services or phases. • ETICS-GETis used to get (blocking or not-blocking) the information published by some local or remote execution of ETICS-SET. • ETICS-LOG is used to log and for real-time monitoring. Server Node Central IS Client Node [ … INSTALL …] [ … CONFIG … ] [ … START … ] ETICS-SET S.IP = x.x.x.x ETICS-LOG “RUNNING” ETICS-GET C.DONE [… STOP AND EXIT …] S.IP = x.x.x.x S: “RUNNING” C.DONE $IP = ETICS-GET S.IP [ … USE $IP … ] [… RUN TEST …] ETICS-SET C.DONE [… EXIT …] ETICS Testing Tools

  17. The PING Example (1/3) ETICS Testing Tools

  18. The PING Example (2/3) ETICS Testing Tools

  19. The PING Example (3/3) CLIENT SERVER ETICS Testing Tools

  20. Challenges • Deployment automation in the context of complex software development is a prerequisite for automatic system testing • Complexity of service configuration • Developers should provide deployable configurations, or parameterised configurations • External dependencies: all dependencies must be deployable automatically • Knowledge of these “external” components is not necessarily with the end-user • Privileged deployment/configuration operations • Root / Super User actions • Mix of normal user-level and root level actions ETICS Testing Tools

  21. Benefits • Automation of complex processes • Automatic setup of complex environment • Automatic generation of reports • Save on resources and time • More scenarios can be explored • Less human errors • Form the foundation for more advanced system tests ETICS Testing Tools

  22. Thanks! http://www.eticsproject.eu ETICS Testing Tools

More Related