The document summarizes the author's learning journey through visual arts and creativity. It quotes several influential figures who emphasize taking risks, freedom of expression, and learning through doing. The document encourages embarking on new and unfamiliar creative paths to smile, reflect, inspire, and more. It provides credits for the photos and music used.
The document summarizes the author's learning journey through visual arts and creativity. It quotes several influential figures who emphasize taking risks, freedom of expression, and learning through doing. The document encourages embarking on new and unfamiliar creative paths to smile, reflect, inspire, and more. It provides credits for the photos and music used.
Droid con 2013 workshop unit testing in android [robolectirc]Leena N
This document discusses unit testing Android applications. It introduces Robolectric, an emulation framework that runs unit tests for Android apps on a Java Virtual Machine instead of an emulator or device. This allows tests to run much faster. Robolectric emulates the Android SDK and resources using shadow objects and view/resource loading. It is easy to extend and has good community support. While useful for unit testing, it cannot replace integrated tests that run on actual devices.
This document discusses the culture of continuous delivery. It promotes building quality in from the start, keeping the build always deployable, and continuous improvement. Continuous delivery aspects include automating the build, having a deployable build, continuous integration, build pipelines, configuration management, release management, and using Kanban and feature toggles. Practicing continuous delivery leads to a great culture with values like delighted customers and software craftsmanship. It also discusses concepts from neuroscience like how the brain reacts to stress and rewards that relate to continuous delivery practices.
This document discusses different types of testing tools, including unit testing tools like Jasmine and Mocha that allow for quick feedback during test-driven development, end-to-end testing tools like Selenium and Protractor that simulate user interactions, contract testing tools like Pact that test design contracts, and screenshot comparison tools like Wraith and Resemble.js for visual regression testing. It also mentions that unit tests should have high value but low maintenance, end-to-end tests have high effort for maintenance, and that testing strategies should follow the testing pyramid with more unit and integration tests than end-to-end tests.
This document discusses the importance of continuous delivery using Jenkins. It introduces continuous integration and continuous delivery, explaining that continuous integration provides fast feedback on code changes while continuous delivery provides feedback on production readiness. It outlines how to set up a build pipeline in Jenkins to guarantee production readiness and make releases risk-free and automated. The document emphasizes that continuous delivery satisfies customers through early and frequent delivery of software and encourages teams to take responsibility for releases through continuous improvement.
This presentation shows how to create a pipeline in Jenkins CI server for push button deployment. It demonstrates the different tools used for the same and also what are the advantages of having a build pipeline
This document discusses impact mapping as a technique for delivering projects with impact. It provides an example of impact mapping for an MDM (mobile device management) product. The key steps of impact mapping include: defining goals and who they impact; identifying desired behaviors and how to enable them; establishing metrics to measure impact; and planning milestones to test assumptions. Impact mapping focuses on creating actual behavioral change rather than just shipping software.