DOCSLIB.ORG

Master Thesis Submitted in Fulfilment of the Requirements for the Academic Degree M.Sc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

PERFORMANCE EVALUATION AND OPTIMIZATION OF CONTINUOUS INTEGRATION BASED AUTOMATED TOOLCHAIN FOR SAFETY RELATED EMBEDDED APPLICATIONS SOFTWARE Master Thesis Submitted in Fulfilment of the Requirements for the Academic Degree M.Sc. Dept. of Computer Science Chair of Computer Engineering Submitted by: Zain Ullah Student ID: 395153 Date: 25.10.2016 Supervising tutor: Prof. Dr. W. Hardt Donny Masril [Baumer Hübner GmbH] Abstract Continues Integration has been a vital part of software development process in order to make the development process fast and reliable. There are number of actors which play an important role with support of third party tools that helps the development process to be effective and productive in nature. The CI- toolchain is capable of doing much more than the compilation of the software project which covers the daily life tasks of the developers like testing, documentation etc. The important part of automated toolchain is the conversion of source code artifacts into executables with the help of the build system. The selection of proper build system is a matter of subjective in nature and it depends upon the number of factors that should be analyzed before proceeding forward towards the selection mechanism. This thesis focuses on software rebuilding and proves practically with experiments that could help developers and managers to decide between two important software build systems SCons and CMake. It has been experimentally proved that what are the conditions and situations where SCons performs better and what are the moments where it is wise to select CMake as a build tool. At first, individual build tools are evaluated in terms of scalability, conveniency, consistency, correctness, performance (in terms of speed and targets) and later, the build systems are experimented by automating the workflow by increasing the source code artifacts to evaluate the performance when there is limited user interaction. The behavior of the build systems are also tried with other third party tools like Tessy for testing purposes, Jenkins as CI server, and Polarion as requirement engineering tool to show how much effort is required to integrate third party tools with the build system in order to increase the functionality. The evaluation of the build systems is important because that will highlights the areas where potential candidates are better and where there is lack of functional specifications. Generally speaking, SCons has an advantage of being Pythonic in nature and provides the developer ease of use to specify the build configurations using programmatic skills. CMake on other hand are on top of shelves where there is no need to understanding and caring about the underlying platform and where developers want to generate the native build tool solutions which are readily available for exporting them into IDEs. Though both of the build systems has different goals, for example SCons is ready to sacrifices the performance while providing user correctness of the build while CMake focuses on generating native build tools by understanding the underlying platform. All of these types of situations are discussed with experiments in this thesis and serves as the practical guides for high level managers to decide the build tools among others. After evaluation, this thesis firstly suggests the general techniques where the bottlenecks could be covered and then build tool specific optimizations and recommendations are discussed to speed-up the development process. Keywords: Build systems, SCons, CMake, Performance Evaluation, Optimization 1 Acknowledgments With the utmost respect, I would like to thank my immediate supervisor and mentor, Mr. Donny Masril who have each left an indelible mark on my life, and for that I am humbled and eternally grateful. Donny, you have motivated me not only to set big goals, but to put into motion a plan of action to achieve them with your enthusiasm, talent, and dedication which are truly awe-inspiring. I would also like to thank my University supervisor Prof. Dr. Wolfram Hardt, at TU Chemnitz who has become personal role model of mine, exemplify the type of strong work ethic and commitment to quality that I can only hope to emulate. I would like to dedicate this work to my family and friends. Without your support, this thesis would not have been possible. 2 Table of Contents 1. Introduction ..................................................................................................... 9 1.1 Motivation ................................................................................................................................................ 9 1.2 Contributions ......................................................................................................................................... 10 1.3 Organization .......................................................................................................................................... 10 2. Background .................................................................................................... 11 2.1 Safety Critical Systems ........................................................................................................................... 12 2.2 Continues Integration ............................................................................................................................. 12 2.3 Build Automation ................................................................................................................................... 13 2.4 Toolchain & Components ....................................................................................................................... 15 2.4.1 Version Control System ......................................................................................................... 16 2.4.2 Continues Integration Server (Jenkins) .................................................................................. 17 2.4.3 Build and test Server ............................................................................................................... 18 2.4.4 System Test Platform ............................................................................................................. 19 2.4.4.1 Architecture ............................................................................................................... 20 2.4.4.2 Testing framework .................................................................................................... 20 2.4.4.3 Output files ................................................................................................................ 21 2.4.5 Polarion ALM ......................................................................................................................... 23 2.4.5.1 Requirement Engineering ......................................................................................... 23 2.4.5.2 Test Management ...................................................................................................... 24 2.4.5.3 Bug and Issue tracker ................................................................................................ 25 2.5 Design Goals ......................................................................................................................................... 26 2.5.1 Convenience ........................................................................................................................... 26 2.5.2 Consistency .............................................................................................................................. 26 2.5.3 Correctness .............................................................................................................................. 27 2.5.4 Scalability ................................................................................................................................ 27 2.5.5 Flexibility................................................................................................................................. 27 2.5.6 Performance ............................................................................................................................ 27 2.6 Build System Features .......................................................................................................................... 28 3 2.6.1 Partial compilation .................................................................................................................. 28 2.6.2 Variant Builds ......................................................................................................................... 28 2.6.3 Configuration .......................................................................................................................... 29 2.6.4 Parallel building ...................................................................................................................... 29 2.6.5 Distributed builds .................................................................................................................... 30 2.7 Summary ............................................................................................................................................... 30 3. Build Systems ................................................................................................. 31 3.1 Build System Philosophy ...................................................................................................................... 31 3.2 Build Machines ....................................................................................................................................
Recommended publications
  • Drupaltools Forks 11 Stars 44

    Drupaltools Forks 11 Stars 44

    DrupalTools forks 11 stars 44 A list of popular open source and free tools that can help people accomplish Drupal related tasks. Acquia Dev Desktop (2015) Source: dev.acquia.com/downloads Docs: docs.acquia.com/dev-desktop Drupal: 7, 8 Description: Acquia Dev Desktop is a free app that allows you to run and develop Drupal sites locally on your computer and optionally host them using Acquia Cloud. Use Acquia Dev Desktop to evaluate Drupal, add and test other Drupal modules, and develop sites while on a plane or away from an internet connection. Requires: macos, windows Category: deployment, development, testing Aegir (2007) Source: github.com/aegir-project Docs: docs.aegirproject.org Drupal: 6, 7, 8 Description: Aegir allows you to deploy and manage many Drupal sites, and can scale across multiple server clusters. Aegir makes it easy to install, upgrade, and backup an entire network of Drupal sites. Requires: linux, own-server Category: clustering, hosting, multisite, paas Amazee Silverback (2019) Source: github.com/AmazeeLabs/silverback Drupal: 8 Description: A composer package adding common project dependencies, tooling and configuration scaffolding to Amazee Drupal projects. It aims to improve product quality and reduce maintenance costs by encouraging three simple principles: Maximize open source, Minimize requirements, Testability first. Requires: composer Category: building, cli, deployment, development, provisioning, scaffolding, testing Aquifer (2015) Source: github.com/aquifer/aquifer Docs: docs.aquifer.io Drupal: 6, 7, 8 Description: Aquifer is a command line interface that makes it easy to scaffold, build, test, and deploy your Drupal websites. It provides a default set of tools that allow you to develop, and build Drupal sites using the Drush-make workflow.
  • Software Engineer Is .Jusiak.Net Kr Is @Jusiak.Net (0) 791-384-1386

    Software Engineer Is .Jusiak.Net Kr Is @Jusiak.Net (0) 791-384-1386

    Krzysztof (Kris) Jusiak Software Engineer http://kr is .jusiak.net kr is @jusiak.net (0) 791-384-1386 Education 2005 - 2010 Wroclaw University of Technology Wroclaw (Poland) MSc in Computer Science, specialised in Software Engineering (Top grade) Employment 2013 – Present King London (United Kingdom) Game/Software Developer (Mobile) King is a worldwide leader in casual games with more than 30 billion games played per month globally. We are a leading interactive entertainment company for the mobile world. Our mission is to provide highly engaging content to our audience to match their mobile lifestyles: anywhere, anytime, through any platform and on any device. Software Developer in a scrum team responsible for development and releases of mobile games played by millions active daily players. 90% of my job is focused on developing software using C++14 standard for different platforms such as, iOS, Android and Facebook (HTML5 - Emscripten). My core role is to provide high quality features and review/refactor already implemented. I am also involved in recruitment process by being a technical expert on interviews. I have done a lot of improvements to the projects I have been involved in, such as, performance/compile times optimizations, introduction of static analysis tools as well as a replacement of Service Locator pattern by Dependency Injection. • Implementing and releasing multi-platform games played by more than 100 millions active daily players • Reduced time to render the textures by 10% by changing loading files caching mechanism • Implemented an integration test framework which eliminated commonly reoccurring issues 2009 – 2013 Nokia Networks Wroclaw (Poland) Software Engineer Nokia Networks is the world’s specialist in mobile broadband, which helps enable end users to do more than ever before with the world’s most efficient mobile networks, the intelligence to maximize their value and the services to make it all work together.
  • Automating Drupal Development: Make!Les, Features and Beyond

    Automating Drupal Development: Make!Les, Features and Beyond

    Automating Drupal Development: Make!les, Features and Beyond Antonio De Marco Andrea Pescetti http://nuvole.org @nuvoleweb Nuvole: Our Team ),3.0<4 0;(3@ )Y\ZZLSZ 7HYTH Clients in Europe and USA Working with Drupal Distributions Serving International Organizations Serving International Organizations Trainings on Code Driven Development Automating Drupal Development 1. Automating code retrieval 2. Automating installation 3. Automating site configuration 4. Automating tests Automating1 code retrieval Core Modules Contributed, Custom, Patched Themes External Libraries Installation Pro!le Drupal site building blocks drupal.org github.com example.com The best way to download code Introducing Drush Make Drush Make Drush make is a Drush command that can create a ready-to-use Drupal site, pulling sources from various locations. In practical terms, this means that it is possible to distribute a complicated Drupal distribution as a single text file. Drush Make ‣ A single .info file to describe modules, dependencies and patches ‣ A one-line command to download contributed and custom code: libraries, modules, themes, etc... Drush Make can download code Minimal make!le: core only ; distro.make ; Usage: ; $ drush make distro.make [directory] ; api = 2 core = 7.x projects[drupal][type] = core projects[drupal][version] = "7.7" Minimal make!le: core only $ drush make distro.make myproject drupal-7.7 downloaded. $ ls -al myproject -rw-r--r-- 1 ademarco staff 174 May 16 20:04 .gitignore drwxr-xr-x 49 ademarco staff 1666 May 16 20:04 includes/ -rw-r--r-- 1 ademarco
  • Erik Lindahl

    Erik Lindahl

    HPC Software Engineering Erik Lindahl XSEDE/PRACE/RIKEN/SciNet HPC Summer School Ostrava, CZ, 2018 Extra Q & A session: Here (or outside at the tables) 12.45 today! “The application of a systematic, disciplined, quantifiable approach to the development, operation and maintenance of software, and the study of these approaches, that is, the application of engineering to software.” Experiences from 20 years of GROMACS development The GROMACS picture until early 2011 Source code repository: • Simulation hardware project, turned software CVS • Early development based on our own needs • Turned GPL in 2001, LGPL in 2012 Build Chain: • Organic growth of development Automake/Autoconf/libtool • Roughly 10-15 core developers Bug Tracking: • Another 15-20 active contributors Bugzilla • Currently 3,076,420 lines of C++11 code (“C++11”) • Over the years we have used Fortran, C, Assembly Testing: • Lots of old code. Lots of new code. Lots of complicated (read: bad) code written by scientists Software Scientist engineer • Trained in physics, • Trained in CS/software chemistry, etc. • Care about their problem • Care about their code • Care about short-term • Care about long-term deadlines maintenance • New code = asset • New code = liability • Writes more code than • Reads much more code she reads than she writes Without proper software engineering, we are building a technical debt that sooner or later will have to be paid. “Technical Debt is a wonderful metaphor developed by Ward Cunningham to help us think about this problem. In this metaphor, doing things the quick and dirty way sets us up with a technical debt, which is similar to a financial debt.
  • Jenkins Github Pull Request Integration

    Jenkins Github Pull Request Integration

    Jenkins Github Pull Request Integration Jay remains out-of-date after Wittie synchronised oftener or hypnotized any tastes. Posticous Guthry augur her geebung so problematically that Anson militarizes very percussively. Long-ago Marvin energise her phenylketonuria so heuristically that Bo marinating very indeed. The six step i to endow the required plugin for integrating GitHub with Jenkins configure it. Once you use these tasks required in code merges or any plans fail, almost any plans fail. Enable Jenkins GitHub plugin service equal to your GitHub repository Click Settings tab Click Integrations services menu option Click. In your environment variables available within a fantastic solution described below to the testing. This means that you have copied the user git log in the repository? Verify each commit the installed repositories has been added on Code Climate. If you can pull comment is github pull integration? GitHub Pull Request Builder This is a different sweet Jenkins plugin that only trigger a lawsuit off of opened pull requests Once jar is configured for a. Insights from ingesting, processing, and analyzing event streams. Can you point ferry to this PR please? Continuous Integration with Bitbucket Server and Jenkins I have. Continuous integration and pull requests are otherwise important concepts for into any development team. The main advantage of finding creative chess problem that github integration plugin repository in use this is also want certain values provided only allows for the years from? It works exactly what a continuous integration server such as Jenkins. Surely somebody done in the original one and it goes on and trigger jenkins server for that you? Pdf deployment are integrated errors, pull request integration they can do not protected with github, will integrate with almost every ci job to.
  • How Google Tests Software

    How Google Tests Software

    How Google Tests Software James Whittaker Jason Arbon Jeff Carollo • nTr Addison-Wesley Upper Saddle River, NJ • Boston • Indianapolis • San Francisco New York • Toronto • Montreal • London • Munich • Paris • Madrid Capetown • Sydney • Tokyo • Singapore • Mexico City ' ' ^ : Г: С : '. , Table of Contents Foreword by Alberto Savoia Xlll Foreword by Patrick Copeland xvii Preface ХХШ Chapter 1 Introduction to Google Software Testing 1 Quality^Test 5 Roles 6 Organizational Structure 8 Crawl, Walk, Run 10 Types of Tests 12 Chapter 2 The Software Engineer in Test 15 The Life of an SET 17 Development and Test Workflow 17 Who Are These SETs Anyway? 22 The Early Phase of a Project 22 Team Structure 24 Design Docs 25 Interfaces and Protocols 27 Automation Planning 28 Testability 29 SET Workflow: An Example 32 Test Execution 40 Test Size Definitions 41 Use of Test Sizes in Shared Infrastructure 44 Benefits of Test Sizes 46 Test Runtime Requirements 48 Case 1: Change in Common Library 52 Test Certified 54 An Interview with the Founders of the Test Certified Program 57 Interviewing SETs 62 An Interview with Tool Developer Ted Mao 68 An Interview with Web Driver Creator Simon Stewart 70 How Google Tests Software Chapter 3 The Test Engineer 75 A User-Facing Test Role 75 The Life of а ТЕ 76 Test Planning 79 Risk 97 Life of a Test Case 108 Life of a Bug 113 Recruiting TEs 127 Test Leadership at Google 134 Maintenance Mode Testing 137 Quality Bots Experiment 141 BITE Experiment 153 Google Test Analytics 163 Free Testing Workflow 169 External Vendors 173
  • Enabling Devops on Premise Or Cloud with Jenkins

    Enabling Devops on Premise Or Cloud with Jenkins

    Enabling DevOps on Premise or Cloud with Jenkins Sam Rostam [email protected] Cloud & Enterprise Integration Consultant/Trainer Certified SOA & Cloud Architect Certified Big Data Professional MSc @SFU & PhD Studies – Partial @UBC Topics The Context - Digital Transformation An Agile IT Framework What DevOps bring to Teams? - Disrupting Software Development - Improved Quality, shorten cycles - highly responsive for the business needs What is CI /CD ? Simple Scenario with Jenkins Advanced Jenkins : Plug-ins , APIs & Pipelines Toolchain concept Q/A Digital Transformation – Modernization As stated by a As established enterprises in all industries begin to evolve themselves into the successful Digital Organizations of the future they need to begin with the realization that the road to becoming a Digital Business goes through their IT functions. However, many of these incumbents are saddled with IT that has organizational structures, management models, operational processes, workforces and systems that were built to solve “turn of the century” problems of the past. Many analysts and industry experts have recognized the need for a new model to manage IT in their Businesses and have proposed approaches to understand and manage a hybrid IT environment that includes slower legacy applications and infrastructure in combination with today’s rapidly evolving Digital-first, mobile- first and analytics-enabled applications. http://www.ntti3.com/wp-content/uploads/Agile-IT-v1.3.pdf Digital Transformation requires building an ecosystem • Digital transformation is a strategic approach to IT that treats IT infrastructure and data as a potential product for customers. • Digital transformation requires shifting perspectives and by looking at new ways to use data and data sources and looking at new ways to engage with customers.
  • Devops Point of View an Enterprise Architecture Perspective

    Devops Point of View an Enterprise Architecture Perspective

    DevOps Point of View An Enterprise Architecture perspective Amsterdam, 2020 Management summary “It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change.”1 Setting the scene Goal of this Point of View In the current world of IT and the development of This point of view aims to create awareness around the IT-related products or services, companies from transformation towards the DevOps way of working, to enterprise level to smaller sizes are starting to help gain understanding what DevOps is, why you need it use the DevOps processes and methods as a part and what is needed to implement DevOps. of their day-to-day organization process. The goal is to reduce the time involved in all the An Enterprise Architecture perspective software development phases, to achieve greater Even though it is DevOps from an Enterprise Architecture application stability and faster development service line perspective, this material has been gathered cycles. from our experiences with customers, combined with However not only on the technical side of the knowledge from subject matter experts and theory from organization is DevOps changing the playing within and outside Deloitte. field, also an organizational change that involves merging development and operations teams is Targeted audience required with an hint of cultural changes. And last but not least the skillset of all people It is specifically for the people within Deloitte that want to involved is changing. use this as an accelerator for conversations and proposals & to get in contact with the people who have performed these type of projects.
  • Jenkins Automation.Key

    Jenkins Automation.Key

    JENKINS or: How I learned to stop worrying and love automation #MidCamp 2018 – Jeff Geerling Jeff Geerling (geerlingguy) • Drupalist and Acquian • Writer • Automator of things AGENDA 1. Installing Jenkins 2. Configuation and Backup 3. Jenkins and Drupal JENKINS JENKINS • Long, long time ago was 'Hudson' JENKINS • Long, long time ago was 'Hudson' JENKINS • Long, long time ago was 'Hudson' JENKINS • Long, long time ago was 'Hudson' • After Oracle: "Time for a new name!" JENKINS • Long, long time ago was 'Hudson' • After Oracle: "Time for a new name!" • Now under the stewardship of Cloudbees JENKINS • Long, long time ago was 'Hudson' • After Oracle: "Time for a new name!" • Now under the stewardship of Cloudbees • Used to be only name in the open source CI game • Today: GitLab CI, Concourse, Travis CI, CircleCI, CodeShip... RUNNING JENKINS • Server: • RAM (Jenkins is a hungry butler!) • CPU (if jobs need it) • Disk (don't fill the system disk!) RUNNING JENKINS • Monitor RAM, CPU, Disk • Monitor jenkins service if RAM is limited • enforce-jenkins-running.sh INSTALLING JENKINS • Install Java. • Install Jenkins. • Done! Image source: https://medium.com/@ricardoespsanto/jenkins-is-dead-long-live-concourse-ce13f94e4975 INSTALLING JENKINS • Install Java. • Install Jenkins. • Done! Image source: https://medium.com/@ricardoespsanto/jenkins-is-dead-long-live-concourse-ce13f94e4975 (Your Jenkins server, 3 years later) Image source: https://www.albany.edu/news/69224.php INSTALLING JENKINS • Securely: • Java • Jenkins • Nginx • Let's Encrypt INSTALLING
  • Forcepoint Behavioral Analytics Installation Manual

    Forcepoint Behavioral Analytics Installation Manual

    Forcepoint Behavioral Analytics Installation Manual Installation Manual | Forcepoint Behavioral Analytics | v3.2 | 23-Aug-2019 Installation Overview This Forcepoint Behavioral Analytics Installation manual guides technical Forcepoint Behavioral Analytics users through a complete installation of a Forcepoint Behavioral Analytics deployment. This guide includes step-by-step instructions for installing Forcepoint Behavioral Analytics via Ansible and Jenkins. This document covers system architecture, required software installation tools, and finally a step-by-step guide for a complete install. The System Architecture section shows how data moves throughout software components, as well as how 3rd party software is used for key front- and back-end functionalities. The Installation Components section elaborates on important pre-installation topics. In preparation for initial installation setup, we discuss high level topics regarding Jenkins and Ansible - the tools Forcepoint Behavioral Analytics utilizes to facilitate installation commands. Although Jenkins is pre-configured at the time of install, we include Jenkins Setup information and important access and directory location information for a holistic understanding of this key installation facilitator. To conclude this document, we include step-by-step instructions for using Ansible to initialize the Jenkins CI/CD server to install each required software component. An addendum is included for additional components which can optionally be installed. Go to the Downloads page and navigate to User and Entity Behavior Analytics to find the downloads for Forcepoint Behavioral Analytics. © 2019 Forcepoint Platform Overview - Component Platform Overview - Physical Installation Components Host OS Forcepoint requires a RedHat 7 host based Operating System for the Forcepoint Behavioral Analytics platform to be installed. CentOS 7 (minimal) is the recommended OS to be used.
  • Googletest - Tips and Frequently-Asked Questions About Google C++ Testing Framework - Google C++ Testing Framework - Google Project Hosting

    Googletest - Tips and Frequently-Asked Questions About Google C++ Testing Framework - Google C++ Testing Framework - Google Project Hosting

    8/23/13 FAQ - googletest - Tips and Frequently-Asked Questions about Google C++ Testing Framework - Google C++ Testing Framework - Google Project Hosting My favorites ▼ | Sign in googletest Google C++ Testing Framework Search projects Project Home Downloads Wiki Issues Source Search Current pages for Search FAQ Tips and Frequently­Asked Questions about Google C++ Testing Framework Updated Jul 7, 2013 by [email protected] Why should I use Google Test instead of my favorite C++ testing framework? I'm getting warnings when compiling Google Test. Would you fix them? Why should not test case names and test names contain underscore? Why is it not recommended to install a pre­compiled copy of Google Test (for example, into /usr/local)? How do I generate 64­bit binaries on Windows (using Visual Studio 2008)? Can I use Google Test on MinGW? Why does Google Test support EXPECT_EQ(NULL, ptr) and ASSERT_EQ(NULL, ptr) but not EXPECT_NE(NULL, ptr) and ASSERT_NE(NULL, ptr)? Does Google Test support running tests in parallel? Why don't Google Test run the tests in different threads to speed things up? Why aren't Google Test assertions implemented using exceptions? Why do we use two different macros for tests with and without fixtures? Why don't we use structs as test fixtures? Why are death tests implemented as assertions instead of using a test runner? My death test modifies some state, but the change seems lost after the death test finishes. Why? The compiler complains about "undefined references" to some static const member variables, but I did define them in the class body.
  • Google Test + Gcover

    Google Test + Gcover

    Google Test + gcover Google Test + gcover Una lista de recetas J. Daniel Garcia Grupo ARCOS Universidad Carlos III de Madrid 19 de noviembre de 2016 cbed – J. Daniel Garcia – ARCOS@UC3M ([email protected]) – Twitter: @jdgarciauc3m 1/68 Google Test + gcover Aviso c Esta obra está bajo una Licencia Creative Commons Atribución-NoComercial-SinDerivar 4.0 Internacional. b Debes dar crédito en la obra en la forma especificada por el autor o licenciante. e El licenciante permite copiar, distribuir y comunicar pú- blicamente la obra. A cambio, esta obra no puede ser utilizada con fines comerciales — a menos que se ob- tenga el permiso expreso del licenciante. d El licenciante permite copiar, distribuir, transmitir y co- municar públicamente solamente copias inalteradas de la obra – no obras derivadas basadas en ella. cbed – J. Daniel Garcia – ARCOS@UC3M ([email protected]) – Twitter: @jdgarciauc3m 2/68 Google Test + gcover ARCOS@uc3m UC3M: Una universidad joven, internacional y orientada a la investigación. ARCOS: Un grupo de investigación aplicada. Líneas: Computación de altas prestaciones, Big data, Sistemas Ciberfísicos, y Modelos de programación para la mejora de las aplicaciones Mejorando las aplicaciones: REPARA: Reengineering and Enabling Performance and poweR of Applications. Financiado por Comisión Europea (FP7). RePhrase: REfactoring Parallel Heterogeneous Resource Aware Applications. Financiado por Comisión Europea (H2020). Normalización: ISO/IEC JTC/SC22/WG21. Comité ISO C++. cbed – J. Daniel Garcia – ARCOS@UC3M ([email protected]) – Twitter: @jdgarciauc3m 3/68 Google Test + gcover ¿Te interesa C++? cbed – J. Daniel Garcia – ARCOS@UC3M ([email protected]) – Twitter: @jdgarciauc3m 4/68 Google Test + gcover Pruebas básicas 1 Pruebas básicas 2 Determinando la cobertura 3 Más pruebas unitarias cbed – J.