Esta palestra um case de utilização de indicadores de eficiência e eficácia no board de Delivery. Mostramos também dicas do processo de passagem dos artefatos de produto para desenvolvimento.
This session aims to shed some light to an emerging test automation framework Karate DSL. This framework resolves many of the test automation problems by having API test-automation along with performance-testing and UI Web Automation testing into a single, unified framework.
This intermediate-level Postman training is geared specifically for API testers and other stakeholders invested in the health of your APIs, including product managers, business managers, DevOps practitioners, and more.
“Continuous quality” is a holistic mindset for API testing, and in this session, we’ll discuss continuous quality principles as we walk through some advanced testing workflows and recommended practices for testing in Postman.
DevOps & Cloud - The Essentials for Digital TransformationCloudJourneee
Learn how DevOps and Cloud can help in Digital Transformation. The deck covers:
Digital Transformation - The Current Organizational Scenario
Understanding the DevOps – Cloud Relationship
Building & Managing Cloud Applications with DevOps
Use Cases
Benefits of Moving to Cloud with DevOps
Esta palestra um case de utilização de indicadores de eficiência e eficácia no board de Delivery. Mostramos também dicas do processo de passagem dos artefatos de produto para desenvolvimento.
This session aims to shed some light to an emerging test automation framework Karate DSL. This framework resolves many of the test automation problems by having API test-automation along with performance-testing and UI Web Automation testing into a single, unified framework.
This intermediate-level Postman training is geared specifically for API testers and other stakeholders invested in the health of your APIs, including product managers, business managers, DevOps practitioners, and more.
“Continuous quality” is a holistic mindset for API testing, and in this session, we’ll discuss continuous quality principles as we walk through some advanced testing workflows and recommended practices for testing in Postman.
DevOps & Cloud - The Essentials for Digital TransformationCloudJourneee
Learn how DevOps and Cloud can help in Digital Transformation. The deck covers:
Digital Transformation - The Current Organizational Scenario
Understanding the DevOps – Cloud Relationship
Building & Managing Cloud Applications with DevOps
Use Cases
Benefits of Moving to Cloud with DevOps
"Experiences Of Test Automation At Spotify" with Kristian KarlTEST Huddle
View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-87-experiences-of-test-automation-at-spotify-
At Spotify, we want the manual testing effort to be focused as much as possible at feature testing, less on regression tests. But we still have to do regression. So, we tried to automate a big chunk of that. Regression tests are run on our Desktop, Android, iOS and WebPlayer clients, and also some backend services.
I will share with you how far we have come. What techniques, tools and methodologies we have tried. What experiences has been good, and what has been not that good.
Testing RESTful Webservices using the REST-assured frameworkMicha Kops
The REST-assured framework and its features explained by example.
For detailed information please take a look at my full tutorial including the sources at http://www.hascode.com/2011/10/testing-restful-web-services-made-easy-using-the-rest-assured-framework/
Space Camp :: API Lifecycle, Part I: Build and Test an APIPostman
Join us for a one-hour, intermediate-level Postman learning session geared specifically for API developers, API producers, and anyone else invested in building quality APIs. We’ll walk through the initial stages of the API lifecycle, including designing, defining, documenting, and testing an API.
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
My playbook for when starting a new role as an engineer. If you're new to the industry or new to changing jobs, there's some helpful information and a game plan for how to be successful for your first week. You can find more information about this presentation at https://blog.thesoftwarementor.com/presentations
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
Objectives:
1. To understand software testing and its importance.
2. To understand the concepts of software quality.
3. To see the different classes/ levels/ types of testing.
4. To see the different test case design techniques.
5. To understand the software processes related to testing in a typical software organisation.
"Experiences Of Test Automation At Spotify" with Kristian KarlTEST Huddle
View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-87-experiences-of-test-automation-at-spotify-
At Spotify, we want the manual testing effort to be focused as much as possible at feature testing, less on regression tests. But we still have to do regression. So, we tried to automate a big chunk of that. Regression tests are run on our Desktop, Android, iOS and WebPlayer clients, and also some backend services.
I will share with you how far we have come. What techniques, tools and methodologies we have tried. What experiences has been good, and what has been not that good.
Testing RESTful Webservices using the REST-assured frameworkMicha Kops
The REST-assured framework and its features explained by example.
For detailed information please take a look at my full tutorial including the sources at http://www.hascode.com/2011/10/testing-restful-web-services-made-easy-using-the-rest-assured-framework/
Space Camp :: API Lifecycle, Part I: Build and Test an APIPostman
Join us for a one-hour, intermediate-level Postman learning session geared specifically for API developers, API producers, and anyone else invested in building quality APIs. We’ll walk through the initial stages of the API lifecycle, including designing, defining, documenting, and testing an API.
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
My playbook for when starting a new role as an engineer. If you're new to the industry or new to changing jobs, there's some helpful information and a game plan for how to be successful for your first week. You can find more information about this presentation at https://blog.thesoftwarementor.com/presentations
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
Objectives:
1. To understand software testing and its importance.
2. To understand the concepts of software quality.
3. To see the different classes/ levels/ types of testing.
4. To see the different test case design techniques.
5. To understand the software processes related to testing in a typical software organisation.
JAX-RS 2.0: RESTful Java on Steroids, by Aron GuptaCodemotion
The purpose of this technical session is to elaborate on all the new features being discussed in JAX-RS 2.0. The most commonly requested feature for JAX-RS 2.0 is a client API. Client APIs can range from low-level, just above HttpURLConnection, to high-level, often including support for IoC and hyperlinking. Other features this presentation covers are hypermedia, MVC, validation, interceptors, improved content negotiation, and better integration with other specifications such as JSR 330.
The presentation provides overview of JAX-RS 2.0 and the cool new things that come with it. It also provides an introduction to OData which is a protocol proposed by Microsoft for data interchange.
This is a introduction to Maven 2. For more information visit http://jpereira.eu/2012/05/03/an-introduction-to-maven-2/
If you want to download the editable presentation contact me (find my contacts on my blog)
Given at TechMaine's Java Users Group on Feb 26 2008
Why do we need another build tool when we already have Ant? By focusing on convention over configuration, Maven allows you to declaratively define how your project is built, which reduces a lot of the procedural code that you'd need to implement in every build file if you were using Ant. This, along with Maven's built-in management of repositories for project dependencies, allows you to streamline your build process. Ultimately Maven can reduce the amount of time that would otherwise be wasted hunting down jar files and fiddling with boilerplate build scripts.
This presentation covers Maven's core concepts. It introduces the Plugin architecture, and explain how the most popular plugins are used. It also covers the POM concept and how it relates to dependency tracking and repositories.
Te presentamos una guía completa, sencilla y práctica para buscar en Google y encontrar todo lo que necesitas sin perder el tiempo.
Descubre como emplear el menú de la búsqueda simple, los operadores de búsqueda, el formulario de búsqueda avanzada y como recuperar información de artículos científicos y patentes.
Todo ello usando sólo Google
Simple y breve introducción a Apache Ant: herramienta usada en programación para la realización de tareas mecánicas y repetitivas, normalmente durante la fase de compilación y construcción (build).
Testing en proyectos Grails del día a día. Greach 2013Dani Latorre
En todos los proyectos de software, habitualmente tenemos que dedicarle mucho esfuerzo al testing. A asegurarnos de que los productos que desarrollamos funcionen correctamente y, aunque sabemos que es imposible asegurar que no tenga ninguno, sí debemos procurar que tengan el menor número de errores posible.
Debemos escribir código que pruebe nuestro código, automatizar al máximo nuestros tests para hacerlos repetibles y poder conocer lo antes posible cuando hemos roto algo, porque no nos engañemos, de vez en cuando rompemos algo.
Si además de escribir tests, lo hacemos antes, estaremos escribiendo antes un cliente que usará nuestro API que la implementación. De ese modo la cobertura de test sobre nuestro código crece exponencialmente y los mismos tests nos guiarán a que nuestro diseño mejore practicando las refactorizaciones pertinentes; En definitiva estaremos practicando TDD.
En esta charla no pretendo sentar cátedra sobre como hacer testing, simplemente compartiré como lo hago yo en mis proyectos Grails, desde los unitarios subiendo hasta la interfaz de usuario.
Conjunto de principios, no son reglas, aplicados al diseño orientado a objetos. SOLID no es un framework, ni una tecnología, tampoco una librería y mucho menos una metodología. Su propósito es generar código fácil de entender y mantener. Representa cinco principios básicos de la programación orientada a objetos y el diseño.
¿Por que cambiar de Apache Hadoop a Apache Spark?Socialmetrix
Abstract de la charla realizada en SUGAR - Scala User Group Argentina
Apache Spark [1] es un framework para procesamiento distribuído diseñado para ser amigable para Data-Scientists y programadores, con soporte nativo a muchos lenguajes y diversidad de formatos de datos es extramadamente flexible. Cambiando el modelo establecido por Hadoop v1 de Map-Reduce por un grafo de ejecución (DAG) y manteniendo los pasos intermédios en RAM, Spark brinda excelente performance y una API muy expresiva.
Gustavo Arjones [2], CTO de Socialmetrix, va contar la experiencia que tuvieron al cambiarse de Hadoop a Spark y lo que los llevaron a este cambio. Esta charla es una introducción teorica y practica a Spark y sus distintos componentes.
Los tópicos a discutir son:
• Qué és?
• Aspectos que hacen Spark tan atractivo para la comunidad
• Plataforma unificada para Data Science (Batch, Stream, ML, Graph)
• Soporte a distintos lenguajes
• Ejecución: RDD y DAG / Task Scheduller
• Tracción de la comunidad (# commits, # commiters)
• testing, etc
• Demos:
• Spark-shell: Explicar paso a paso el WordCount
• LogAnalytics - compilar y submeter al cluster
• SQL/DataFrames: Demostrar que se puede consumir directamente JSON y hacer queries con SQL
[1] http://spark.apache.org
[2] https://linkedin.com/in/arjones
See how Groovy can help you in your Android development. From language basics to advanced features such as ASTs or Extension Modules. Also there's room for talking about testing and reactive programming.
2. Hola!
• Mario García
• @marioggar
• desmontandojava.blogspot.com
Wednesday, April 25, 12
3. ¿De qué voy a hablar?
• Evolución de “Build Tools” en java
• Qué es Gradle
• Qué tiene que aportar respecto a Maven
• Puntos fuertes
• Puntos flojos
Wednesday, April 25, 12
6. Evolución
• Apache Ant
• Configuración sobre convención
• Basado en xml y en general muy verboso
• No gestiona de manera integrál las
dependencias (Ivy)
• Lo mejor: Realizar tareas custom
• Lo peor: xml y la gestión de dependencias
Wednesday, April 25, 12
8. Evolución
• Apache Maven
• Convención sobre configuración
• Basado en xml menos verboso que Ant
• Integra la gestión de dependencias
• Lo mejor: Gestión de dependencias, y distribución de proyectos
• Lo peor: xml y dificultad para tareas “custom”
Wednesday, April 25, 12
11. ¿Que és Gradle?
• Herramienta de construcción de software
que combina la flexibilidad de Ant con las
convenciones de Maven
Wednesday, April 25, 12
12. ¿Que és Gradle?
• Herramienta de construcción de software
que combina la flexibilidad de Ant con las
convenciones de Maven
Wednesday, April 25, 12
13. ¿Que és Gradle?
• Herramienta de construcción de software
que combina la flexibilidad de Ant con las
convenciones de Maven
?
Wednesday, April 25, 12
15. ¿Qué es Gradle?
• Groovy
• Reducción de lineas de código respecto a Xml
• Usas código que puedes trazar, testear...
• Puedes crear tu propia dsl para tus scripts de
build
Wednesday, April 25, 12
16. ¿Qué es Gradle?
• Fichero de Gradle
• Ant --> ant.build
• Maven --> pom.xml
• Gradle -->build.gradle
Wednesday, April 25, 12
17. ¿Qué es Gradle?
• Tasks
• La unidad de operación es la tarea (task)
• Las tareas se invocan despues del comando
“gradle”:
• gradle build
• Se pueden encadenar tantas tareas en linea de
comandos como se quiera:
• gradle clean compileJava
Wednesday, April 25, 12
18. ¿Qué es gradle?
• Consola
• Encadenar llamadas a tareas
• Gradle daemon: mejora de rendimiento
• Gradle gui
• Información sobre tareas
• Próximamente: consola interactiva con
autocompletado
Wednesday, April 25, 12
19. Round 1
• Xml vs Código
• Maven: se basa en xml, y siempre tienes que
escribir una serie de etiquetas para realizar
ciertas tareas.
• Gradle: te permite hacer lo mismo con menos
código.
Wednesday, April 25, 12
21. Round 2
• Convención sobre configuración
• Ambos permiten tener un layout por defecto para proyectos Java/
Groovy/Scala
• Pero Gradle te permite extender la convención con Ant,
Groovy, “Tipos”,Orden por dependencia entre tareas.
Wednesday, April 25, 12
22. Round 3
• Ciclo de vida
• Maven: compilado, compilado de tests, tests,
empaquetado...
• Gradle: inicialización, configuración, ejecución.
(Los plugins crean sus propios ciclos de vida
encadenando tasks)
Wednesday, April 25, 12
23. Round 4
• Scripting
• Maven: Realizar scripting en Maven es un
infierno, además de que la mayoría de las veces
acabas embebiendo código en el propio xml.
• Gradle: En Gradle, el propio script es código
con lo que puedes importar plugins o clases de
utilidad que ya tuvieras para realizar las tareas y
ademas categorizarlas.
Wednesday, April 25, 12
25. Round 5
• Dependencias
• Maven: es la referencia en la gestión/
distribución de dependencias. No puede agrupar
dependencias.
• Gradle: delega en Maven/Ivy. Puede agrupar
dependencias.
• Cambia la nomenclatura de ámbito (por ejemplo
compile = compile + runtime)
Wednesday, April 25, 12
26. Round 6
• Soporte IDE
• Maven: tiene soporte para Netbeans, Eclipse,
Intellij
• Gradle: tiene soporte para Netbeans
(limitado), Eclipse (STS) e Intellij
Wednesday, April 25, 12
28. Round 7
• Multiproyecto
• Maven:
• Se puede declarar un pom.xml “padre” y luego los
pom.xml de cada proyecto. Heredamos configuraciones
de plugins y propiedades
• Gradle:
• Se separa la declaracion de hijos de las configuraciones
de herencia. Decoupling. (build.gradle/settings.gradle)
Wednesday, April 25, 12
29. Resultado
Gradle Maven
Convencion Vs Conf
Ciclo de Vida
Xml vs Código
Scripting
Dependencias
Multiproject
IDE
Wednesday, April 25, 12
31. Por donde empezar
• Página del proyecto
• http://www.gradle.org
• Wiki:
• http://wiki.gradle.org/display/GRADLE/Home
• Libros:
• Building And Testing with Gradle (O’Reilly)
• Se puede leer online a través de la página de Gradle
Wednesday, April 25, 12