Unit testing and Android
2 likes1,865 views
This document discusses various types of tests for Android applications, including instrumentation tests, which run on an emulator or physical device, and unit tests, which run on a JVM without Android dependencies. It covers challenges with instrumentation tests like speed and dependencies on the device state. The document recommends writing business logic separately from UI code to make it more testable. It also provides information on frameworks like Robolectric, Mockito, and JaCoCo that can help with unit testing and code coverage of Android applications.
1 of 61
Downloaded 33 times
![Potential problems
• Manifest merger
• problems when testing libraries
• aar dependency using manifest placeholders
• e.g. ${applicationId}, ${localApplicationId}
android {
defaultConfig {
manifestPlaceholders =
[localApplicationId:”com.example.mylib”]
}
}](https://image.slidesharecdn.com/unittestingandandroidwithreferences-150628165206-lva1-app6892/85/Unit-testing-and-Android-17-320.jpg)
Ad
Recommended
Learn How to Unit Test Your Android Application (with Robolectric)
Learn How to Unit Test Your Android Application (with Robolectric)Marakana Inc. The document discusses the Android unit test framework Robolectric. It provides an overview of Robolectric, including how it works by using shadow objects to simulate the Android framework classes, allowing tests to run on a normal JVM. It also covers how to get started with Robolectric by using the sample project, and how to write tests by accessing shadow objects and dealing with classes that don't expose full state.
Unit Testing Android Applications
Unit Testing Android ApplicationsRody Middelkoop The document discusses effective unit testing strategies for Android, emphasizing the importance of automation, writing tests first, and utilizing various test doubles like mocks and stubs. It highlights the use of frameworks such as Mockito and Robolectric to facilitate testing while addressing common issues like slow tests and dependencies on specific platforms. The document concludes with recommendations for good testing practices and resources for further reading.
Testing on Android
Testing on AndroidAri Lacenski The document covers best practices for testing Android applications, including the use of testing libraries such as JUnit, Robolectric, and Robotium. It emphasizes the importance of Test-Driven Development (TDD) and Behavior-Driven Development (BDD) to ensure reliable and maintainable code. Additionally, it details the integration of Continuous Integration (CI) systems like Jenkins to automate testing and deployment processes.
Testing for Android: When, Where, and How to Successfully Use Test Automation
Testing for Android: When, Where, and How to Successfully Use Test AutomationTrent Peterson The document discusses the importance of test automation in Android development, outlining the various types of tests and best practices for implementation. It highlights the challenges of building applications and the need to choose effective automation strategies to save time and resources. Additionally, different testing tools and frameworks are presented, along with their advantages and disadvantages.
How to setup unit testing in Android Studio
How to setup unit testing in Android Studiotobiaspreuss The document describes the steps to set up unit testing in an Android project using Android Studio, Robolectric, and JUnit. It includes adding dependencies for Robolectric and JUnit to the app/build.gradle file, applying the Robolectric Gradle plugin, creating a test folder and sample test class, and configuring the project structure and IDE integration so tests can be run from Android Studio.
Android testing
Android testingBitbar The document discusses strategies for coping with device fragmentation in Android testing, emphasizing tools and approaches offered by Bitbar, including Testdroid Recorder and Testdroid Server. It highlights problems faced by developers, like application failures and layout issues, and provides solutions through automated testing frameworks like Robotium and Robolectric. Best practices for testing ensure comprehensive coverage across devices and encourage developers to integrate test case creation with code development.
Android testing
Android testingJinaTm The document outlines various testing approaches for Android applications, including unit testing, integration testing, manual testing, and automated testing frameworks. It discusses tools such as Espresso, Robotium, and UI Automator, highlighting their features and comparisons, as well as the Android testing API and its components. Additionally, it details the key characteristics of Android testing frameworks and libraries and provides references for further reading.
Robotium Tutorial
Robotium TutorialMobile March This document provides an overview of Robotium, an open source test framework for Android. The presentation covers what Robotium is, how to set it up, why it's needed compared to standard Android testing, how to write tests using the Robotium Solo API, tips and tricks, and additional resources. The purpose of Robotium is to simplify Android testing by providing instrumentation of UI components without needing deep knowledge of Android internals or how the app works.
Android Automation Using Robotium
Android Automation Using RobotiumMindfire Solutions The document provides an overview of Android automation using Robotium, including its features, limitations, requirements, and setup instructions. Robotium enables writing automation scripts for both native and hybrid Android applications, with support for various UI elements and testing environments. The document also discusses project workflow, developing test scripts, and integration with build tools and CI servers.
Inside Android Testing
Inside Android TestingFernando Cejas The document outlines the importance of testing in software development, particularly in Android applications, and discusses various testing tools such as JUnit, Mockito, and Robolectric. It emphasizes that testing boosts confidence in code quality and enables safe refactoring. Additionally, it lists concepts like dependency injection and continuous integration while encouraging developers to adopt testing practices.
Android Testing: An Overview
Android Testing: An OverviewSmartLogic This document provides an overview of testing Android applications. It discusses using Robolectric to run tests on a development machine without needing an emulator. It also recommends libraries like Hamcrest, FEST Android, and Awaitility to improve testing. Spoon is presented as a tool to take screenshots during tests. Continuous integration with Jenkins and generating test reports and documentation are also covered.
Robotium - sampath
Robotium - sampathSampath Muddineni The document outlines the Robotium test framework, which is an open-source tool for black box testing of Android applications. It provides guidance on setting up the framework, writing tests using the Robotium API, and offers tips and tricks for effective testing. Additionally, it highlights the benefits of using Robotium, including ease of writing tests and automatic handling of Android activity states.
Efficient JavaScript Unit Testing, JavaOne China 2013
Efficient JavaScript Unit Testing, JavaOne China 2013Hazem Saleh The document discusses the importance of unit testing in JavaScript development, highlighting the complexities and challenges developers face without it. It introduces jstestdriver as a powerful tool that meets key requirements for effective unit testing, including support for multiple browsers and integration with IDEs. Additionally, it covers writing test cases, generating reports, and managing test execution efficiently.
[AnDevCon 2016] Mutation Testing for Android
[AnDevCon 2016] Mutation Testing for AndroidHazem Saleh The document presents a comprehensive overview of mutation testing, focusing on its significance, techniques, and tools applicable in Android development. It discusses unit testing essentials, challenges of traditional code coverage, and introduces the Pit mutation testing tool, including integration tips for Android projects. The author, Hazem Saleh, emphasizes the need for robust unit tests to enhance application quality and reduce defects.
Selenium Automation Testing Interview Questions And Answers
Selenium Automation Testing Interview Questions And AnswersAjit Jadhav This document contains 30 interview questions and answers related to Selenium testing. Some of the key questions covered include how to start the Selenium server from code, how to handle multiple browser windows, locate elements and verify text, connect to databases, and use Selenium Grid for parallel testing across different machines. The answers provide technical details on using Selenium commands, locators, and programming techniques.
Efficient JavaScript Unit Testing, May 2012
Efficient JavaScript Unit Testing, May 2012Hazem Saleh The document discusses the significance of unit testing in JavaScript development, emphasizing its benefits such as early detection of defects, improved application quality, and reduced testing cycles. It introduces jstestdriver as an effective open-source tool for unit testing, detailing its architecture, configuration, and features like compatibility with various frameworks and report generation capabilities. The author, Hazem Saleh, is a software engineer with extensive experience and contributions to the field, advocating for the importance of effective testing in software development.
Top trending selenium interview questions
Top trending selenium interview questionsRock Interview The document lists top trending Selenium interview questions relevant for automation testing roles, emphasizing the high demand for testing professionals. Key topics include the usage of XPath, differences between assert and verify, and handling web-based pop-ups. It recommends the Rock Interview app for further preparation and practice with industry experts.
Android with dagger_2
Android with dagger_2Kros Huang The document discusses dependency injection and Dagger 2. It explains that dependency injection is a design pattern where dependencies are provided to classes rather than having classes create their own dependencies. Dagger 2 uses modules annotated with @Module to provide dependencies, with methods annotated with @Provides. Classes request dependencies using @Inject. A component provides a bridge between modules and injection points so they can work together. The document provides examples of using Dagger 2 to define modules that provide dependencies and inject them into classes.
Introduction to Protractor - Habilelabs
Introduction to Protractor - HabilelabsHabileLabs This document provides an overview of end-to-end testing with Protractor. It defines end-to-end testing as testing whether the flow of an application performs as designed from start to finish. The document then discusses Protractor, an end-to-end test framework for AngularJS, how it works by using WebDriverJS and Selenium, and its advantages like automatic waiting and support for page objects. Finally, the document provides instructions on installing Protractor and a demo of running tests.
Test Automation On Android Platform Using Robotium
Test Automation On Android Platform Using RobotiumIndicThreads The document discusses test automation on the Android platform using Robotium, outlining its features, limitations, and future enhancements. It covers the Android testing framework, prerequisites for creating test projects, and provides sample test case instrumentation code. Key limitations of Robotium include its inability to support flash and web-based applications, and its non-functionality on canvas.
Reliable mobile test automation
Reliable mobile test automationVishal Banthia This document summarizes Vishal Banthia's presentation on achieving reliable mobile test automation. It discusses the difficulties of flaky tests and inconsistent test execution environments. It then presents solutions like capturing comprehensive test reports with screenshots, videos, and logs to better diagnose flaky tests. It also recommends leveraging cloud services for scalable and accessible test execution. The presentation demonstrates these concepts through tools like Bitrise, OpenSTF, and CircleCI used in Mercari's mobile test automation pipeline.
Realtime selenium interview questions
Realtime selenium interview questionsKuldeep Pawar The document contains interview questions from various companies like HCL, Emids, Manhattan, 3PLM, Zolipe Solutions, Synchronoss, and Cognizant for positions ranging from 2-3 years of experience in Selenium testing. The questions cover a wide range of topics including Selenium, manual testing, Java, SQL, algorithms, data structures and design patterns. Common questions asked relate to frameworks, test automation lifecycles, handling dynamic elements, test case design techniques, and debugging skills.
Getting Started with XCTest and XCUITest for iOS App Testing
Getting Started with XCTest and XCUITest for iOS App TestingBitbar The document outlines a webinar on getting started with XCTest and XCUItest for iOS app testing, covering frameworks, tools, and methods. It highlights the benefits and limitations of XCTest and XCUItest, provides examples of test methods, and details on creating .ipa files for testing. Additionally, it compares various iOS test automation frameworks, emphasizing the key features of XCTest and XCUItest.
The Test way
The Test wayMikhail Grinfeld The document discusses different types of software testing including unit tests, component tests, integration tests, and test-driven development (TDD).
It provides definitions and examples of unit tests and how they are used to test individual functions or methods in isolation. It also discusses JUnit and how it is used for writing unit tests in Java.
The document then covers component tests, which test larger logical units or modules that combine multiple classes. It provides an example of component tests for a Spring Boot application.
Other topics covered include test-driven development (TDD) and the red-green-yellow process, public vs private tests and maintainability, and who tests the testers through mutation testing. Finally, it
Unit-testing and E2E testing in JS
Unit-testing and E2E testing in JSMichael Haberman Unit testing and end-to-end (E2E) testing are important types of automated testing for JavaScript applications. Unit tests focus on testing individual functions or components in isolation to catch bugs, while E2E tests ensure that user flows work as expected by interacting with the application through a browser. The presentation discussed setting up testing frameworks like Karma and Jasmine for unit testing and Protractor for E2E testing. It also covered writing testable code, handling dependencies through dependency injection, and selecting elements and interacting with them during E2E tests.
Codeception introduction and use in Yii
Codeception introduction and use in YiiIlPeach This document presents an introduction to Codeception and its application in Yii, emphasizing its modular design aimed at simplifying the testing process across various test types including acceptance, functional, and unit tests. It outlines the steps to set up Codeception within a Yii environment, discusses the different testing approaches, and provides a basic example of an acceptance test. The presenter encourages the adoption of testing as part of a quality assurance strategy and offers resources for further guidance.
How do you tame a big ball of mud? One test at a time.
How do you tame a big ball of mud? One test at a time.Matt Eland The document discusses strategies for improving unit testing in legacy systems, focusing on techniques to enhance testability and refactor code. It emphasizes building safety nets, reducing dependencies, and utilizing various tools and frameworks for effective testing. Key tools mentioned include NUnit, Autofac, Moq, and SpecFlow, with links provided for further resources and code examples.
Principles and patterns for test driven development
Principles and patterns for test driven developmentStephen Fuqua The document discusses principles and patterns for Test Driven Development (TDD), emphasizing the importance of testing for risk reduction, better design, and ensuring software functionality. Key topics include writing expressive tests, user stories, isolation in testing, essential object-oriented patterns, and handling legacy code. It concludes with resources and strategies for overcoming obstacles in implementing TDD effectively.
Introduction to android testing
Introduction to android testingDiego Torres Milano The document discusses different types of tests for Android applications including unit tests, functional tests, integration tests, and performance tests. It covers testing frameworks and tools like JUnit, FitNesse, and AndroidTestCase that can be used to write and run tests at the unit and integration level. The goal of testing is to ensure applications work as intended across all components of the system in a repeatable way.
Android & iPhone App Testing
Android & iPhone App TestingSWAAM Tech The document provides an overview of Android and iPhone applications, highlighting their differences, key features, and the importance of mobile application testing. It outlines various testing types, including unit, integration, functional, performance, compatibility, load, stress, regression, and security testing. The document emphasizes the necessity of ensuring a positive user experience through comprehensive testing strategies and methodologies tailored for mobile devices.
More Related Content
What's hot (20)
Android Automation Using Robotium
Android Automation Using RobotiumMindfire Solutions The document provides an overview of Android automation using Robotium, including its features, limitations, requirements, and setup instructions. Robotium enables writing automation scripts for both native and hybrid Android applications, with support for various UI elements and testing environments. The document also discusses project workflow, developing test scripts, and integration with build tools and CI servers.
Inside Android Testing
Inside Android TestingFernando Cejas The document outlines the importance of testing in software development, particularly in Android applications, and discusses various testing tools such as JUnit, Mockito, and Robolectric. It emphasizes that testing boosts confidence in code quality and enables safe refactoring. Additionally, it lists concepts like dependency injection and continuous integration while encouraging developers to adopt testing practices.
Android Testing: An Overview
Android Testing: An OverviewSmartLogic This document provides an overview of testing Android applications. It discusses using Robolectric to run tests on a development machine without needing an emulator. It also recommends libraries like Hamcrest, FEST Android, and Awaitility to improve testing. Spoon is presented as a tool to take screenshots during tests. Continuous integration with Jenkins and generating test reports and documentation are also covered.
Robotium - sampath
Robotium - sampathSampath Muddineni The document outlines the Robotium test framework, which is an open-source tool for black box testing of Android applications. It provides guidance on setting up the framework, writing tests using the Robotium API, and offers tips and tricks for effective testing. Additionally, it highlights the benefits of using Robotium, including ease of writing tests and automatic handling of Android activity states.
Efficient JavaScript Unit Testing, JavaOne China 2013
Efficient JavaScript Unit Testing, JavaOne China 2013Hazem Saleh The document discusses the importance of unit testing in JavaScript development, highlighting the complexities and challenges developers face without it. It introduces jstestdriver as a powerful tool that meets key requirements for effective unit testing, including support for multiple browsers and integration with IDEs. Additionally, it covers writing test cases, generating reports, and managing test execution efficiently.
[AnDevCon 2016] Mutation Testing for Android
[AnDevCon 2016] Mutation Testing for AndroidHazem Saleh The document presents a comprehensive overview of mutation testing, focusing on its significance, techniques, and tools applicable in Android development. It discusses unit testing essentials, challenges of traditional code coverage, and introduces the Pit mutation testing tool, including integration tips for Android projects. The author, Hazem Saleh, emphasizes the need for robust unit tests to enhance application quality and reduce defects.
Selenium Automation Testing Interview Questions And Answers
Selenium Automation Testing Interview Questions And AnswersAjit Jadhav This document contains 30 interview questions and answers related to Selenium testing. Some of the key questions covered include how to start the Selenium server from code, how to handle multiple browser windows, locate elements and verify text, connect to databases, and use Selenium Grid for parallel testing across different machines. The answers provide technical details on using Selenium commands, locators, and programming techniques.
Efficient JavaScript Unit Testing, May 2012
Efficient JavaScript Unit Testing, May 2012Hazem Saleh The document discusses the significance of unit testing in JavaScript development, emphasizing its benefits such as early detection of defects, improved application quality, and reduced testing cycles. It introduces jstestdriver as an effective open-source tool for unit testing, detailing its architecture, configuration, and features like compatibility with various frameworks and report generation capabilities. The author, Hazem Saleh, is a software engineer with extensive experience and contributions to the field, advocating for the importance of effective testing in software development.
Top trending selenium interview questions
Top trending selenium interview questionsRock Interview The document lists top trending Selenium interview questions relevant for automation testing roles, emphasizing the high demand for testing professionals. Key topics include the usage of XPath, differences between assert and verify, and handling web-based pop-ups. It recommends the Rock Interview app for further preparation and practice with industry experts.
Android with dagger_2
Android with dagger_2Kros Huang The document discusses dependency injection and Dagger 2. It explains that dependency injection is a design pattern where dependencies are provided to classes rather than having classes create their own dependencies. Dagger 2 uses modules annotated with @Module to provide dependencies, with methods annotated with @Provides. Classes request dependencies using @Inject. A component provides a bridge between modules and injection points so they can work together. The document provides examples of using Dagger 2 to define modules that provide dependencies and inject them into classes.
Introduction to Protractor - Habilelabs
Introduction to Protractor - HabilelabsHabileLabs This document provides an overview of end-to-end testing with Protractor. It defines end-to-end testing as testing whether the flow of an application performs as designed from start to finish. The document then discusses Protractor, an end-to-end test framework for AngularJS, how it works by using WebDriverJS and Selenium, and its advantages like automatic waiting and support for page objects. Finally, the document provides instructions on installing Protractor and a demo of running tests.
Test Automation On Android Platform Using Robotium
Test Automation On Android Platform Using RobotiumIndicThreads The document discusses test automation on the Android platform using Robotium, outlining its features, limitations, and future enhancements. It covers the Android testing framework, prerequisites for creating test projects, and provides sample test case instrumentation code. Key limitations of Robotium include its inability to support flash and web-based applications, and its non-functionality on canvas.
Reliable mobile test automation
Reliable mobile test automationVishal Banthia This document summarizes Vishal Banthia's presentation on achieving reliable mobile test automation. It discusses the difficulties of flaky tests and inconsistent test execution environments. It then presents solutions like capturing comprehensive test reports with screenshots, videos, and logs to better diagnose flaky tests. It also recommends leveraging cloud services for scalable and accessible test execution. The presentation demonstrates these concepts through tools like Bitrise, OpenSTF, and CircleCI used in Mercari's mobile test automation pipeline.
Realtime selenium interview questions
Realtime selenium interview questionsKuldeep Pawar The document contains interview questions from various companies like HCL, Emids, Manhattan, 3PLM, Zolipe Solutions, Synchronoss, and Cognizant for positions ranging from 2-3 years of experience in Selenium testing. The questions cover a wide range of topics including Selenium, manual testing, Java, SQL, algorithms, data structures and design patterns. Common questions asked relate to frameworks, test automation lifecycles, handling dynamic elements, test case design techniques, and debugging skills.
Getting Started with XCTest and XCUITest for iOS App Testing
Getting Started with XCTest and XCUITest for iOS App TestingBitbar The document outlines a webinar on getting started with XCTest and XCUItest for iOS app testing, covering frameworks, tools, and methods. It highlights the benefits and limitations of XCTest and XCUItest, provides examples of test methods, and details on creating .ipa files for testing. Additionally, it compares various iOS test automation frameworks, emphasizing the key features of XCTest and XCUItest.
The Test way
The Test wayMikhail Grinfeld The document discusses different types of software testing including unit tests, component tests, integration tests, and test-driven development (TDD).
It provides definitions and examples of unit tests and how they are used to test individual functions or methods in isolation. It also discusses JUnit and how it is used for writing unit tests in Java.
The document then covers component tests, which test larger logical units or modules that combine multiple classes. It provides an example of component tests for a Spring Boot application.
Other topics covered include test-driven development (TDD) and the red-green-yellow process, public vs private tests and maintainability, and who tests the testers through mutation testing. Finally, it
Unit-testing and E2E testing in JS
Unit-testing and E2E testing in JSMichael Haberman Unit testing and end-to-end (E2E) testing are important types of automated testing for JavaScript applications. Unit tests focus on testing individual functions or components in isolation to catch bugs, while E2E tests ensure that user flows work as expected by interacting with the application through a browser. The presentation discussed setting up testing frameworks like Karma and Jasmine for unit testing and Protractor for E2E testing. It also covered writing testable code, handling dependencies through dependency injection, and selecting elements and interacting with them during E2E tests.
Codeception introduction and use in Yii
Codeception introduction and use in YiiIlPeach This document presents an introduction to Codeception and its application in Yii, emphasizing its modular design aimed at simplifying the testing process across various test types including acceptance, functional, and unit tests. It outlines the steps to set up Codeception within a Yii environment, discusses the different testing approaches, and provides a basic example of an acceptance test. The presenter encourages the adoption of testing as part of a quality assurance strategy and offers resources for further guidance.
How do you tame a big ball of mud? One test at a time.
How do you tame a big ball of mud? One test at a time.Matt Eland The document discusses strategies for improving unit testing in legacy systems, focusing on techniques to enhance testability and refactor code. It emphasizes building safety nets, reducing dependencies, and utilizing various tools and frameworks for effective testing. Key tools mentioned include NUnit, Autofac, Moq, and SpecFlow, with links provided for further resources and code examples.
Principles and patterns for test driven development
Principles and patterns for test driven developmentStephen Fuqua The document discusses principles and patterns for Test Driven Development (TDD), emphasizing the importance of testing for risk reduction, better design, and ensuring software functionality. Key topics include writing expressive tests, user stories, isolation in testing, essential object-oriented patterns, and handling legacy code. It concludes with resources and strategies for overcoming obstacles in implementing TDD effectively.
Viewers also liked (20)
Introduction to android testing
Introduction to android testingDiego Torres Milano The document discusses different types of tests for Android applications including unit tests, functional tests, integration tests, and performance tests. It covers testing frameworks and tools like JUnit, FitNesse, and AndroidTestCase that can be used to write and run tests at the unit and integration level. The goal of testing is to ensure applications work as intended across all components of the system in a repeatable way.
Android & iPhone App Testing
Android & iPhone App TestingSWAAM Tech The document provides an overview of Android and iPhone applications, highlighting their differences, key features, and the importance of mobile application testing. It outlines various testing types, including unit, integration, functional, performance, compatibility, load, stress, regression, and security testing. The document emphasizes the necessity of ensuring a positive user experience through comprehensive testing strategies and methodologies tailored for mobile devices.
Android Unit Tesing at I/O rewind 2015
Android Unit Tesing at I/O rewind 2015Somkiat Puisungnoen The document discusses various techniques for testing Android applications including:
- Unit testing with JUnit and Espresso - Provides examples of finding views, performing actions, and checking states
- Monkey testing - A command line tool that generates random events to test app stability
- Useful resources like sample code from Google are provided to help developers learn Android testing
Testing With Open Source
Testing With Open SourceMatthias Käppler This document summarizes a 1 hour workshop on testing Android applications with open source tools. It discusses writing Android tests with JUnit, running tests with Instrumentation, using Maven for build management and automation, and integrating with Hudson for continuous integration. Examples are provided for writing and running tests in AndroidTestCase and InstrumentationTestCase, and using the Maven Android plugin and Hudson build server.
Unit testing on Android (Droidcon Dubai 2015)
Unit testing on Android (Droidcon Dubai 2015)Danny Preussler The document discusses unit testing in Android development, highlighting the importance of testing code to ensure functionality and maintainability. It outlines methods for writing tests, tools like Robolectric, and best practices for structuring tests effectively. Additionally, it emphasizes the necessity for clean code and dependency injection to facilitate testing.
How ANDROID TESTING changed how we think about Death - Second Edition
How ANDROID TESTING changed how we think about Death - Second Editionpenanochizzo The document discusses the importance of testing in Android development, highlighting its role in increasing code confidence and enabling safe refactoring. It introduces various testing types, frameworks like Mockito and Robolectric, and best practices for a robust testing strategy. The presentation emphasizes the use of tools for automation and continuous integration to enhance testing effectiveness.
Mobile Performance Testing - Best Practices
Mobile Performance Testing - Best PracticesEran Kinsbrunner The document discusses best practices for mobile performance testing to enhance enterprise mobility and software quality, highlighting the importance of understanding and optimizing mobile user experiences. It outlines key requirements for effective mobile performance testing, including measuring user-facing KPIs across diverse devices and network conditions. The document emphasizes the critical impact of performance on customer satisfaction and brand loyalty, along with practical recommendations for identifying and addressing performance bottlenecks.
Testing on Android
Testing on AndroidDiego Torres Milano The document provides an overview of testing on Android. It discusses test driven development (TDD) and behavior driven development (BDD). It describes the built-in Android testing framework, which is based on JUnit 3 and supports unit, functional, and activity tests. It outlines various test case types like ActivityInstrumentationTestCase2 that can be used to test Activities. It also documents utilities for writing tests, such as TouchUtils for simulating user interactions and ViewAsserts for making assertions about Views. The document guides the reader through an example of setting up an Android project and test project to apply TDD techniques.
TDD with AngularJS
TDD with AngularJSLeena N The document discusses the importance of Test Driven Development (TDD) using AngularJS, highlighting tools like Jasmine and Karma for implementation. It emphasizes the benefits of TDD in building quality software, maintaining focus, and measuring progress while also incorporating elements of fun in the process. Additionally, it mentions job opportunities and provides references for further reading.
Droid con 2013 workshop unit testing in android [robolectirc]
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.
Robolectric Android Unit Testing Framework
Robolectric Android Unit Testing Frameworktylerschultz Robolectric is a unit test framework that de-fangs the Android SDK jar so you can test-drive the development of your Android app.
7 stages of unit testing
7 stages of unit testingJorge Ortiz The document presents a comprehensive overview of the 7 stages of unit testing in Android, highlighting the importance of unit tests in ensuring code correctness and facilitating easier refactoring. Each stage, from shock and denial to acceptance and hope, addresses common emotions and challenges faced by developers in the testing process, providing guidelines on writing effective tests, using dependency injection, and employing testing frameworks like JUnit. The content emphasizes the need for gradual implementation and the benefits of incorporating testing as part of the development lifecycle for improved code quality.
How To Improve Your Product Testing Program
How To Improve Your Product Testing ProgramThe DRG (The Dieringer Research Group) The Dieringer Research Group specializes in product testing and market research, addressing common pitfalls in product development that lead to high failure rates. Through customized research strategies tailored to clients' specific needs, the group aims to enhance product performance, ensure market fit, and improve overall brand reputation. The document emphasizes the importance of ongoing testing throughout the product development cycle to identify issues early and maximize investment effectiveness.
Product Testing and Refinement
Product Testing and RefinementChris Cera The document outlines the process of product testing and refining through the scientific method, emphasizing hypothesis formation and testing with customer input. It details budget challenges for testing product names and user sign-in methods, highlighting funnel analysis for customer engagement and A/B testing results. The document concludes with a collaborative assignment for optimization and testing among participants.
Product testing methodology & how to conduct a product test
Product testing methodology & how to conduct a product testVINAMR - Vietnam Marketing Research & Consultants Product tests can be categorized based on what is being evaluated, such as sensory tests for food and drink or usage tests for products like pharmaceuticals and cleaners. Tests are also categorized based on their marketing objective, such as determining if consumers can detect changes in re formulations or assessing new products. Product tests are typically conducted using quantitative research methods and ideally take place where the product would normally be used, though central locations are also often used for control and practicality. The length of trials depends on typical usage patterns but extended trials over longer periods may be necessary for some products like appliances.
A guide to Android automated testing
A guide to Android automated testingjotaemepereira The document discusses best practices for automated Android testing, including testing utilities, Android components, the UI, and expected user behavior. It recommends using support libraries like Instrumentation, Android JUnit Runner, Espresso, and UIAutomator for testing. Espresso allows testing UI interactions within an app, while UIAutomator can test interactions between apps and the system. Tests should be decoupled and use stubs for dependencies that can't be controlled. Everything that could cause errors, like getter/setters, should be tested.
Testing Android Security
Testing Android SecurityJose Manuel Ortega Candel Este documento resume diferentes técnicas y herramientas para realizar análisis de seguridad en aplicaciones móviles Android. Cubre análisis estático utilizando Lint, SonarQube y otras herramientas, así como análisis dinámico mediante el monitoreo de red, llamadas y logs. También discute temas como el cifrado, almacenamiento seguro de datos, detección de root, ofuscación y marcos como OWASP Mobile Top 10.
Product Testing: Methodological Issues & Design Considerations
Product Testing: Methodological Issues & Design ConsiderationsT.S. Lim The document discusses product testing methodologies crucial for fast-moving consumer goods (FMCG), emphasizing the importance of consumer evaluation in product development and optimization. It outlines various testing designs such as unbranded vs. branded tests and monadic vs. sequential approaches, along with considerations for utilizing central location tests versus in-home use tests. Key areas of focus include aligning research objectives with stage development, capturing consumer feedback, and ensuring quality assurance throughout the product's lifecycle.
Introduction to android testing - oscon 2012
Introduction to android testing - oscon 2012OSCON Byrum The document discusses testing for Android applications. It covers different types of tests like unit tests, functional tests, integration tests and performance tests. It also discusses test frameworks in Android like InstrumentationTestCase, AndroidTestCase and ActivityInstrumentationTestCase2. The rest of the document talks about test driven development and how to write tests for an Android temperature converter application.
Android Performance Tips & Tricks
Android Performance Tips & TricksSergii Zhuk The document provides a comprehensive overview of best practices for optimizing Android application performance, including advice on effective coding techniques, layout efficiency, and resource management. Key topics include the use of primitives, layout strategies, memory leak detection through LeakCanary, and employing developer tools for performance measurement. It also emphasizes the importance of developing for low-end devices and offers specific tools and methods to streamline applications.
Product testing methodology & how to conduct a product test
Product testing methodology & how to conduct a product testVINAMR - Vietnam Marketing Research & Consultants
Ad
Similar to Unit testing and Android (20)
Guide to the jungle of testing frameworks
Guide to the jungle of testing frameworksTomáš Kypta The document serves as a comprehensive guide to testing frameworks for Android applications, detailing various testing types including unit tests and instrumentation tests, along with their respective setup and execution. It covers the use of testing libraries such as JUnit and Espresso, addressing challenges in device-based testing and providing examples of test implementations. Additionally, it highlights best practices for effective testing, including maintaining isolation and speed in tests while separating business logic from UI components.
Enterprise Strength Mobile JavaScript
Enterprise Strength Mobile JavaScriptTroy Miles The document discusses the importance and challenges of JavaScript, covering its history, best practices, unit testing, and debugging techniques. It outlines issues like browser wars and the difficulties in writing quality JavaScript code, while emphasizing the need for proper tools and practices. The document also lists resources for unit testing and debugging methods, encouraging developers to adopt best practices and be pragmatic in their approach.
How to Build Your Own Test Automation Framework?
How to Build Your Own Test Automation Framework?Dmitry Buzdin The document provides a detailed guide on building a test automation framework, emphasizing requirements like minimal cost of ownership, integration with existing tools, and transparency. It discusses the distinction between frameworks and libraries, outlines essential components such as test libraries, test cases, and assertion strategies, and introduces various technologies involved like JUnit 5 and Cucumber. Additionally, it highlights the importance of logging, reporting, and configuration, concluding with a call to action for test automation enthusiasts.
LDNSE: Testdroid for Mobile App and Web Testing (London Selenium Meetup)
LDNSE: Testdroid for Mobile App and Web Testing (London Selenium Meetup)Bitbar The document presents various mobile app testing solutions provided by Bitbar, including Testdroid cloud, enterprise, and private cloud options for automated testing on real devices. It discusses the importance of real-device testing over emulation, the benefits of test automation, and categorizes different testing types and strategies. Additionally, it outlines various mobile testing frameworks and provides insights into test script execution from client-side to cloud-based environments.
Testing Angular
Testing AngularLilia Sfaxi Unit testing and end-to-end testing are important for Angular applications. The document discusses various types of tests, including unit tests, integration tests, and end-to-end tests. It also covers tools for testing Angular applications, such as Jasmine for writing unit tests, Karma as a test runner, Protractor for end-to-end tests, and Angular testing utilities. The document provides recommendations on testing components and services, including how to set up tests and write tests with dependencies.
Play with Testing on Android - Gilang Ramadhan (Academy Content Writer at Dic...
Play with Testing on Android - Gilang Ramadhan (Academy Content Writer at Dic...DicodingEvent The document outlines best practices for testing in Android development, emphasizing the use of Android Jetpack libraries to simplify code management and reduce bugs. It discusses the importance of test-driven development (TDD) and various testing methodologies, including unit tests, integration tests, and end-to-end tests, highlighting the advantages of a well-structured testing approach. Additionally, it covers the use of dependency injection and test doubles to create a testable architecture, ultimately aiming to improve code quality and development efficiency.
Testing Ext JS and Sencha Touch
Testing Ext JS and Sencha TouchMats Bryntse - Testing JavaScript code helps ensure quality and allows for refactoring and code handovers. Unit, integration, and functional testing methodologies were discussed.
- Siesta was introduced as a JavaScript testing tool that supports unit and functional testing for Ext JS and Sencha Touch. It allows simulating user interactions and verifying results.
- Writing testable code through separation of concerns, avoiding direct DOM manipulation, and supporting dependency injection were recommended to facilitate automated testing. Continuous integration was also recommended for running tests regularly.
Qt test framework
Qt test frameworkICS QtTest is a unit testing framework that comes with Qt. It provides classes and methods for building test fixtures to test units of code. QtTest allows testing signals without needing to write slots using QSignalSpy. It can also simulate user events like mouse clicks and key presses. While QtTest is useful for unit testing, it does not provide isolation of dependencies between units. Tests using QtTest should focus on testing one thing at a time and creating new objects for each test to isolate the code being tested.
Robotium at Android Only 2010-09-29
Robotium at Android Only 2010-09-29Hugo Josefson The document discusses Robotium, an open-source framework for black-box testing of Android applications, comparing it to traditional instrumentation testing methods. It highlights the advantages of Robotium, such as simplified test writing and automated actions, while also noting limitations tied to JUnit 3 and specific app processes. Additionally, it covers the integration of Robotium with Maven for project management and outlines future features planned for the framework.
Java script unit testing
Java script unit testingMats Bryntse This document discusses the importance of unit testing JavaScript code. It provides reasons for testing JavaScript, such as avoiding bugs when refactoring code or introducing errors. The document discusses how to write testable JavaScript by separating business logic from views. It also recommends choosing JavaScript unit testing tools like Jasmine and Siesta, and integrating tests into continuous integration processes to run automatically on commits. Functional testing tools like Selenium are also mentioned for testing user interactions across browsers.
Test it! Unit, mocking and in-container Meet Arquillian!
Test it! Unit, mocking and in-container Meet Arquillian!Ivan Ivanov The document outlines the principles and processes of unit testing, emphasizing the use of the JUnit framework and mocking libraries like Mockito within container environments using Arquillian. It elaborates on the benefits and limitations of unit testing, providing guidance on test preparation, execution, and the importance of dependency injection. Additionally, it offers a structured five-step approach to connecting, packaging, and running tests in various container platforms.
33rd degree
33rd degreeDariusz Kordonski The document discusses challenges faced with automated testing at scale for a large codebase with many dependencies, technologies, and test types. It describes how the large number of tests led to slow build times, failures blocking changes, and reduced developer productivity. Specific issues mentioned include monolithic test organization, slow unit/functional tests, non-deterministic races/timeouts, and re-running all tests on every commit. The document advocates for strategies like separating test types, running in parallel, and using page objects to isolate tests from UI changes.
#BABBQAmsterdam The other Android getting started guide: Gradle power
#BABBQAmsterdam The other Android getting started guide: Gradle powerJavier de Pedro López The document is a comprehensive guide for beginners to intermediate Android developers on using Gradle for Android projects, covering configuration, continuous integration, testing, code coverage, and code quality practices. It discusses various Gradle components, including project structure, tasks, and Android DSL, along with tips for effective versioning and utilizing testing frameworks. Additionally, it emphasizes the importance of unit testing, Android testing, and code quality measures, concluding with a section on creating Gradle plugins.
Software testing: an introduction - 2017
Software testing: an introduction - 2017XavierDevroey Software testing involves dynamically verifying that a program behaves as expected on a finite set of test cases. This is done because exhaustively testing every possible case is not feasible. Unit testing involves testing individual program units such as classes through automated tests that make assertions about the output. JUnit is a unit testing framework for Java that uses annotations to identify test methods and make assertions about the results.
Genymotion with Jenkins
Genymotion with JenkinsVishal Nayak The document outlines the integration of Genymotion with Jenkins for Android testing, focusing on implementing Genymotion devices in headless mode and managing challenges such as IP address retrieval and port conflicts. It provides detailed workarounds for various issues encountered during setup, including managing concurrent builds and ensuring test APK installation. The final implementation steps are highlighted, alongside a repository link for a working script.
Breaking Dependencies To Allow Unit Testing - Steve Smith | FalafelCON 2014
Breaking Dependencies To Allow Unit Testing - Steve Smith | FalafelCON 2014FalafelSoftware The document discusses strategies for unit testing legacy code by breaking dependencies and maintaining loosely coupled architecture. It emphasizes the importance of unit tests being fast, small, and focused on testing single methods or classes while avoiding infrastructure concerns. Key concepts include dependency injection, avoiding global state, and adhering to the dependency inversion principle to make code more testable.
Breaking Dependencies to Allow Unit Testing
Breaking Dependencies to Allow Unit TestingSteven Smith The document discusses strategies for breaking dependencies in legacy code to enable effective unit testing. It emphasizes the importance of unit tests being fast, small, and focused on single units of code, while also promoting principles like dependency injection and maintaining loose coupling. It highlights common pitfalls in code structure that hinder testing and provides guidelines to create more testable design.
Agile Software Testing the Agilogy Way
Agile Software Testing the Agilogy WayJordi Pradel The document discusses best practices for automated software testing in an agile environment, focusing on principles like bug detection and prevention, creating usable and deterministic tests, and avoiding flaky results. It introduces technical concepts such as hexagonal architecture, testing strategies (unit, integration tests), and the importance of clear error reporting and maintainable code. Key techniques highlighted include the AAA (Arrange-Act-Assert) pattern and the use of test doubles for effective testing.
Test Driven Development with JavaFX
Test Driven Development with JavaFXHendrik Ebbers This document discusses test-driven development with JavaFX. It covers testing JavaFX applications at the unit, integration, and system levels. It also discusses continuous integration/continuous delivery and different tools that can be used for testing JavaFX applications, including TestFX, MarvinFX, JemmyFX, and Automaton. TestFX is highlighted as the recommended tool, with details provided on how to interact with JavaFX applications using its fluent API. The document also discusses using the view object pattern to write more readable tests and testing JavaFX applications that use DataFX or Afterburner.fx frameworks. It provides an example of using CDI to inject mocks when testing.
Building XWiki
Building XWikiVincent Massol Le document présente une série de présentations sur le projet XWiki, un wiki d'entreprise open source, et ses processus de développement, d'intégration continue et de libération. Il décrit l'importance des tests automatisés, des contrôles de qualité et de la gestion des versions tout en détaillant le flux de développement et la gouvernance communautaire. Les sujets incluent également l'utilisation de Jenkins pour la CI et l'automatisation des tests pour assurer la qualité et la compatibilité des versions.
Ad
More from Tomáš Kypta (20)
Modern Android app library stack
Modern Android app library stackTomáš Kypta The document discusses modern Android app development practices, comparing traditional methods with contemporary approaches that utilize cleaner architectures, support libraries, and dependency injection frameworks like Dagger 2. It highlights tools such as Retrofit for API interaction, OkHttp for HTTP requests, and libraries for handling memory leaks and image loading, while encouraging developers to consider the implications of adding new libraries to their projects. The content serves as a guide for efficient Android development, emphasizing the importance of modern techniques and tools for improved app performance and maintainability.
Guide to the jungle of testing frameworks
Guide to the jungle of testing frameworksTomáš Kypta The document discusses unit testing in Android applications, outlining various types of tests including instrumentation and local unit tests, along with the respective advantages and limitations. It explains frameworks like Mockito and Robolectric for mocking and testing, provides coding examples, and emphasizes best practices for writing testable code. Code coverage tools and guidelines for good testing practices are also covered.
Practical RxJava for Android
Practical RxJava for AndroidTomáš Kypta The document provides an overview of RxJava for Android, focusing on its concepts and applications, including observable and observer patterns, functional programming, and async processing. It emphasizes the benefits of RxJava, such as simplifying code and eliminating callback hell, while also discussing common mistakes and threading considerations. Additionally, it covers using RxJava with Android lifecycle, integration with Retrofit and SQLite, and provides resources for further exploration.
Practical RxJava for Android
Practical RxJava for AndroidTomáš Kypta The document provides an overview of RxJava for Android, explaining its core concepts such as observable streams, observers, and asynchronous programming approaches. It discusses different RxJava functionalities, including transformation and subscription, while addressing the nuances of integrating with Android's lifecycle and handling reactive programming patterns. Additionally, the document includes code snippets and examples to illustrate the practical application of RxJava in Android development.
Reactive programming on Android
Reactive programming on AndroidTomáš Kypta The document provides an overview of Reactive Programming in Android, focusing on RxJava, its components, key methods, and operators for creating observable sequences. It discusses the benefits of asynchronous processing, error handling, and the importance of threading and lifecycle management in Android development. Additionally, it highlights the integration of RxJava with Retrofit and RxBinding for UI interactions, while addressing common pitfalls and performance considerations.
Android Develpment vol. 3, MFF UK, 2015
Android Develpment vol. 3, MFF UK, 2015Tomáš Kypta The document covers various topics in Android development, including dialogs, material design, UX patterns, and dependency injection. It provides code examples for implementing features like dialog fragments, toolbar customization, card views, and state list animations. Additionally, it discusses software design patterns such as service locator and Dagger 2 for dependency injection, emphasizing best practices and patterns in Android application development.
Writing testable Android apps
Writing testable Android appsTomáš Kypta This document discusses how to write testable Android apps. It recommends abstracting away from Android APIs to isolate business logic, using dependency injection with Dagger 2, and mocking dependencies for testing. The key points are:
1) Abstract business logic from Android components like Activities and Fragments into plain Java classes like presenters and managers to make logic independently testable.
2) Use dependency injection, preferably with Dagger 2, to avoid direct instantiation with "new" and allow mocking dependencies.
3) For testing, mock dependencies using libraries like Mockito and program to interfaces to make mocking possible. This allows testing presenters and other classes in isolation.
4) Other best practices discussed
Android Develpment vol. 2, MFF UK, 2015
Android Develpment vol. 2, MFF UK, 2015Tomáš Kypta The document covers essential concepts in Android development including services (started and bound), broadcast receivers, notifications, and background processing using threads and loaders. It also includes guidelines on creating fragments and integrating libraries like Retrofit for network operations. Exercises are provided to reinforce learning through practical application of these concepts.
ProGuard
ProGuardTomáš Kypta ProGuard is a free Java class file shrinker, optimizer, obfuscator, and preverifier. It supports specifying which classes and class members to keep, options for handling attributes, and configuration for inputs, outputs, and rules. ProGuard is commonly used with Android builds to minimize APK size and prevent reverse engineering by obfuscating code. It outputs mapping files that allow mapping obfuscated code back to its original form.
Android Development for Phone and Tablet
Android Development for Phone and TabletTomáš Kypta Older talk about developing Android applications for phone and tables
Reactive programming on Android
Reactive programming on AndroidTomáš Kypta The document discusses reactive programming and how it can be used on Android. It explains that reactive programming uses observable sequences and asynchronous data flows. It introduces RxJava as a library for reactive programming that uses Observables to compose flows of asynchronous data. It provides examples of how RxJava can be used on Android to perform background tasks, handle errors and activity lifecycles, load images asynchronously, and create and transform Observables.
Android development - the basics, MFF UK, 2014
Android development - the basics, MFF UK, 2014Tomáš Kypta This document provides an overview of Android development, including:
- The basics of the Android platform, ecosystem, and history
- Tools for Android development like Android Studio and SDK
- Key Android app components like Activities, Services, and Broadcast Receivers
- Building a basic "Hello World" Android app
- Designing user interfaces with widgets and handling configuration changes
Android Libraries
Android LibrariesTomáš Kypta This document discusses various Android libraries that can help simplify and improve development. It covers libraries for dialogs, pull-to-refresh, swipe-to-dismiss, image loading, view injection, dependency injection, event bus, IDE plugins, UI debugging, and unit testing. It also provides tips for developing and publishing libraries as JAR, SO, APKLIB, or AAR files.
Android Development 201
Android Development 201Tomáš Kypta The document provides a comprehensive overview of Android development, focusing on key components such as Android Wear, user interface design patterns, navigation elements, and libraries essential for efficient development. It discusses tools and methods for networking, UI debugging, dependency injection, unit testing, and build systems like Maven and Gradle. Additionally, it covers Proguard for code optimization and Android Lint for static code analysis, emphasizing best practices and strategies for managing various aspects of Android applications.
Android development - the basics, MFF UK, 2013
Android development - the basics, MFF UK, 2013Tomáš Kypta This document provides an overview and agenda for an Android development course. It covers the basics of the Android platform, development tools, building blocks of Android apps like activities and fragments, and other key topics like resources, intents, lifecycles, and handling different device configurations. The document gives developers an introduction to developing apps for the Android ecosystem.
Užitečné Android knihovny pro vývoj a testování
Užitečné Android knihovny pro vývoj a testováníTomáš Kypta Prezentace s konference mDevCamp 2013 o Android knihovnách
Programování pro Android - úvod, FI MUNI, 2013
Programování pro Android - úvod, FI MUNI, 2013Tomáš Kypta Introductory lecture to Android development. Faculty of Informatics, Masaryk University, 2013.
Stylování ActionBaru
Stylování ActionBaruTomáš Kypta Lecture on Android ActionBar styling. At aDev Meetup #2 FIT ČVUT Prague.
Android development - the basics, MFF UK, 2012
Android development - the basics, MFF UK, 2012Tomáš Kypta This document provides an overview of Android development basics. It discusses the Android platform, ecosystem, and SDK tools. It describes key Android concepts like activities, services, content providers, and broadcasts. It also covers user interface components, resources, handling different device configurations, fragments, threads, menus, dialogs, notifications and more. The document is intended as an introduction to the fundamentals of Android development.
Android development - the basics, FI MUNI, 2012
Android development - the basics, FI MUNI, 2012Tomáš Kypta This document provides an overview of the basics of Android development. It discusses the Android platform, ecosystem, SDK and tools. It describes the key building blocks like activities, services, content providers and broadcast receivers. It also covers the app lifecycle, intents, user interface components and common widgets like lists, dialogs and toasts.
Recently uploaded (20)
FIDO Seminar: New Data: Passkey Adoption in the Workforce.pptx
FIDO Seminar: New Data: Passkey Adoption in the Workforce.pptxFIDO Alliance FIDO Seminar: New Data: Passkey Adoption in the Workforce
Lessons Learned from Developing Secure AI Workflows.pdf
Lessons Learned from Developing Secure AI Workflows.pdfPriyanka Aash Lessons Learned from Developing Secure AI Workflows
2025_06_18 - OpenMetadata Community Meeting.pdf
2025_06_18 - OpenMetadata Community Meeting.pdfOpenMetadata The community meetup was held Wednesday June 18, 2025 @ 9:00 AM PST.
Catch the next OpenMetadata Community Meetup @ https://www.meetup.com/openmetadata-meetup-group/
In this month's OpenMetadata Community Meetup, "Enforcing Quality & SLAs with OpenMetadata Data Contracts," we covered data contracts, why they matter, and how to implement them in OpenMetadata to increase the quality of your data assets!
Agenda Highlights:
👋 Introducing Data Contracts: An agreement between data producers and consumers
📝 Data Contracts key components: Understanding a contract and its purpose
🧑🎨 Writing your first contract: How to create your own contracts in OpenMetadata
🦾 An OpenMetadata MCP Server update!
➕ And More!
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...Josef Weingand IBM LTO10
Smarter Aviation Data Management: Lessons from Swedavia Airports and Sweco
Smarter Aviation Data Management: Lessons from Swedavia Airports and SwecoSafe Software Managing airport and airspace data is no small task, especially when you’re expected to deliver it in AIXM format without spending a fortune on specialized tools. But what if there was a smarter, more affordable way?
Join us for a behind-the-scenes look at how Sweco partnered with Swedavia, the Swedish airport operator, to solve this challenge using FME and Esri.
Learn how they built automated workflows to manage periodic updates, merge airspace data, and support data extracts – all while meeting strict government reporting requirements to the Civil Aviation Administration of Sweden.
Even better? Swedavia built custom services and applications that use the FME Flow REST API to trigger jobs and retrieve results – streamlining tasks like securing the quality of new surveyor data, creating permdelta and baseline representations in the AIS schema, and generating AIXM extracts from their AIS data.
To conclude, FME expert Dean Hintz will walk through a GeoBorders reading workflow and highlight recent enhancements to FME’s AIXM (Aeronautical Information Exchange Model) processing and interpretation capabilities.
Discover how airports like Swedavia are harnessing the power of FME to simplify aviation data management, and how you can too.
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdf
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdfbiswajitbanerjee38 Russia is one of the most aggressive nations when it comes to state coordinated cyberattacks — and Ukraine has been at the center of their crosshairs for 3 years. This report, provided the State Service of Special Communications and Information Protection of Ukraine contains an incredible amount of cybersecurity insights, showcasing the coordinated aggressive cyberwarfare campaigns of Russia against Ukraine.
It brings to the forefront that understanding your adversary, especially an aggressive nation state, is important for cyber defense. Knowing their motivations, capabilities, and tactics becomes an advantage when allocating resources for maximum impact.
Intelligence shows Russia is on a cyber rampage, leveraging FSB, SVR, and GRU resources to professionally target Ukraine’s critical infrastructures, military, and international diplomacy support efforts.
The number of total incidents against Ukraine, originating from Russia, has steadily increased from 1350 in 2021 to 4315 in 2024, but the number of actual critical incidents has been managed down from a high of 1048 in 2022 to a mere 59 in 2024 — showcasing how the rapid detection and response to cyberattacks has been impacted by Ukraine’s improved cyber resilience.
Even against a much larger adversary, Ukraine is showcasing outstanding cybersecurity, enabled by strong strategies and sound tactics. There are lessons to learn for any enterprise that could potentially be targeted by aggressive nation states.
Definitely worth the read!
You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante We live in an ever evolving landscape for cyber threats creating security risk for your production systems. Mitigating these risks requires participation throughout all stages from development through production delivery - and by every role including architects, developers QA and DevOps engineers, product owners and leadership. No one is excused! This session will cover examples of common mistakes or missed opportunities that can lead to vulnerabilities in production - and ways to do better throughout the development lifecycle.
The Future of Technology: 2025-2125 by Saikat Basu.pdf
The Future of Technology: 2025-2125 by Saikat Basu.pdfSaikat Basu A peek into the next 100 years of technology. From Generative AI to Global AI networks to Martian Colonisation to Interstellar exploration to Industrial Nanotechnology to Artificial Consciousness, this is a journey you don't want to miss. Which ones excite you the most? Which ones are you apprehensive about? Feel free to comment! Let the conversation begin!
Connecting Data and Intelligence: The Role of FME in Machine Learning
Connecting Data and Intelligence: The Role of FME in Machine LearningSafe Software In this presentation, we want to explore powerful data integration and preparation for Machine Learning. FME is known for its ability to manipulate and transform geospatial data, connecting diverse data sources into efficient and automated workflows. By integrating FME with Machine Learning techniques, it is possible to transform raw data into valuable insights faster and more accurately, enabling intelligent analysis and data-driven decision making.
Powering Multi-Page Web Applications Using Flow Apps and FME Data Streaming
Powering Multi-Page Web Applications Using Flow Apps and FME Data StreamingSafe Software Unleash the potential of FME Flow to build and deploy advanced multi-page web applications with ease. Discover how Flow Apps and FME’s data streaming capabilities empower you to create interactive web experiences directly within FME Platform. Without the need for dedicated web-hosting infrastructure, FME enhances both data accessibility and user experience. Join us to explore how to unlock the full potential of FME for your web projects and seamlessly integrate data-driven applications into your workflows.
Security Tips for Enterprise Azure Solutions
Security Tips for Enterprise Azure SolutionsMichele Leroux Bustamante Delivering solutions to Azure may involve a variety of architecture patterns involving your applications, APIs data and associated Azure resources that comprise the solution. This session will use reference architectures to illustrate the security considerations to protect your Azure resources and data, how to achieve Zero Trust, and why it matters. Topics covered will include specific security recommendations for types Azure resources and related network security practices. The goal is to give you a breadth of understanding as to typical security requirements to meet compliance and security controls in an enterprise solution.
“Key Requirements to Successfully Implement Generative AI in Edge Devices—Opt...
“Key Requirements to Successfully Implement Generative AI in Edge Devices—Opt...Edge AI and Vision Alliance For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2025/06/key-requirements-to-successfully-implement-generative-ai-in-edge-devices-optimized-mapping-to-the-enhanced-npx6-neural-processing-unit-ip-a-presentation-from-synopsys/
Gordon Cooper, Principal Product Manager at Synopsys, presents the “Key Requirements to Successfully Implement Generative AI in Edge Devices—Optimized Mapping to the Enhanced NPX6 Neural Processing Unit IP” tutorial at the May 2025 Embedded Vision Summit.
In this talk, Cooper discusses emerging trends in generative AI for edge devices and the key role of transformer-based neural networks. He reviews the distinct attributes of transformers, their advantages over conventional convolutional neural networks and how they enable generative AI.
Cooper then covers key requirements that must be met for neural processing units (NPU) to support transformers and generative AI in edge device applications. He uses transformer-based generative AI examples to illustrate the efficient mapping of these workloads onto the enhanced Synopsys ARC NPX NPU IP family.
cnc-processing-centers-centateq-p-110-en.pdf
cnc-processing-centers-centateq-p-110-en.pdfAmirStern2 מרכז עיבודים תעשייתי בעל 3/4/5 צירים, עד 22 החלפות כלים עם כל אפשרויות העיבוד הדרושות. בעל שטח עבודה גדול ומחשב נוח וקל להפעלה בשפה העברית/רוסית/אנגלית/ספרדית/ערבית ועוד..
מסוגל לבצע פעולות עיבוד שונות המתאימות לענפים שונים: קידוח אנכי, אופקי, ניסור, וכרסום אנכי.
Coordinated Disclosure for ML - What's Different and What's the Same.pdf
Coordinated Disclosure for ML - What's Different and What's the Same.pdfPriyanka Aash Coordinated Disclosure for ML - What's Different and What's the Same
Raman Bhaumik - Passionate Tech Enthusiast
Raman Bhaumik - Passionate Tech EnthusiastRaman Bhaumik A Junior Software Developer with a flair for innovation, Raman Bhaumik excels in delivering scalable web solutions. With three years of experience and a solid foundation in Java, Python, JavaScript, and SQL, she has streamlined task tracking by 20% and improved application stability.
The Future of AI Agent Development Trends to Watch.pptx
The Future of AI Agent Development Trends to Watch.pptxLisa ward The Future of AI Agent Development: Trends to Watch explores emerging innovations shaping smarter, more autonomous AI solutions for businesses and technology.
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdf
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdfPriyanka Aash Oh, the Possibilities - Balancing Innovation and Risk with Generative AI
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdf
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdfPriyanka Aash A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy
OWASP Barcelona 2025 Threat Model Library
OWASP Barcelona 2025 Threat Model LibraryPetraVukmirovic Threat Model Library Launch at OWASP Barcelona 2025
https://owasp.org/www-project-threat-model-library/
You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante
“Key Requirements to Successfully Implement Generative AI in Edge Devices—Opt...
“Key Requirements to Successfully Implement Generative AI in Edge Devices—Opt...Edge AI and Vision Alliance
Unit testing and Android
- 1. Unit Testing & Android Tomáš Kypta
- 2. Unit Testing Experience on Android
- 4. Android apps are difficult to test
- 6. Types of Android tests
- 7. Types of Android tests Instrumentation tests Unit tests
- 9. Instrumentation tests • running on physical device or emulator • gradle connectedCheck
- 11. Intstrumentation tests • Legacy instrumentation tests or • Testing Support Library
- 12. Legacy instrumentation tests • JUnit3 • Tests extend from TestCase • AndroidTestCase • ActivityInstrumentationTestCase2 • ServiceTestCase • …
- 13. Testing Support Library • AndroidJUnitRunner • JUnit4 compatible android { defaultConfig { testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner" } } androidTestCompile 'com.android.support.test:runner:0.3' androidTestCompile 'com.android.support.test:rules:0.3'
- 14. Testing Support Library • Test filtering • @RequiresDevice - run on physical device, no emulator • @SdkSupress - don’t run on lower Android API level
- 15. Test Sizes • @SmallTest • @MediumTest • @LargeTest
- 16. Test Sizes Feature Small Medium Large Network access No localhost only Yes Database No Yes Yes File system access No Yes Yes Use external systems No Discouraged Yes Multiple threads No Yes Yes Sleep statements No Yes Yes System properties No Yes Yes Time limit (seconds) 60 300 900+
- 17. Potential problems • Manifest merger • problems when testing libraries • aar dependency using manifest placeholders • e.g. ${applicationId}, ${localApplicationId} android { defaultConfig { manifestPlaceholders = [localApplicationId:”com.example.mylib”] } }
- 18. Problems • It affects the device! • Wiping contacts will wipe contacts! • You can’t prepare all test preconditions • e.g. you can’t dynamically change permissions
- 19. Problems Test failed to run to completion. Reason: 'Instrumentation run failed due to 'java.lang.IllegalStateException''. Check device logcat for details
- 21. • framework for functional UI tests • part of Android Testing Support Library androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2'
- 22. @Test public void sayHello(){ onView(withId(R.id.editText)) .perform(typeText(STRING_TO_BE_TYPED), closeSoftKeyboard()); onView(withText("Say hello!”)) .perform(click()); String expectedText = "Hello, " + STRING_TO_BE_TYPED + "!"; onView(withId(R.id.textView)) .check(matches(withText(expectedText))); }
- 23. Problems • testing on device is not isolated • device state affects the result • e.g. screen on/off might affect test result onView(withId(R.id.my_view)) .check(matches(isDisplayed()));
- 26. Unit Tests
- 27. Unit Tests • run on JVM • mockable android.jar • gradle test
- 28. Grade and Android Studio support • natively supported since Gradle plugin 1.1.0 • big problems in AS in previous versions • has issues • switching between unit & instrumentation tests • disabled type is not indexed
- 31. • the essential piece • alone can be used only for pure Java • don’t use on Android APIs!
- 32. Method ... not mocked. android { testOptions { unitTests.returnDefaultValues = true } } • Helps rarely • returns 0, false, null, …
- 34. • mocking framework • easy to use • compatible with Android unit testing testCompile ‘org.mockito:mockito-core:1.10.19'
- 35. • can be used in instrumentation tests • needs dexmaker androidTestCompile ‘org.mockito:mockito-core:1.10.19' androidTestCompile "com.google.dexmaker:dexmaker:1.2" androidTestCompile "com.google.dexmaker:dexmaker-mockito:1.2"
- 36. • @RunWith(MockitoJUnitRunner.class) • @Mock • Mockito.mock() • Mockito.when().thenReturn() • when(obj.getA()).thenReturn(aInstance)
- 37. • Mockito.spy() • wrapping a real object • Mockito.verify() • verify that special condition are met • e.g. method called, called twice, …
- 38. Limitations • final classes • anonymous classes • primitive types • static methods
- 40. • at first, might be difficult to use • the ultimate mock of Android APIs • allows custom shadows • @RunWith(RobolectricTestRunner.class)
- 41. • supports Android API level 18 • doesn’t support multiple users on the same machine!!! 2.4
- 42. • Robolectric class splits into • Robolectric • RuntimeEnvironment • Shadows • ShadowApplication • ShadowLooper 3.0-rc3
- 43. that’s the s**t you need for Android unit testing
- 44. Potential problems • difficult to search for solutions • long history of bigger changes • many obsolete posts
- 45. Potential problems • difficulties running on command line and in AS • different paths • difficulty working with resources • RobolectricGradleTestRunner • doesn’t work in AS
- 46. Code Coverage
- 47. Code Coverage • unit tests • JaCoCo • instrumentation tests • EMMA • obsolete • Google is supposedly working on JaCoCo support
- 48. JaCoCo
- 49. JaCoCo • enabled by default for unit tests • generates binary report in build/jacoco • build/jacoco/testDebugUnitTest.exec • gradle test
- 52. Code Coverage • don’t use it • generates coverage-instrumented-classes • for instrumentation tests • coverage for instrumentation tests is not ready buildTypes { debug { testCoverageEnabled true } }
- 53. Good tests
- 54. Good tests • run in any order • run in isolation • run consistently • run fast • are orthogonal
- 55. How to write testable apps?
- 56. Rules of thumb • prefer pure Java • abstract away from Android APIs • separate business logic and UI • don’t write business logic into activities and fragments • try avoid static methods • use dependency injection
- 57. Questions?
- 58. References • Espresso • https://code.google.com/p/android-test-kit/ • https://code.google.com/p/android-test-kit/wiki/ EspressoV2CheatSheet
- 59. References • Mockito • http://mockito.org/ • https://github.com/mockito/mockito • Dexmaker • https://github.com/crittercism/dexmaker
- 60. References • Robolectric • http://robolectric.org/ • https://github.com/robolectric/robolectric
- 61. References • code coverage • JaCoCo • Eclipse Public License v1.0 • http://www.eclemma.org/jacoco/trunk/index.html • https://github.com/jacoco/jacoco • EMMA • Common Public License v1.0 • http://emma.sourceforge.net/