POPULARITY
8 episodes with Appium
9 episodes with Appium
3 episodes with Appium
3 episodes with Appium
2 episodes with Appium
6 episodes with Appium
3 episodes with Appium
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
In this episode, Joe Colantonio sits down with Dalton Alexandre, a self-taught Swift developer who has recently developed a new Swift driver for the Appium framework. Streamline Your Mobile App Testing now: https://testguild.me/applive2 Dalton shares his journey from developing iOS applications to creating this innovative driver. He discusses the motivations behind choosing Swift, the challenges in creating a bare-bones project, and the benefits of contributing to open-source projects like Appium. With insights into parallelization, session management, and versatile testing strategies, this conversation promises valuable takeaways for developers and testers eager to expand their automation expertise. Tune in to learn, explore, and get inspired by Dalton's approach to UI and mobile automation testing!
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
In today's episode, we'll explore my specially curated list of the top 10 must-attend software testing conferences and events for 2025. See all testing conferences with dates and time: https://testguild.com/software-testing-conferences/ Whether you want to stay ahead in the ever-evolving world of test automation, QA, and software testing, this episode is packed with invaluable insights. We'll explore conferences focused on industry-leading tools like Playwright, Selenium, Appium, Cypress, and Robot Framework and events dedicated to security testing, QA leadership, and performance engineering. I'll share experiences, expert-led sessions, and real-world success stories from these remarkable gatherings. Plus, you'll get tips on how to make the most of your conference experience—from networking to taking structured notes. Stay tuned until the end, when I'll reveal a no-brainer event you won't want to miss! This episode is a must-listen if you're ready to boost your testing knowledge and connect with like-minded professionals. Let's get started! ** For Bitrise users signing up on BrowserStack App Automate, grab your free upgrade to App Automate Device Cloud Plan here: https://testguild.me/bitriseuser ** For App Automate users signing up on Bitrise, grab your free credits here: https://testguild.me/AppAutomateUser ** BrowserStack Test Observability: Why Your Automation Tests Are Failing (Test Observability Can Help): https://youtu.be/1myqnQLnA7g
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
Today, I have a fascinating conversation lined up with Tobias Müller, the visionary founder and CTO of TestrResults.io. In this episode, we'll explore the complexities of test environments and innovative solutions in test automation. Tobias shares insights on handling complex enterprise cross-domain automation testing and practical techniques for streamlining test automation. He also explains why relying solely on code-based methods might be limiting. We'll also discuss the significance of UI versus API testing, dynamic software elements, and the challenge of universal approaches in automation. From the limitations of traditional tools like Selenium and Appium to the promising potential of computer vision techniques and AI integration, this episode is a must-listen for anyone looking to push the boundaries of test automation. Get ready for expert advice, industry anecdotes, and a thoughtful discussion on the future of digital testing. Listen up!
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
In this episode, we explore the future of automation, where natural language bridges human intent and machine execution. Mudit unveils the concept of an "AI testing assistant" that interprets natural language to generate and manage test scenarios seamlessly. We'll discuss how this revolutionary tool supports popular frameworks like Selenium, Appium, and Playwright, enabling quality engineers to enhance existing code and execute tests more efficiently. Get ready to learn about innovative features like error classification, root cause analysis, and flakiness detection that streamline debugging and improve test reliability. Join us as we explore Kane AI, LambdaTest's smart AI-powered test agent for high-speed Quality Engineering teams. That allows you to create, debug, and evolve tests using natural language. natural language processing-based platform, designed to democratize quality assurance and tackle the challenges of CI/CD integration. Listen up!
How did NASA test their critical systems for their successful Apollo missions? Have you seen the new free course on how to get started with Playwright and Typescript What really caused the CrowdStrike/Microsoft outage last week? Find out in this episode of the Test Guild New Shows for the week of July 28th. So, grab your favorite cup of coffee or tea, and let's do this. Time News Title Rocket Link 0:22 Register for Newsshow https://testguild.me/newsub 0:31 Appium-device-farm https://testguild.me/73ycdk 1:24 AI Testing for Salesforce https://testguild.me/aisales 2:04 QA Wolf Raises $36M https://testguild.me/e3jwi2 2:33 Cypress Framework with BDD https://testguild.me/syq139 3:39 Apollo success testing https://testguild.me/3b1qst 5:05 Gerald Weinberg https://testguild.me/d8871q 5:31 CrowdStrike blames bug https://testguild.me/qgpi2b 6:02 New Course: Playwright + Typescript https://testguild.me/typescript 7:08 Load tester's guide (part 1) https://testguild.me/ysjn1l 7:57 New Telemetry Tool https://testguild.me/76p3em 8:31 Lakera AI raises $20M https://testguild.me/vms1wd
Welcome back to Season 21 of the "Building Better Developers" podcast! In this episode, "Boost Your Developer Efficiency: Automation Tips for Developers," we explore strategies to enhance productivity. As developers, we often focus on optimizing processes for clients but neglect to apply the same principles to our own work. This episode aims to change that by identifying repetitive tasks in our daily routines and exploring ways to automate and streamline them. Join us as we share insights and practical tips to help you become a more efficient and effective developer. Listen to the podcast and Boost Your Developer Efficiency Identifying Opportunities for Developer Efficiency The first step in enhancing productivity is taking inventory of daily repetitive tasks. Whether it's managing emails or routine development activities, there's always room for improvement. For instance, using email filters, labels, and rules can significantly reduce the time spent sorting through emails. If you don't use these tools, start today by setting up a few simple rules that will organize your inbox and save you time in the long run. Automating Development Tasks for Greater Efficiency Many routine development tasks can be automated to save time and reduce errors. Consider common activities like status reporting, version control, branch creation, and code merging. Automating these tasks can streamline your workflow and free up time for more critical activities. Version Control and Branch Management: If you create multiple branches daily, consider scripting the branch creation process. This can include automating the naming conventions and ensuring consistency across your projects. Build and Deployment Automation: Setting up Continuous Integration/Continuous Deployment (CI/CD) pipelines can automate the build and deployment process. If a full CI/CD setup isn't feasible, simple scripts can still automate tasks like compiling code, copying files to servers, and packaging applications. Database Management: For projects involving databases, having a set of SQL scripts to create users, tables, and other necessary elements can save significant time. Automating these foundational tasks ensures consistency and reduces the potential for errors. Enhancing Developer Efficiency with Shell Scripts and Scripting Languages Shell scripts and other scripting tools are invaluable for automating repetitive tasks. Whether you're using shell scripts on a Unix system or PowerShell on Windows, these tools can significantly enhance productivity. File Operations: Automating file movements, backups, and log management can save time and ensure accuracy. For example, you can write a script to handle directory crawling, file copying, and log parsing, which you might frequently perform. Environment Setup: Setting up development environments can be tedious, especially when dealing with multiple projects or clients. Interactive shell scripts can automate the installation and configuration of required software, making it easier to start new projects. Boosting Efficiency with Macros and IDE Features Most Integrated Development Environments (IDEs) offer features like macros and code snippets that can automate repetitive coding tasks. By setting up templates and custom shortcuts, you can reduce the time spent writing boilerplate code. Code Snippets: Define code snippets for commonly used blocks of code. This not only speeds up coding but also ensures consistency across your projects. IDE Plugins: Explore plugins that enhance your IDE's functionality. Tools like SonarLint can help you write cleaner code by highlighting potential issues as you type. Improving Developer Efficiency with Automated Testing and Quality Assurance Automated testing is another area where you can save time and ensure code quality. Writing unit tests for your code allows you to quickly verify functionality without manually testing every change. Tools like Selenium and Appium can automate testing for web and mobile applications, ensuring that your applications work as intended. Leveraging AI and Communication Tools for Enhanced Developer Efficiency Modern AI tools like ChatGPT and GitHub Copilot can assist in coding by providing suggestions and answering questions. These tools can be particularly useful for overcoming roadblocks and finding solutions to common coding problems. Communication Tools: Use Slack and Microsoft Teams to stay connected with your team. Integrating these tools with CI/CD systems can provide real-time updates on builds and deployments, ensuring everyone is informed about the project's status. Elevate Your Developer Efficiency with Automation Incorporating these productivity shortcuts and automation techniques can transform your development workflow, making you more efficient and less prone to errors. By identifying repetitive tasks, leveraging automation tools, and using modern IDE features, you can save time and focus on more important aspects of your projects. Remember, the key to being a better developer is writing better code and working smarter and more efficiently. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Leverage Technology And Automation For A High Performing Business Use Regular Touch Points And Automation For Better Networking Automating Solutions – Solve First, Then Perfect Outsource And Automate For Passive Income Behind the Scenes Podcast Video
Do you know what open-source tool now has a contribution payment program? Have you seen the first open source AI Test Generation LLM? What are the hottest trends in Kubernetes Find out in this episode of the Test Guild New Shows for the week of May 26th. So, grab your favorite cup of coffee or tea, and let's do this. Time News Title Link 0:00 Register for LinkedIn NewsLetter https://links.testguild.com/wwA8x 0:28 Appium's Sponsorship https://testguild.me/xp8vwy 1:15 Meta's TestGen–LLM https://testguild.me/hwdhiw 2:35 SmartBear Introduces HaloAI https://testguild.me/hsu239 3:37 Testing an API without E2E tests https://testguild.me/2e5k7k 4:40 Kubernetes Trends https://testguild.me/dblljq 5:54 Gatling JavaScript & TypeScript! https://testguild.me/z3fvxb 7:05 HoundDog.ai https://testguild.me/gcz3xb 8:11 Bugcrowd Buys Informer https://testguild.me/r5a7wn
Keep watching until a robot plays Angry Birds! It's insane!Jason Huggins, Creator of Selenium, Co-Founder of Sauce Labs, and Founder & CEO of Tapster Robotics, demos game-changing robots that can swipe, tap, and even insert credit cards in part two of our conversation. Jason shares how teaching a robot to play Angry Birds became a way to provide control over real devices with no limitations. He explains how Tapster's robots complement Appium, shares the evolution of Tapster Valet, and gives advice for aspiring innovators.In case you missed it, we covered the creation of Selenium and Sauce Labs in Part 1 of the conversation with Jason Huggins here:https://www.buzzsprout.com/2211482/14957179-jason-huggins-creator-of-selenium-sauce-labs-part-1.mp3?download=true❓What did you think of the show? Leave your anonymous feedback:https://forms.gle/Df5sDABiNMQn4YSj7CONNECT WITH JASON HUGGINS
What testing podcast is 10 years old today! Have you seen the new open sourced AI-powered Appium script generation tool? And What ever happened to the BDD C# tool SpecFlow? Find out in this episode of the Test Guild New Shows for the week of Feb 18th. So, grab your favorite cup of coffee or tea, and let's do this. Time News Title Rocket Link 0:24 TestGuild Automation Podcast is 10 years OLD!! https://testguild.com/podreview 1:33 Automation Guild After Event Ticket https://links.testguild.com/ag24after 3:07 Eggplant Generative AI https://testguild.me/f4spp6 4:21 From SpecFlow to Reqnroll: Why and How https://testguild.me/yt3c5a 5:44 Mocking API Response In Cypress.io https://testguild.me/723y96 7:14 Applitools Unveils GenAI https://testguild.me/woywzl 8:21 Opensource AI-powered Appium script generation https://testguild.me/453kfn 9:07 Automated red team for Kubernetes security https://testguild.me/qe3w70
What are some of the top Automation Trends for 2024 How do you do Contract Testing using Playwright Have you seen the video on how you can easily learn to Build, train, Test and deploy machine learning models? Find out in this episode of the Test Guild New Shows for the week of Jan 7th. So, grab your favorite cup of coffee or tea, and let's do this. Time News Title Link 0:22 Subsribe to Newsletter https://testguild.com/newssub 0:30 WebDriver BiDi with Puppeteer https://testguild.me/x355g9 1:41 4 difficulty levels of creating test data https://testguild.me/gmvxa4 3:03 API Contract Testing on Frontend with Playwright https://testguild.me/so7lio 4:20 Automation 2024 Trends https://testguild.com/automation-testing-trends/ 5:12 Build, Test machine learning models https://testguild.me/l9d3b3 5:58 appium-interceptor-plugin https://testguild.me/da67uf 7:18 PayPal Billion Transactions per Day https://testguild.me/78ncs1 8:30 OpenTelemetry and Observability https://testguild.me/ba0h63
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
In this episode, I sit down with the CEO and founder of Engenious.io, Igor Dorovskikh. With years of experience in mobile development and expertise in test automation, Igor takes us on a deep dive into the potential of XCUITest and Espresso. Throughout the conversation, Igor discusses his journey in mobile testing, starting with Robotium and eventually transitioning to Espresso. He highlights the benefits of using native solutions like Espresso for native apps and the pros and cons of using Appium for cross-platform applications. We also explore the learning curve of XCUITest and Espresso and the resources available for beginners. Plus, Igor discusses the role of AI and machine learning in mobile testing, offering fascinating insights into code generation and UI visual testing. So, tune in to this episode as Igor Dorovskikh reveals the potential of XCUITest and Espresso and how they can significantly impact your mobile automation journey. Listen up!
Open source contributors and maintainers play a vital role in the technology ecosystem. But what's it like to develop and maintain an open source tool — especially one that thousands of other developers use and depend on? In this episode of the Technology Podcast, Srinivasan Sekar and Sai Krishna join hosts Rebecca Parsons and Scott Shaw to discuss their work on AppiumTestDistribution, an open source tool that supports test automation framework Appium. AppiumTestDistribution won a LambdaTest Delta Award at the August 2023 Testμ Conference. Listen to Sekar and Krishna explain how the project emerged, how they approach maintaining and evolving the tool and what it takes to be a part of an award-winning open source project.
In this episode, host Nikolay Advolodkin engages in a captivating discussion with a true automation expert, Luke Masterman. With over a decade of experience in test automation, Luke specializes in creating frameworks for a wide range of platforms, including web, mobile, and desktop applications. Join us as we delve into critical topics such as test automation reliability, the ROI of test automation, and the intriguing question of whether Selenium is on the verge of being replaced. Subscribe now and stay ahead of the curve with Test Automation Experience!CONNECT WITH LUKE MASTERMAN
This episode of the React Native Show delves into the recent introduction of End-to-End (E2E) testing in the React Native core. Join us as we unpack the thought process, technical considerations, and practical implementation of this new approach to testing in React Native. In conversation with Mateusz Ulańczyk and Szymon Rybczak, the people directly involved in making this solution a reality, we'll cover: - the context and need for improvement in testing within the React Native ecosystem - the goal and expected outcomes of introducing E2E testing - the technical stack behind RNTester-E2E, including Appium and WebDriverIO - the workflow of RNTester-E2E in practice and how it operates on every PR - future plans for RNTester-E2E, including community involvement, device farm integration, and screenshot testing This episode will give you a candid look at how E2E tests in RNTester can help reduce regressions, speed up releases, and ultimately lead to a more robust codebase. Tune in, and enjoy a more stable codebase and more pleasant work! You can find the resources mentioned in the episode on our website ➡️ https://hubs.ly/Q0204Z_D0 Check out other episodes of our podcast
What trends have I been seeing that may mean codeless automation testing is the future? Have you heard the latest on Appium? And what is PerfOps? Find out in this episode of the Test Guild New Shows for the week of July 9th. Time News Title Rocket Link 0:16 Applitoools FREE Account Offer https://applitools.info/joe 0:35 Applitools Acquires Preflight https://testguild.me/9wf6vl 1:59 API TESTING WITH NIGHTWATCH https://testguild.me/mj76g3 2:52 Appium 2.0 is here! https://testguild.me/8v0lz9 3:47 Appium plugin gestures https://testguild.me/dv0chc 4:49 HTMX: Beyond HTML https://testguild.me/hh7oo7 5:46 Api mocking with Playwright https://testguild.me/gtbx9w 6:31 Tricentis Acquires Waldo https://testguild.me/oi5l9x 7:38 PerfOps https://testguild.me/5sv0do 8:35 hacking an online banking API https://testguild.me/o2lbmi
What is Generative AI, and how does it impact automation testing? Can you use AI for test automation code reviews? And have you seen the latest version of Playwright? Find out in this Automation in DevSecOps News Show episode for the Week of March 26. So grab your favorite cup of coffee or tea, and let's do this. Time News Title Rocket Link 0:17 Create your FREE Applitools Account Now https://applitools.info/joe 0:36 MagnifAI by Globant - Sponsored Promo http://bit.ly/3FxfUMT 2:14 Playwright 1.32 is out! https://testguild.me/w1m4x8 2:47 Appium 2.0 now has a decoupled architecture, https://testguild.me/d2zpoo 3:35 SmartBear Acquires OpenTelemetry Pioneer Aspecto https://testguild.me/xiwz43 4:44 Serenity/JS 3.0.0! https://testguild.me/3c7cvn 5:19 Playwright with Cucumber Java https://testguild.me/t0yepk 5:44 Use GPT-4 to do code reviews. https://testguild.me/c24yrt 6:28 Grafana performance testing https://testguild.me/yz91or 7:16 OpenAI SRE and scaling explained easy https://testguild.me/viaijy 7:45 (AppSec) solution automate threat models https://testguild.me/d47v7r
Join our resident Business Ninja Andy, together with Jason Baum, the Director of Community at SauceLabs, the only cloud-based continuous testing platform that enables developers to run their automated tests across desktops, emulators, simulators, and real devices, using Selenium, Appium, Espresso or XCUITest. Sauce Labs helps organizations deliver a trusted digital experience with the most comprehensive and trusted continuous testing cloud in the world. Only Sauce Labs provides the visibility, analytics, and expertise needed to deliver flawless digital experiences and better products to market, faster. Sauce Labs' new "Every Experience Matters" report explores user experience and brand loyalty, focusing on the way users interact with brands, which is more complex and important than ever. Their new study shows the importance of the test, and how that empowers development with speed and quality to keep consumers happy. Every framework, browser, OS, mobile device, API, in every step, from design to deployment, and for the best customer experience, just add Sauce. Visit their website at https://saucelabs.com/.-----Do you want to be interviewed for your business? Schedule time with us, and we'll create a podcast like this for your business: https://www.WriteForMe.io/----- https://www.facebook.com/writeforme.iohttps://www.instagram.com/writeforme.io/https://twitter.com/writeformeiohttps://www.linkedin.com/company/writeforme/https://www.pinterest.com/andysteuer/Want to be interviewed on our Business Ninjas podcast? Schedule time with us now, and we'll make it happen right away! Check out WriteForMe, more than just a Content Agency! See the Faces Behind The Voices on our YouTube Channel!
Leland Takamine is Co-Founder & CEO of mobile.dev, the team behind open source mobile UI testing framework Maestro. The framework, which is a compelling new alternative to Appium or Espresso, has quickly grown to 2.6K stars and a community of >700 users. The company has raised $3M from investors including Cowboy Ventures, Essence VC, and a number of high-profile angel investors. In this episode, we discuss the importance of ease of use for getting open source adoption, how community feedback creates a product advantage, the challenges with timing open source adoption, learnings from growing a community, how to time a paid product & more!
Is low code an automation anti-pattern? Do the majority of organizations recognize the value of AI-augmented DevOps? And what are the top application security trends for 2022? Find out the answers to these and all other and full pipeline DevOps automation testing, performance testing, SRE, and security testing in 10 minutes or less. This episode of the TestGuild News show is for the week of August 8th. So grab your favorite cup of coffee or tea, and let's do this. Time News Title Rocket Link 0:24 Create a FREE Applitools Account https://rcl.ink/xroZw 0:48 API Testing Resources https://testguild.me/hmhoop 1:06 ERP Report https://links.testguild.com/nuLrD 1:55 LOW-CODE ANTI-PATTERN? https://testguild.me/td4ebv 2:46 LambdaTest https://testguild.me/labndaaug7 3:52 Modern Cross Browser Testing with Selenium in Java https://links.testguild.com/8rpgN 5:15 Appium Wait Plugin https://testguild.me/appiumwait 5:58 Early Hints speed up page loads https://testguild.me/hhe5mi 6:51 AI-DevOps Survey https://testguild.me/ergrhb 8:09 Top Application Security Trends for 2022? https://testguild.me/knywoo 9:06 Free Developer Tool Open Source Security & SBOM Creation https://testguild.me/vy8agd
Want to know how to get started with Appium 2.0. Does it matter if you call it monitoring or observability? You're also going to want to stay to the very end to see the five CI/CD breaches analyzed and how they impact your security testing. So stay tuned to these and other and full pipeline DevOps automation testing, performance testing, and security testing in 10 minutes or less in this episode of the TestGuild news show. For the week of June 27. So grab a cup of coffee or tea and let's do this. Time News Title News Link 0:24 Create a FREE Applitools Account https://rcl.ink/xroZw 0:57 CodeWhisperer, https://links.testguild.com/Jiean 2:46 Can we trust AI https://links.testguild.com/AmJVa 3:18 BitBar https://links.testguild.com/c03Dv 3:51 Appium 2.0 https://links.testguild.com/BV83I 4:43 AI CyFast https://links.testguild.com/xgNav 5:33 Monitoring Or Observability? https://links.testguild.com/48siR 7:07 Classification of severity levels https://links.testguild.com/FxLub 7:48 PyPi unsecured sites https://links.testguild.com/apsEn 8:49 5 CI/CD breaches https://links.testguild.com/yf6vM
Echo Innovate IT - Web & Mobile App Development Technologies Podcast
In this podcast, we've compiled a comprehensive list of the best test automation tools for your convenience. You can explore each option and determine which is best for your project. Running software programs that automatically execute test cases and create test results without the need for human intervention is known as automation testing. Top 15 List of Automation Testing Tools for Software & Application 2.1 Katalon Studio 2.2 Selenium 2.3 Appium 2.4 TestComplete 2.5 Cypress 2.6 Ranorex Studio 2.7 Perfecto 2.8 LambdaTest 2.9 Postman 2.10 SoapUI 2.11 Eggplant Functional 2.12 Tricentis Tosca 2.13 Apache JMeter 2.14 Robot Framework 2.15 Protractor We've compiled a list of 15 of the top Automation Testing Tools for various types of testing in this podcast. Some of these tools are free to use, while others require a license. If you have experienced engineers on your team, adopting Selenium or Appium as an automation framework can be beneficial because it allows you to create and scale from the ground up. We're an app development company. At Echo innovate IT Our team of developers can help you to develop your own app. We not only help our clients to develop apps but also help them to maintain it. Contact Us Today! --- Send in a voice message: https://anchor.fm/echo-innovate-it/message
Have you seen the new Appium Inspector? Do you Like BBQ and Performance Testing? Are your using projects such as Cucumber, WebdriverIO, Karma, Cypress? Do you know what security vulnerability they all might have in common that put you at risk? Find out the answers to these and other end-to-end full pipeline DevOps, automation, performance, and security testing in this episode of the test guild news show for the week of Jan 9. 0:28 Applitools FREE Acount: https://rcl.ink/xroZw 1:00 LambdaTest hyperTest:https://links.testguild.com/a9hTB 1:30 Cypress Concourse CI:https://links.testguild.com/xJz09 2:08 Python Top Language:https://links.testguild.com/RJZRz 2:25 Top Automation Testing Prediction for 2022 https://links.testguild.com/VoJrx 3:31 Appium-inspectorhttps://links.testguild.com/MqqA8 4:33 Monkey Testinghttps://links.testguild.com/mOAzU 5:33 PerfTourhttps://links.testguild.com/Rr7dM 6:28 Selenium-3 vs Selenium-4https://links.testguild.com/Fqqnq 6:59 Color.JS Vunerabilityhttps://links.testguild.com/fqwWq 8:12 Mobile App Breaches:https://links.testguild.com/c8EgN 8:45 Snyk Open Source:https://links.testguild.com/MET36
モバイルアプリの実機を使った自動テストが注目されている。リモート操作＆テストプラットフォーム「HeadSpin」の日本正規代理店であり、日本唯一のテクニカルパートナーであるCO-WELL（コウェル）社は2021年3月27日（土）、モバイルアプリのテスト自動化ツール「Appium」と「HeadSpin」を使ったスマートフォン実機テストの最新情報を伝えるオンラインイベント「【CO-WELL】Global Tech Meet #01 モバイルテストの最前線 〜Appiumの今とこれから、急成長HeadSpinとは？」を開催した。イベントのレポートの後編は、テスト自動化ツール「Appium」のアーキテクトでありメインテナーであり、モバイル実機テストプラットフォーム「HeadSpin」の教育プログラムのディレクターであるJonathan Lipp氏の講演内容をお伝えする。
モバイルアプリの実機を使った自動テストが注目されている。リモート操作＆テストプラットフォーム「HeadSpin」の日本正規代理店であり、日本唯一のテクニカルパートナーであるCO-WELL（コウェル）社は2021年3月27日（土）、モバイルアプリのテスト自動化ツール「Appium」と「HeadSpin」を使ったスマートフォン実機テストの最新情報を伝えるオンラインイベント「【CO-WELL】Global Tech Meet #01 モバイルテストの最前線 〜Appiumの今とこれから、急成長HeadSpinとは？」を開催した。イベントのレポートの後編は、テスト自動化ツール「Appium」のアーキテクトでありメインテナーであり、モバイル実機テストプラットフォーム「HeadSpin」の教育プログラムのディレクターであるJonathan Lipp氏の講演内容をお伝えする。
Did you know that Appium has an in-built integration to XCode Instruments? In this episode, Sandeep Dinesh shares how to leverage this information to measure your iOS app's performance in a real device or a simulator. Discover performance testing mobile app tips, what to measure, and key performance indicators to be aware of. Listen up!
モバイルアプリの実機を使った自動テストが注目されている。リモート操作＆テストプラットフォーム「HeadSpin」の日本正規代理店であり、日本唯一のテクニカルパートナーであるCO-WELL（コウェル）社は2021年3月27日（土）、モバイルアプリのテスト自動化ツール「Appium」と「HeadSpin」を使ったスマートフォン実機テストの最新情報を伝えるオンラインイベント「【CO-WELL】Global Tech Meet #01 モバイルテストの最前線 〜Appiumの今とこれから、急成長HeadSpinとは？」を開催した。今回は、そのイベントのレポートの前編として、AppiumコミッターでありHeadSpinのサービス基盤開発を米国で行っている松尾和昭 氏の講演内容を整理してお伝えする。
モバイルアプリの実機を使った自動テストが注目されている。リモート操作＆テストプラットフォーム「HeadSpin」の日本正規代理店であり、日本唯一のテクニカルパートナーであるCO-WELL（コウェル）社は2021年3月27日（土）、モバイルアプリのテスト自動化ツール「Appium」と「HeadSpin」を使ったスマートフォン実機テストの最新情報を伝えるオンラインイベント「【CO-WELL】Global Tech Meet #01 モバイルテストの最前線 〜Appiumの今とこれから、急成長HeadSpinとは？」を開催した。今回は、そのイベントのレポートの前編として、AppiumコミッターでありHeadSpinのサービス基盤開発を米国で行っている松尾和昭 氏の講演内容を整理してお伝えする。
Ela criou um curso de automação de testes com Appium usando Python e disponibilizou gratuitamente no Github para ajudar a comunidade a conseguir dar seus primeiros passos nessa camada. Maria Clara Bezerra é o nome dela, que atua hoje em dia no CESAR, é professora de pós graduação e tem contribuído para a comunidade em sua região e nacionalmente. Encontre-a no linkedin buscando por Maria Clara Bezerra.
スマートフォンの世界的浸透に伴い、アプリ開発者は動作検証や不具合対応をグローバルな視点で行うことが不可欠となった。膨大な機能検証、回線など物理的な環境の違いを踏まえた複雑な検証プロセス、各地域におけるスマートフォン実機の獲得など負担の大きさが深刻な課題となっている。それらを効率的に進められると注目されているのがモバイルアプリのテスト自動化ツール「Appium」とリモート操作＆テストプラットフォーム「HeadSpin」の合わせ技だ。「HeadSpin」の日本正規代理店であり、日本唯一のテクニカルパートナーであるCO-WELL（コウェル）社は2021年3月27日（土）、「Appium」と「HeadSpin」を使ったスマートフォン実機テストの最新情報を伝えるオンラインイベント「【CO-WELL】Global Tech Meet #01 モバイルテストの最前線 〜Appiumの今とこれから、急成長HeadSpinとは？」を開催する。時間は10時から12時15分まで。参加費は無料。なお、このイベントにはAppium開発リードでありHeadSpinの学習および教育プログラムのディレクターとして活躍するJonathan Lipps 氏とAppiumコミッターでありHeadSpinのサービス基盤開発を米国で行っている松尾和昭 氏が登壇する。
2021年3月27日（土） 「モバイルテスト最前線」オンラインイベント参加はこちらスマートフォンの世界的浸透に伴い、アプリ開発者は動作検証や不具合対応をグローバルな視点で行うことが不可欠となった。膨大な機能検証、回線など物理的な環境の違いを踏まえた複雑な検証プロセス、各地域におけるスマートフォン実機の獲得など負担の大きさが深刻な課題となっている。それらを効率的に進められると注目されているのがモバイルアプリのテスト自動化ツール「Appium」とリモート操作＆テストプラットフォーム「HeadSpin」の合わせ技だ。「HeadSpin」の日本正規代理店であり、日本唯一のテクニカルパートナーであるCO-WELL（コウェル）社は2021年3月27日（土）、「Appium」と「HeadSpin」を使ったスマートフォン実機テストの最新情報を伝えるオンラインイベント「【CO-WELL】Global Tech Meet #01 モバイルテストの最前線 〜Appiumの今とこれから、急成長HeadSpinとは？」を開催する。時間は10時から12時15分まで。参加費は無料。なお、このイベントにはAppium開発リードでありHeadSpinの学習および教育プログラムのディレクターとして活躍するJonathan Lipps 氏とAppiumコミッターでありHeadSpinのサービス基盤開発を米国で行っている松尾和昭 氏が登壇する。
This episode brought to you by Infinite Red! Infinite Red is a premier React Native design and development agency located in the USA. With five years of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter), Infinite Red is the best choice for your next React Native app.Helpful Links:RN testing overviewThe Practical Test PyramidAn awesome guide from Kent C Dodds on Testing JSCarly Litchfield's Talk at Chain React about screenshot testing with PercyDetoxAppiumCypressSeleniumMotion JuxtaposeConnect With Us! Jamon - @jamonholmgrenRobin - @robin_heinzeHarris - @brunostmannAdhithi - @adhithiravi
This podcast dwells on Selenium as one of the most widely-used and efficient testing software frameworks, we have been practicing in Agiliway for a while so far. Why we opt for Selenium? It has a number of advantages such as cost, flexibility and parallel testing capability. Regarding our practical experience, Selenium is perfectly combined with Appium for better automation service. What is more, we cannot but focus on the Robot Framework in the course of the testing procedure. In combination with Selenium libraries, the Robot Framework provides power and simplicity esteemed so high among the non-technical people. Finally, the whole testing process (creating test case and, afterward, scripts) could take from 20 minutes to two days wholly depending on the very feature tested. With the Selenium testing framework, both we and our clients get extra level of confidence and security.
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
If you are on social media, you’ve probably seen folks discussing the free TestProject automation framework. With the release of their new OpenSDK, there’s, even more, to be excited about. In this episode, Kevin Dunne will talk about the most recent version of their OpenSDK. Discover what’s new in this significant milestone that can make your Selenium and Appium automation efforts easier.
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
Are you an Appium automation engineer? Or do you need to automate mobile applications? In this episode, the main leader and contributor at Appium, Jonathan Lipps, will share his vision, technical possibilities, and changes you need to know about for Appium 2.0. Jonathan will also share his involvement with a new must-know resource for Appium testers—HeadSpin University. You don’t want to miss this episode!
Гости: Алексей Хурсевич - главный специалист по созданию мобильных ферм Темы: - 00:00:09 - Начало - 00:01:41 - Гость - 00:04:15 - Кому нужны мобильные фермы? - 00:12:36 - Какие периферийные устройства используются при построении фермы? - 00:16:40 - Сколько устройств я могу подключить к одному серверу? - 00:19:11 - Как вы подбираете мобильные устройства для ферм? - 00:21:08 - Какие преимущества и недостатки перед cloud провайдерами: Browserstack и Saucelabs? - 00:23:58 - В чем основные ограничения ферм и cloud провайдеров в сравнении с устройствами на руках? - 00:24:49 - Сколько стоит содержать мобильную ферму? - 00:28:01 - С каким проблемами приходится сталкиваться в процессе эксплуатации? - 00:31:15 - Как сделать стабильными беспроводной доступ к интернету для сотни девайсов? - 00:33:51 - Где хранятся все устройства и как обеспечивается безопасность? - 00:41:41 - Что из себя представляет конфигурация сервера: Ubuntu, MacOS? - 00:48:27 - Может вспомните негативные случаи из опыта? - 00:53:40 - В чем ваш интерес? - 00:54:25 - Бекапы, дублирование надежность - 00:59:36 - Возможно ли работать с устройствами удаленно, кому это может быть полезно в команде? - 01:02:37 - Возможно ли полностью перевести мобильную автоматизацию в облако под управлением Kubernetes? - 01:06:05 - Отчеты - 01:09:45 - Appium vs Espresso ? - 01:12:49 - Нужен ли паяльник? - 01:16:32 - Патроны - 01:24:55 - Финал Telegram: t.me/automation_remarks Стать патроном: www.patreon.com/automation_remarks Спасибо патронам: Igor Gruziev, Maryna Kolesnik, Miguel Suddya, Tetiana Hrybok, Alisa Markova, Marat Reymers, Vitaly Fedrunov, Kuptsov Ivan, Anastasiya Mazheika, Mykola Podolianiuk, Nikita Verbitsky, Stanislav Ivanov, Maxim Denisov, Перетятько Игорь, Nikolay Georgievskiy, Alex Hramovich, Vitalii Полезное: MCloud presentation: https://docs.google.com/presentation/d/19xS2QeEUzPxqtZLZ4U5gfni0C44G5tZ5kfxCe6-YROE/edit?usp=sharing MCloud Github repo: https://github.com/qaprosoft/mcloud Android provider: https://github.com/qaprosoft/mcloud/tree/android-slave IOS code signing https://medium.com/xcblog/ios-code-signing-tutorial-series-814b22eba507
In this episode of React Native Radio the panel overviews the libraries and tools they choose for their stack and explain why they choose them. Christopher Reyes starts by discussing his favorite notes app, Bear Notes. He shares the features from the app that makes him love it so much. The panel also discusses Notion as a good resource for organizing teams. Next, Chris outlines the stack he would recommend for someone new to development and React Native. He recommends React Native CLI, React Native Navigation, Native Base, and Async Storage. Chris explains why he recommends these tools. The panel also discusses the importance of going back to your source to make sure you are using the most up to date product. The panel considers what version five of React Navigation with the component-based API will change in their everyday work. They all express their excitement to try it. Jamon Holmgren is the next panelist to outline his stack. He builds with Ignite and uses the stack that it provides. Jamon explains how Ignite works and what it has in its stack. He likes React Navigation, MobX and, React Native Screens. Jamon goes over the pros and cons of a Native navigation stack compared to a JavaScript one. He also explains why he prefers MobX and goes over the differences over their various tools. He also discusses the boilerplates built by Infinite Red and what to expect in their upcoming boilerplates. Next, Charles Max Wood shares his troubles with his current DevchatTV app and the panel tries to help. Josh Justice is the last to overview his stack, he discusses one of his hobby apps, building a todo app. He is using Orbitjs, ESLint, Prettier, React Native Elements, and React Native Paper. Josh emphasizes the need to test even in hobby projects, for that he uses Dependabot, React Native testing library, and Detox. Panelists Josh Justice Charles Max Wood Christopher Reyes Jamon Holmgren Sponsors Infinite Red G2i CacheFly Links Bear Notes Notion NativeBase AsyncStorage React Native CLI React Navigation React Navigation v5 preview Ignite React Native screens MobX State Tree React Native EU 2019: Jamon Holmgren MobX Jamon Holmgren - Build an iOS and Android app in 15 minutes using React Native Orbit JS nativeup Dependabot Material UI guidelines iOS Human Interface Guidelines Appium https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio Picks Charles Max Wood: The MaxCoders Guide To Finding Your Dream Developer Job Buy DevchatTV a coffee Josh Justice: Editor Snippets Christopher Reyes: MacBook Pro Web Developer Setup — From clean slate to dev machine Jamon Holmgren: Software Libraries Are Terrifying
In this episode of React Native Radio the panel overviews the libraries and tools they choose for their stack and explain why they choose them. Christopher Reyes starts by discussing his favorite notes app, Bear Notes. He shares the features from the app that makes him love it so much. The panel also discusses Notion as a good resource for organizing teams. Next, Chris outlines the stack he would recommend for someone new to development and React Native. He recommends React Native CLI, React Native Navigation, Native Base, and Async Storage. Chris explains why he recommends these tools. The panel also discusses the importance of going back to your source to make sure you are using the most up to date product. The panel considers what version five of React Navigation with the component-based API will change in their everyday work. They all express their excitement to try it. Jamon Holmgren is the next panelist to outline his stack. He builds with Ignite and uses the stack that it provides. Jamon explains how Ignite works and what it has in its stack. He likes React Navigation, MobX and, React Native Screens. Jamon goes over the pros and cons of a Native navigation stack compared to a JavaScript one. He also explains why he prefers MobX and goes over the differences over their various tools. He also discusses the boilerplates built by Infinite Red and what to expect in their upcoming boilerplates. Next, Charles Max Wood shares his troubles with his current DevchatTV app and the panel tries to help. Josh Justice is the last to overview his stack, he discusses one of his hobby apps, building a todo app. He is using Orbitjs, ESLint, Prettier, React Native Elements, and React Native Paper. Josh emphasizes the need to test even in hobby projects, for that he uses Dependabot, React Native testing library, and Detox. Panelists Josh Justice Charles Max Wood Christopher Reyes Jamon Holmgren Sponsors Infinite Red G2i CacheFly Links Bear Notes Notion NativeBase AsyncStorage React Native CLI React Navigation React Navigation v5 preview Ignite React Native screens MobX State Tree React Native EU 2019: Jamon Holmgren MobX Jamon Holmgren - Build an iOS and Android app in 15 minutes using React Native Orbit JS nativeup Dependabot Material UI guidelines iOS Human Interface Guidelines Appium https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio Picks Charles Max Wood: The MaxCoders Guide To Finding Your Dream Developer Job Buy DevchatTV a coffee Josh Justice: Editor Snippets Christopher Reyes: MacBook Pro Web Developer Setup — From clean slate to dev machine Jamon Holmgren: Software Libraries Are Terrifying
In this episode of React Native Radio the panel considers the roles of QA and development teams. Charles Max Wood and Josh Justice share their backgrounds in QA and development, this gives them a unique perspective, having seen it from both sides. They begin by discussing and defining some terms. Charles explains that most terms are defined more by an organization than the industry. The panel discusses testing tools like Cypress and Detox, explaining their uses and value. They define black box and gray box testing and consider the benefits of each testing type. Josh explains the value of manual testing and how that value may never be lost. They consider the strategy of relying on users to find bugs. They compare testing mobile and web development. They consider how the roles of QA and development overlap and the best ways to define the roles of each team. Charles recommends each organization sit down and clearly define these roles. Josh recommends clearly outlining where CI and CD come into play. They consider the common relationship issues found between QA and development, including animosity and an “us vs. them” mentality. Charles and Josh explain the value of working together and communicating with each other. They give advice on how to work together and improve relationships between QA and development. Panelists Charles Max Wood Josh Justice Sponsors Infinite Red G2i CacheFly Links The MaxCoders Guide To Finding Your Dream Developer Job https://github.com/wix/Detox Appium https://www.cypress.io/ https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio Picks Charles Max Wood: Holiday Inn White Christmas The MaxCoders Guide To Finding Your Dream Developer Job Josh Justice: Code review Slack
In this episode of React Native Radio the panel considers the roles of QA and development teams. Charles Max Wood and Josh Justice share their backgrounds in QA and development, this gives them a unique perspective, having seen it from both sides. They begin by discussing and defining some terms. Charles explains that most terms are defined more by an organization than the industry. The panel discusses testing tools like Cypress and Detox, explaining their uses and value. They define black box and gray box testing and consider the benefits of each testing type. Josh explains the value of manual testing and how that value may never be lost. They consider the strategy of relying on users to find bugs. They compare testing mobile and web development. They consider how the roles of QA and development overlap and the best ways to define the roles of each team. Charles recommends each organization sit down and clearly define these roles. Josh recommends clearly outlining where CI and CD come into play. They consider the common relationship issues found between QA and development, including animosity and an “us vs. them” mentality. Charles and Josh explain the value of working together and communicating with each other. They give advice on how to work together and improve relationships between QA and development. Panelists Charles Max Wood Josh Justice Sponsors Infinite Red G2i CacheFly Links The MaxCoders Guide To Finding Your Dream Developer Job https://github.com/wix/Detox Appium https://www.cypress.io/ https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio Picks Charles Max Wood: Holiday Inn White Christmas The MaxCoders Guide To Finding Your Dream Developer Job Josh Justice: Code review Slack
In gesprek met Job van den Berg over het JOSF Selenium framework. Het verschil tussen Selenium IDE en Selenium Webdriver. Mobile testing met Appium en JOSF voor low-code platformen zoals Pega.
Unser Eindruck von SwiftUI und Android Entwicklung, PushOver DDoS und den IPv6 Problemen bei Elite Dangerous... SwiftUI lernen: https://developer.apple.com/tutorials/swiftui/resources ・ Android Studio: https://developer.android.com/studio ・ PushOver DDoS: https://blog.pushover.net/posts/2019/10/october-24-25-ddos-attack ・ DDoS: https://en.wikipedia.org/wiki/Denial-of-service_attack ・ Android API Level: https://source.android.com/setup/start/build-numbers ・ Streamsheets: https://cedalo.com/produkt/ ・ Streamsheets Docker: https://hub.docker.com/r/cedalo/streamsheets-installer ・ Hörer Fabian startet mit Node-Red: https://www.youtube.com/watch?v=KMgIa0l_ukQ ・ Xerox scanners/photocopiers randomly alter numbers in scanned documents: http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_are_switching_written_numbers_when_scanning ・ EzControl XS1: http://www.ezcontrol.de/content/view/36/28/ ・ FS20: https://de.wikipedia.org/wiki/Funksysteme_zur_Geb%C3%A4udeautomatisierung ・ ELV MAX: https://de.elv.com/technik-fuer-ihr-zuhause/heizungssteuerung/systemuebersicht-heizkoerperthermostate/max-funk-heizungsregler-system/ ・ ELV MAX Library: https://github.com/bietiekay/MAXSharp ・ SDR Wettersensor: https://www.kompf.de/weather/rtlsdrsensor.html ・ NodeRed: https://nodered.org/ ・ Höhere Gehälter für IT Experten https://www.heise.de/newsticker/meldung/Oeffentlicher-Dienst-Bundestag-beschliesst-Zulagen-und-Praemien-fuer-IT-Experten-4569784.html ・ Ice Lake CPU: https://en.wikipedia.org/wiki/Ice_Lake_(microprocessor) ・ USB-C: https://en.wikipedia.org/wiki/USB-C ・ Quickcharge 3 für Arduino: https://www.schrankmonster.de/2019/09/18/quickcharge-3-qc3-enable-your-arduino-project/ ・ Android Espresso: https://developer.android.com/training/testing/espresso ・ JUnit: https://junit.org/junit5/ ・ WebBrowser UI Testing: https://www.seleniumhq.org/ ・ Appium: http://appium.io/ ・ Visual Studio 2019: https://devblogs.microsoft.com/devops/changes-to-coded-ui-test-in-visual-studio-2019/ ・ Elite: https://en.wikipedia.org/wiki/Elite_(video_game) ・ Elite Dangerous: https://www.elitedangerous.com/ ・ Andreas bei Distant Worlds 2: https://www.hack-the-planet.net/2019/06/02/distant-worlds-2-been-there-seen-it/ ・ Galaxie: Milchstraße: https://de.wikipedia.org/wiki/Milchstra%C3%9Fe ・ Trappist-1 System: https://de.wikipedia.org/wiki/Trappist-1 ・ Elite Dangerous VR: https://www.youtube.com/watch?v=Fa0b2Kd2xhU ・ IPv6 https://de.wikipedia.org/wiki/IPv6 ・ IPv4 https://de.wikipedia.org/wiki/IPv4 ・ Carrier grade NAT https://de.wikipedia.org/wiki/Carrier-grade_NAT ・ NAT64 https://de.wikipedia.org/wiki/NAT64 ・ aText Mac: https://www.trankynam.com/atext/ ・ Autohotkey Windows: https://www.autohotkey.com/ ・
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
Today we’ll be discussing Appium and Visual Testing with Wim Selles. Wim is a Netherlands-based solutions architect for Sauce Labs. He has extensive knowledge about all things automation and has helped hundreds of Sauce customers solve automation challenges in their own organizations. Wim is also known for his extensive experience using Appium for automating Hybrid and React Native apps. Don’t miss this chance to discover Appium hacks for your mobile automation efforts.
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
In this episode, we’ll talk to Mark Kardashov, CEO and Co-Founder of TestProject, a free automation framework built on top of Selenium and Appium. You may have heard that Tricentis recently acquired TestProject, and that’s one of the things we’ll be discussing today. Listen to discover what all the buzz around Test Project is, and how Tricentis plans on making it even better.
0:38 - Hilal Rakıcı Paşalı Kimdir? 2:20 - Getir maceran nasıl başladı? 4:39 - Ofiste günün genel olarak nasıl geçiyor? 6.42 - Test ekibi kaç kişi, bir qa hem manuel hem otomasyon yapabilmeli mi? 9.46 - Türkiye'deki yazılım firmalarının teste bakış açısı nedir? 14:42 - Ekipteki Developer / QA oranı nasıl olmalı? 16:17 - Bir developer, qa rolünü üstlenebilir mi? 18:21 - Bir qa işe almak istersen nelere dikkat edersin? 21:38 - Mobil test yaparken yaşanan zorluklar? 24:24 - Appium. 26:44 - Kendinin ve ekibinin motivasyonunu ayakta tutmak için kullandığın yöntemler var mı? 29:05 - İyi bir fikir nasıl anlaşılır? 30:21 - Kariyerinde kırılma noktam dediğin bir an var mı? 31:09 - Deadline ve kaliteden ödün vermek. 32:11 - Büyük bir makinanın küçük bir çarkı olmak, küçük bir makinanın büyük bir çarkı olmak. 32:51 - Bug reporting & hata örnekleme 43:56 - Kusursuzluk iyinin düşmanı mıdır? 45:47 - Yazılım testinin geleceği hakkında ne düşünüyorsun? 47:55 - Zaman yönetimi 49:39 - Konfor alanından çıkmak, yeni şeyler denemek. 52:26 - Qa performansı 57:58 - Testrail 59:24 - Üretmek için doğru kaynakları tüketmek, para harcamayı öğrenmek. 1:03:25 - Sektördeki qa kalitesi 1:05:25 - Radarımıza alıp incelememizi tavsiye edeceğin yöntem, dil, disiplin var mıdır? 1:07:15 - Mesai yapmak. 1:09:32 - Mobil testine sıfırdan başlamak veya ilerlemek isteyenlere tavsiyeler.
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
Do you like Cypress.io, but feel it’s too developer-centric for your testing team? Do you still want to use Selenium and Appium, but in a more straightforward way? If so, this episode is for you as we test talk about the automation framework Oxygen with the co-founder of Cloudbeat, Nachum Dimer. Listen up to learn about another open- source tool that might be the perfect fit for your automation efforts.
In this internal Frontside Podcast episode, Charles, Taras, and Jeffrey analyze the NativeScript Mobile Platform. Please join us in these conversations! If you or someone you know would be a perfect guest, please get in touch with us at contact@frontside.io. Our goal is to get people thinking on the platform level which includes tooling, internalization, state management, routing, upgrade, and the data layer. This show was produced by Mandy Moore, aka @therubyrep of DevReps, LLC. Transcript: CHARLES: Hello and welcome to The Frontside Podcast, a place where we talk about user interfaces and everything that you need to know to build them right. My name is Charles, a developer here at Frontside. With me today are Taras and Jeffrey. TARAS: Hello everyone. CHARLES: Today, we're going to be talking about NativeScript, in particular, and evaluating technologies and frameworks, kind of at the meta level. So, I'm kind of excited about it because we've been pretty heavily involved with NativeScript for the past three months or so. And so, we've gotten to look at it both from beginners' eyes being kind of totally fresh to the platform, but then actually having to start to pump up against some of the edge cases which is what always ends up happening when you actually use a framework for real. Let's get started. TARAS: All right. I think there's a lot of things that we could talk about because when we would start looking at NativeScript, the length that we were looking at NativeScript through this is that this platform that our client is going to be using for doing development of large applications. So, what does NativeScript need to have to be able to support potentially hundreds of developers building apps? We started looking at it and one things that made us consider NativeScript early on was it kind of provides a platform that allows you to encode in JavaScript and run it on mobile. And we saw this kind of emergence of Angular and Vue.js running on top of NativeScript. So, those things together is kind of exciting. CHARLES: There was also an implementation in progress of React and there were a couple of spikes of Ember also running on top of NativeScript. So, my first impression was initially very favorable. The onboarding experience is actually pretty nice because it was JavaScript and the application was interpreted, there's the ability to completely and totally dynamically change the application at runtime. So, they have essentially an application called the NativeScript Playground which lets you flash a QR code at it and then it will go in to the URL associated with that QR code and it will download all of the assets for a NativeScript application running at that URL. So, all the JavaScript, all the templates, all the whatever, it'll pull it down, it will actually start running like within that app. So, the Playground app then becomes your actual app that you want to use. There's no App Store, no TestFlight, no Google Play. There's no gatekeeping to delivering your application into a running app. And I thought that was really, really cool and really, really compelling. TARAS: We should clarify that this is specifically for preview purposes because if you're going to be shipping the application to production, you still need to go through all those things before... CHARLES: Yes. TARAS: But the onboarding process, you could just install the preview app and then you can point a QR code and it will open that app, whether it's in Angular or in Vue, that app will open up in the preview app and you have a native app that you could play around with. CHARLES: Right. JEFFREY: And that's key both for the engineers who are playing around with this and building this and also really key for the non-engineers who are part of the team to be able to really easily spin up and see what the engineers on the team are working on. CHARLES: That's exactly why we thought, "Hey, we want to be able to use this mechanism for preview apps." In the same way on the server side, you have preview apps associated with a pull request. When we saw this, what we immediately wanted to do was have a bot post a comment onto a pull request with a QR code, so that anybody could just, boom, test out this app on their phone. TARAS: We ultimately ended up setting that up but not quite that way because the original idea of being able to have something like danger bot post the QR code to the comments, you can kind of point out with your phone and open the preview app, that didn't actually pan out. Charles tried to implement that. What happened there? CHARLES: What it actually turned out was that the preview functionality was dependent on a central server, a central NativeScript server. So rather than kind of statically bundling the assets and just saying 'these assets are this URL and just pull them in and bootstrap your NativeScript application that way', it required a lot of extra stuff. So, it required you to be running a Webpack Dev Server that was building your assets and then basically registering and doing some port forwarding with that dev server to a central NativeScript service that was provided by the company that underpins NativeScript. And that connection needed to be hot and live the whole time for that to work. So, while it was really cool that you could get the QR codes up and running, unfortunately that functionality could not be decoupled from the hot update and the central service. Those central services were kind of hard coded into the tools. TARAS: Yeah. So we eventually ended up implementing the preview apps that we wanted but we ended up using Appetize.io to essentially -- the process there is you build the app, you upload the app to Appetize and then danger bot embeds a link to a URL where you can open that app and it will essentially stream like it's running somewhere in a simulator for iOS, an emulator for Android and it will stream a video of that and you can interact with it, kind of like a VNC setup. CHARLES: Yeah. TARAS: And that actually accomplished the goal. It's just we weren't able to do the way that we thought we were hoping to do it straight off with the preview app mechanism. CHARLES: It accomplished the goal. And Appetize is an incredible service that lets you preview the apps on pretty much any type of Android device, any type of iOS device, right there inside of a pull request. But what it didn't allow us to do was pop up your actual device, your actual phone and scan a QR code off of the pull request and pull down the assets. That would have been amazing. But it doesn't always work out that way. And I don't know if that would work long term anyhow because you can't pull down native libraries over the wire and funk them in. That's a big, big no-no. So, the process does have limitations. But nevertheless, that part was really cool. TARAS: Yeah. That was kind of the entry point, the onboarding. And then I think one of the things that was kind of, I remember at the time when we were talking about the NativeScript architecture because we were starting to understand more about how it works. The idea itself is really kind of amazing actually because you have this V8 where you can run your JavaScript code and then they're kind of wired together on iOS and Android. They're wired to the native implementation. So when you're interacting with it, I think the thing that's really great about NativeScript is that the runtime environment for JavaScript essentially gives you API access. In JavaScript, you could say, "I want to create a Java view," and there will be a Java view that's rendered in the actual native device. You're using the same -- the APIs that you find on the Android docs or iOS docs, all of those APIs are available to you as JavaScript. So, you [crosstalk] as JavaScript. And it's seamless, right? CHARLES: Yeah, and it makes it very, very handy. The language is different but the APIs are exactly the same. There is an attempt to make cross-platform components and cross-platform classes that serve the needs on both platforms and then delegate to the platform on which you happen to be running. But those are not mandatory, and the low level APIs are always available to you. An example of this is in iOS, kind of the core foundational object is NSObject. All the controllers, the views, the things, all of them are descended from this object. I can go from object and I can go in from JavaScript and I can just say {let object = new NSObject} and boom! I've got a reference to the actual object and I can pass it around to any other iOS API. That is really, really powerful that there's nothing off limits. There's nothing at an arm's distance. There's really not much you can't do because all of those things are available to you. There's nothing that's off limits. That means that they can build cross-platform components on top of those APIs. Whereas a sort of system like React Native which does have cross-platform components, that's kind of where the base layer is but you can't crack open the hatch and go down the next level and start mucking around, unless you want to actually start meddling with the React Native source code or recompiling Swift in Java code. TARAS: For me, I think this architecture is probably my favorite part of NativeScript. JEFFREY: Mine too. CHARLES: Yeah, me too. TARAS: I really like this part. I kind of hope that everything else is as clever as that was. CHARLES: Because among other things, it allowed us to write a Bluetooth. We were able to implement Bluetooth using nothing but JavaScript. We didn't actually have to go down and do any Swift and do any asynchronous message passing between the iOS libraries and the JavaScript libraries. It's like, "No." We've just got a very simple cross-platform interface that instantiates an implementation for Android and an implementation for iOS, but both of them are like JavaScript. And so, it really is you're doing native development but it's JavaScript all the way down. TARAS: Yeah. And when you're writing plugins, your plugin is actually JavaScript plugin that is assuming iOS APIs and Android APIs. CHARLES: Yeah. And if you have to have a native plugin like a CocoaPod or an Android Package, you just install it and you can instantiate it from JavaScript. There's no fuss, no muss, no ceremony. It's just like, "Hey, I want to use the..." what was the one we like to use? The Material-UI floating button which is a CocoaPod. You download it, you link it into your application, and then you just instantiate it from JavaScript. TARAS: That was really cool. The challenging part was that a lot of that kind of awesomeness, like everything around it wasn't quite as polished. And so, one of the big things is that like around tooling, because one of the things about having grown up in a way like in the Ember community, in a sense, we have a certain expectation of what the level of polish from tooling that we would expect. And it's kind of supported in the way like when you look at how React or React Native tooling is, even Angular tooling, it's very polished. You kind of expect to see what you need to see when you're looking at a CLI input and you don't see anything else. That level of polish. I think part of the changes that they're going through, maybe that's part of the reason but that same level of polish isn't available around the tooling. CHARLES: There are these fantastic qualities about the platform and it is amazing. We were using Angular and a lot of people are using Vue and things like that and that actually is pretty incredible. And there is nice tooling, there is command line stuff, but we started to run into issues where, for example, it was very clear that we were pretty much, as far as I could tell, one of the very, very few people running a NativeScript project on CircleCI or in a CI environment at all. It had capability for testing, both for acceptance testing and for unit testing, but it required changes to the core framework and the core tools in order to get those tests to work in a CI environment. JEFFREY: Before we kind of get into the testing story there, some of the issues were around determinism of reliably reproducing your whole NativeScript environment and stack every time because that's such a key feature of doing it. And on a CI server, it's like, "Hey, we need this to load in the same exact packages every time." And so, we ran into challenges there. TARAS: I think we spent almost two days. There's example projects in different combinations. One thing that was off was that there's a pattern that is applied in a lot of the plugins in NativeScript ecosystem is installing things. So, you run npm install and npm install will generate some files. And so, when we're trying to move it over to a CI, there were files, like there's hooks, like TypeScript hooks that were excluded that you can ignore, but they were necessary to compile the TypeScript. And so, what was happening is when we're running these at CI, the application, we would build the app but the app would crash the moment that you start it. And the reason for that was that the JavaScript files that were transpiled from TypeScript to JavaScript, those JavaScript files were actually never included because they were never transpiled in CI because the hooks directory, like we weren't preserving it between our tasks and so... CHARLES: Right. We weren't caching. This was an artifact of the install. And so, we were caching the install, so essentially the yarn.lock was not changing. But the directory was not getting generated unless the cache key changed. TARAS: And we spent spent quite a lot of time... CHARLES: Two or three days out. TARAS: Yeah. CHARLES: What that said is, "Oh, nobody's really running this in CI." Nobody's actually building an app from scratch every time. TARAS: There are people in NativeScript team that actually does a great job of documenting. They did have example projects that exist but sometimes that example project doesn't fit like a perfect combination of what you're looking for. There was an example project that was showing how to run on CI but it didn't use TypeScript. And so, that's where we lost a lot of time. CHARLES: Right. JEFFREY: So, let's talk about testing since that's kind of the core, the most important part of why you even want continuous integration capabilities to begin with. What did we run into there? What did it look like? TARAS: Well, I think it's safe to say that we were really on a bleeding edge of testing capabilities in NativeScript ecosystem with Angular, at least. But I think it was still an interesting project. We were using the latest builds. And I have to say I think this is one of those things that's going to be kind of consistent through this, is like the people in NativeScript team are amazing. They're so easy to work with. They're so accommodating. When we ask for stuff, they're on it. But it was a lot of things we're trying to figure out like how do we run unit tests, what can we do. Ideally, we wanted to run, first and foremost, we started with how do we run functional testing. So we spent quite a lot of time trying to get Appium set up. I spent a good two to three weeks on that and it was not productively spent time. CHARLES: I think ultimately, we had to pull back from it. And there were a number of reasons. Part of that is there are multiple paradigms for how you can build your NativeScript application. So as we speak, there's a move towards using Webpack to build all of your JavaScript in your style sheet assets because it's very much like a React Native application. You've got style sheets, you've got JavaScript assets, that some of them might be in TypeScript, some of them you might be using Babel, and you need to actually transpile them down to include them in a way that your underlying JavaScript runtime is going to be able to understand. But that wasn't always so. They have their own build system and packaging system, they kind of used the TypeScript compiler ad-hoc, if you were using TypeScript, which we were. And so, this was kind of this orthogonal complexity, I guess, where you have your unit testing and it has to play nice with this one package or Webpack. There were multiple ways to package your app. And so, we ran into problems where, like TypeScript kept coming up as a problem and the way in which we were bundling our assets. So, in order to get TypeScript to work, we kind of had to get Webpack running. But the problem is it felt like three quarters of the tooling wasn't Webpack compatible yet. And so, it meant that other pieces of the build were breaking because of this. And so, we had to be on the bleeding edge of several different aspects of the runtime. And the problem is when you're on the bleeding edge, that can break other stuff. TARAS: But there's complexity in running on native platforms that I think a lot of this complexity is kind of leaking to development experience because one of the challenges is your tests need to run on the native device in the application. So, you have to build the app. You have to push the app into the actual device. So, there's like all the setup of installing the at the app on the device. CHARLES: You have to launch the simulator. TARAS: Yeah, right. CHARLES: To make sure the device is connected. TARAS: And you run your tests in there. So, that created kind of this situation where we say let's just kind of set Appium aside and just use unit testing which is a very small fraction of the kind of testing that we actually want to do. It will test very little. But let's just do that because getting functional testing to work was really kind of not going anywhere. So once we start doing unit testing, one of the challenges is that it takes like 30 seconds to start your tests. And then, if you for whatever reason, made a mistake, the moment you cancel the build, it leaves, like it doesn't clean up of itself well. So, it leaves processes running in the background. And so now, you spend another like 10 to 15 minutes Googling around for a cookie, "How do you find these processes and stop them?" So, we eventually settled on having a script that does that, but this is the kind of things you have to end up doing because there's a bunch of things that are wired together, but they're not wired together in a way that is seamless. And so, you end up kind of just debugging a lot of stuff where you just want to run some tests but you end up doing all these other stuff. CHARLES: Right. TARAS: And you spend a couple of minutes just doing something that you'd expect to happen in like 20 seconds. CHARLES: Right. There is a feeling that every aspect of the system is coupled to every other aspect of the system in kind of varying ways of interconnectedness. And that's not what you want for a very, very complex system. You want it to be extremely modular. So, I think we should keep the command line tool. There's probably a separate discussion, I think, about that. But you have to close the book on the Appium and the unit testing. I think the other problem was that you have to run these things on simulators. On macOS, that's not a problem because the simulators ship with X code. And so, you don't actually require an external service. Whereas in CI on Android, it's very unlikely that you're going to have Android emulators on hand because they require a separate virtual machine. Android emulation is actually quite heavy. If you're running through Android Studio or something locally, you essentially need VirtualBox or some equivalent to run your Android simulator because you actually need that simulated hardware. If I understand correctly, that was actually not something that had been really accounted for. It was that you might want to be running simulators not on the same machine as what you were developing on or what the actual that you were building on. TARAS: Yeah, a lot of the tooling seems to be designed around this idea that you're going to be building and running everything on your machine. And so, you can spin up a virtual machine easily. But in CircleCI, for example, they don't support running a virtual machine inside of a Docker container because for that, you need a feature of a virtualization that is not supported in many CI platforms. You have to run a parallel server if you want to have like Appium running, for example. You need to have a separate server running like an Azure or a Google Cloud somewhere that is able to run virtualized servers that have a host machine that's being guest systems that are running the actual Android emulators of different versions. And so, when I started doing research in this, there are companies that are doing this really well but it's not unusual to be using hardware from Amazon that costs thousands and thousands of dollars per month. I think for anyone who's getting into mobile development, I would say the hidden gem of Android world is Genymotion. Those that do a lot of Android development, they know about it. But Genymotion has both like a desktop environment and it has SaaS offering that they're in the process of releasing. And so, what it allows you to do is when you run it locally or on your local machine, it allows you to create a virtual machine that is running in VirtualBox and then it allows you to run kind of optimized environment for running Android. And when you do that, it's really fast. It's very smooth. It makes running Android devices locally as easy as it is to run iOS devices on macOS. CHARLES: I remember starting out and trying to actually just get any Android emulator running on my Mac and I couldn't even do it. JEFFREY: It was such a huge time saver. CHARLES: Yeah. TARAS: And to have this Saas offering is really great because you could basically create your virtual machines on demand and then you install into a virtual machine from your CI server and then you run your tests there. That's kind of the key that I found to be able to run tests and automate it against emulated devices for Android. Genymotion is really great. CHARLES: Yeah. Again that's the kind of thing that you need when you're in CI. And so, one of the things, I think, one of our discoveries is that there just isn't -- when we started working on this and we haven't seen a culture of running these tools in the cloud and accounting for the fact that you might have not all of the tools running on the same machine. From, I would say, the beginning, I remember the kind of the diagnostics command didn't work but we were running it on a CI server. So, there's a diagnostics command that you run to see do you have this, do you have that, do you have that. It would work and give meaningful results when I wanted to debug my CI server because when we were initially getting set up, something wasn't building right, there was some dependency missing. And I just wanted a diagnosis but it was trying to install all those tools for me. And I was like, "No, no, no. I don't want you to do anything. I don't want to install them. I'm going to be doing all of that as part of the setup of the CI environment. It's going to be installed, it's going to be cached. I don't want you to just try and like massage my system into a suitable state for NativeScript development. I just want you to diagnose what is wrong. Tell me, am I missing this compiler? Maybe I've got the wrong version of Android SDK. Tell me what's going on." And I couldn't get that to work. That was very frustrating. I think it was because the kind of bulk of the assumptions was that it was going to be individual developers working on their own laptops or their own desktop computers to build, to test, to distribute these applications. I think that's becoming less and less the case. I mean, at this point, that's not a way that we're willing to operate. TARAS: And we eventually figured out how to do all this stuff, right? CHARLES: Yeah, we have. JEFFREY: We have. TARAS: We have the entire process working but it took a lot longer than one would imagine. It took all the time that we had allocated to it which we thought was very generous amount of time but it took like almost a month to get everything set up. The great part of this is that we do have now everything working. And so, there's a repo where people could take a look if they want to get all stuff working on CI, but it took quite a bit of work in figuring out. CHARLES: Yeah. Actually, I think worth probably a Screencast to show some of those capabilities because it is really exciting. I mean, when you actually think about the pipeline in its entirety. But we never were able to get functional testing working. TARAS: And then the challenge here is that because we were essentially looking at NativeScript, going back to this question like, "What do we need to be able to have like hundreds of developers potentially running on this platform?" And so there's a lot of considerations and this tool is just one of them. I think the other one that is a big one is like what are the capabilities of the view layer because that's where most of developers were spending most of their time. We got stuck a little bit about that because I spent a lot of time working in the view layer. The thing that was really great and the thing that I really liked about it is the fact that you have a collection of components that you can use in Angular. You render it as component and then that component is going to look correctly on iOS and is going to look correctly on Android. From a single code base, it's building appropriate components for iOS and Android. What I think is really confusing in that case, though, is because the Android and iOS components don't have parity in a sense. They don't behave exactly the same. And there is also a kind of a reputation in the NativeScript documentation that Android tends to be slower, much slower than iOS. And so, when you start to run into performance problems and you start to run into those pretty fast because it is not really clear what is necessary to not optimize NativeScript, when you start to run into performance problems, it's not really clear like where is it coming from. Right now, the profiling that they have for the UI is very limited. They're kind of in the process of migrating over to chrome.debugger, but profiling in chrome.debugger is not implemented. You can do performance optimization using Android tooling but that's only going to tell you performance of the Java side, or the iOS side is not going to tell you the performance of the code that's running inside of JavaScript. It's not really clear what is causing the problem. If you don't know what's happening, you kind of write it off as like, "I think it's just Android being slow." In reality, when you actually start to dig deeper, you realize there's things about the Android implementation of the components that are different or the views that are different than iOS. And it's the differences that add up to weird performance problems. That's probably the thing that gave me the most hesitation because one of the things that made me think like if we want to be able to give this to a team of like 50 people, we need to have our own view layer because we cannot rely on components. An example of this would be, they have a list ticker on iOS, it doesn't omit change events when you scroll. If the list is moving, it change events and not omit it. But on Android, every time that a different item shows up on a screen, it changes the selection. And so now, you've got this view that's a meeting on Android as a meeting change events. I made an issue around this and the response was that while there's a workaround that you can have for this, but that's hard. Work around is not a solution. CHARLES: Right. When you have a leaky abstraction like that. TARAS: Part of the problem is because people use leak abstraction. And so, what's happened in Native -- we actually got on the call with NativeScript core team and they're excellent in really being very helpful, understanding what the problems are, and providing pass on making things better. But what's happened as a result of having this leaky abstraction is that people are relying on the leak. And so now, the leak is the API. And so, we can't change that. JEFFREY: Right. CHARLES: And the answer that you really need there is, "We can't change that without breaking stuff. Here's our migration path for deprecating this and introducing a new API." And that gets more into the process stuff and it seems like the process for making changes to the underlying API, I think, could use a little love in the sense that it's kind of opaque as to where the platform is going. There's not a concept of like an [RSC], there's no roadmap about what to expect. What is this API going to look like in the future? Is this stable? If I were writing a software and someone said, "Hey, there's this leaky abstraction," I think my reaction would be, "We've got to fix this." And we also have to acknowledge that there are users who may depend on this. And so, we have to be very deliberate about it. TARAS: The challenge with this too is that NativeScript kind of outgrew its hands because I think originally, it wasn't meant to be hosting Angular and hosting Vue. Vue didn't exist. Angular didn't exist when NativeScript started. So I think what's happened is that these views that were available, I wouldn't call them components because they don't act like components, but they're exposed in Angular like components but the API feel like Vue objects. So these Vue objects that you consume, that you render in Angular, for example, or in Vue.js, they are the same APIs that NativeScript had before Angular and Vue.js. CHARLES: Right. You know what? It feels like there's a MVC framework, like a Circa 2010, 2012 MVC framework that has now become the foundational layer for Vue frameworks that have had significant advances in the way we conceive of model in Vue and how data is generated and passed around and how views are rendered off of the data and how reactivity is changed. But there's still, the underlying platform has not evolved. And in fact, this was originally user-facing APIs and now these APIs have become foundational for other user-facing APIs but haven't had the iteration and evolution to make them robust. TARAS: And flexible enough. As a result, you have the situation where not only is it really super easy to deoptimize the views simply because the requirements of keeping performance expectations are not obvious. One of the things that I found is that the list which is, lists are like 50% of most applications. Before I go into the problem with list, the nice thing about lists in NativeScript is that because they're interacting directly with native APIs, you have really fast list when they're optimized. They're really easy to work with. But they easily get deoptimized by the fact that the expectation to keep the list fast, you have to use this API in NativeScript called array observable and observable. And this is not to be confused with like... CHARLES: [Inaudible] observables? TARAS: Yeah. CHARLES: It's not to be confused, but in fact, every conversation involves a lot of confusion. Because we were using observables, right? TARAS: And we were actually using observables. So, we're using observable [inaudible] and we're using this array observables and object observables. And so, it's necessary for NativeScript to, essentially what it expects for list to be fast, is it expects that it's going to receive an array observable which is an object that wraps an array because it needs to know when an order or length of data rate changes. So what happens when you pass an array observable, a NativeScript array observable into a list? It will listen for change events on that object. But if you want to change the value of each of the items, like if you want to change a property on the object and have your view remain optimized, the array observable has to have an observable object which allows NativeScript ListView to listen for changes, property changes on the object. You pass this array observable which contains observables that ListView listens for changes on to make sure that it knows how to correctly apply this change to the list. If you don't have this magic, like if you haven't figured out this recipe for ListView performance success, you're going to have a really hard time because it's really not clear at what point and how this thing got deoptimized, why has it just gotten slower. CHARLES: There's a lot of iteration that needs to happen there and it's not clear what the plan, what the priority, or even how you will even begin to go about this. Because I think that the internal working is that it seems basically to be controlled by one company. I don't recall seeing any contribution from anybody except for Progress which is Progress Incorporated is the company that's kind of the controlling interest, the original company that developed it. TARAS: The way this showed itself very practically is that to make changes too -- so they have a ListView which comes with NativeScript public and there's RadListView which is the component that has a lot of stuff on it. Like if you want to pull to refresh or if you want to do like laser loading a data or if you want to do a filtering, you want to do -- so most people use RadListView. But RadListView, you can install, so there's no limitation when you build to install it, and your node modules has the source code for that. But the source code, the original TypeScript code, untranspiled code is not publicly available. They have a process for doing this and it's very nice that everybody's very kind and very accommodating. You send an email, they'll give you access to this repo and then you'll have the ability to contribute. NativeScript core team is very helpful and they're open to contributions. There are changes that need to be done to the Angular implementation to make it faster without having to put the requirements of the observable thing, and so they can give you a path to make that stuff happen but it's not open source in the sense that it's not a traditional open source that we would kind of expect. So, there's all kinds of hoops that you need to jump through and the source code is very difficult to read because it's transpiled from TypeScript to JavaScript. CHARLES: And there was a certain level of opacity in terms of process. For example, I filed an issue which was actually a blocker. For us, it was actually causing our Android build not to work. I didn't hear anything about it. And then, all of a sudden like four days later, a fix came through referencing another repository on which this thing depended with. There was not a lot of context service. So it was obviously referencing a bunch of context that probably happened between two people in a face-to-face conversation. But I couldn't really tell what was going on, why it was an issue, because there was no comment. It was just a pull request that was referencing this issue. I never got a notification. I actually had to go and be like, "Hey, I really would like for this issue to be solved. I wonder if I..." I was actually going to post a, "Hey, is there any progress on this?" Or, "Is there any way that I can help? What can I do to get this looked at?" And I saw that there was another pull request that had referenced my issue. And it was merged and I looked down, but then there was no indication of when this would be available for public release, how I might be able to work around it. And so, the strange loop that didn't get connected was, "Hey, you've got a user who files an issue. You actually use this as the impetus to fix the issue and make a release." But then that whole process was completely invisible to me. TARAS: You know what? It sounds like you wanted for it to work [inaudible] but you got a pulling mechanism. CHARLES: Yeah, exactly. Well, I wanted someone to say like, "Hey, here's what's going on, and we're looking right into it." Or, "We're going to look into it in like two months," or, "We can't address this now. But here's a workaround for it." Or, "I don't have a workaround." That's just kind of the expectation that you have when you're playing with open source. In many ways, it does not feel like an open source project. TARAS: Let's just do a quick note about Saas. Jeffrey, what did you find about the styling of NativeScript views? JEFFREY: All the components that come kind of shipped as part of the NativeScript core set of components all have styles attached to them. They have CSS attached to them. And as part of the standard data script workflow, with your build toy, you have SaaS available which is very nice. But actually on a recent project, we're not using Saas at all. We're simply using post-CSS and we were able to kick out some CSS variables that turned out to be really nice for theming. So as kind of a future friendly experiment, we were trying to have a light theme and a dark theme since that is very recently now a core part of Android and very likely will be part of iOS this year, where there's kind of a light theme and a dark theme for everything. We were trying to do that. The simplest way to do that with standard web tools is with CSS variables. You can have the flexibility, you have the theming with those. It's so nice. You just, "Hey, my primary color is this color in one scenario and it's this color in another." And we just didn't really have the flexibility to do that with SaaS by itself. And so, that's kind of a limitation of the tooling right now that I hope in the future, we'll have some more sophisticated CSS tools. And really, NativeScript's move toward Webpack and having that as a primary part of the workflow really opens up that possibility that I hope somebody runs with in the near future. TARAS: Yes, let's bring it all back together. CHARLES: Can we pause for a moment? Because I actually do think it's important that we at least touch on the command line. I can give a little bit of a kind rant in here but I think that's actually something really important that we have to talk specifically about that. The other thing that I wanted to touch on very briefly as we kind of draw to the close is the command line tooling, in particular in NativeScript. I think that this is probably one of the weakest points of the platform. And again, I don't want to disparage anybody working on NativeScript. It's an extraordinarily complex problem. This is a command line tool that needs to manage launching simulators, installing things into simulators, pushing code to those simulators. It needs to handle hot updates to things that it's running on, devices and simulators. So, it needs to be building JavaScript assets either with Babel or with TypeScript. It needs to be building those SaaS assets that you were just talking about, image assets. But it needs to be doing all of this for two platforms, so it needs to be managing everything that I just described. It needs to be managing on iOS. Everything that I've just described needs to be managed on Android, as well. It needs to work for a single developer's desktop. It also needs to work with all of those components that I just described distributed out in the Cloud. So, we're talking about an extraordinarily complex piece of software. And I think that unfortunately, the NativeScript CLI does not inspire confidence because it can do all of those tasks. But Taras, you also mentioned often if you stop the process midway, it will leave a thousand things open and they're just spewing output to your console. The console output, unfortunately, means there's a big noise to signal ratio because it puts out all of the content for Webpack. Every little thing that it's doing with any of the devices, it's logging to the console. So, it doesn't give you a sense of control. So, what you really are looking for in terms of a command line is, "Hey, I've got this incredible sprawl of complexity and I want to feel like I'm on top of it." And unfortunately, by leaving these things open and having so much console output and having the console output not be formatted well, there's all kinds of colors. Every single tool that you're using whether it's Webpack or whether it's Karma or whether it's just console outputs that you are happing inside of your NativeScript application, the brand of those tools comes through. Webpack is a great example. Its console output feels very Webpack. So when you've got Webpack content randomly interleaved with your console content from your Mocha content, from Karma, all of these competing brands, it doesn't feel like a cohesive developer experience. And so, I really, really hope that -- so, to the point being where I felt like I could not live with that command line tool without rewriting it myself. If we want to use this platform long term, we'd have to either have an alternative command line tool or really, really, really help the NativeScript team completely and totally rewrite the command line experience. TARAS: I would love to work on fixing a lot of these parts about NativeScript if there was a way to actually do it in terms of like, if they wanted to pay us to help them kind of bring some of these things to a state that would match. For example, what's available in Ember or available in React CLI, I would love to do that. CHARLES: React Native, yeah. TARAS: Yeah, let's do that work. But who knows what's in store? A lot of awesome platform like the idea around NativeScript architecture is fascinating and it's really, really powerful and really wonderful people doing some, trying to tackle really challenging problems, but it's all glued together in a way that doesn't instill confidence. And it just makes everything feel wobbly, just makes it feel like you never know, is it a problem? Where's the problem from? What is causing this? CHARLES: Yeah. And if I fix this thing, is it going to break something else? TARAS: Yeah, we've seen it happen actually with one of the solutions that was introduced to a bug that you were referring to earlier. CHARLES: Yeah. So that was our three months experience working with NativeScript. TARAS: We are considering other things now, very seriously looking at Flutter as an alternative for the same client, same scenario. Flutter is looking pretty exciting. There's a lot of things that are really good there. So in three months, we'll do another report and talk about Flutter and what we found. So, that's it. CHARLES: And I will say I'm actually not like super excited about dart but I'm in dart spot. JEFFREY: That's a whole other conversation for yet another episode. CHARLES: I think that, to continue the conversation maybe next week, next time we have kind of an internal podcast, is I would like to really talk about platform evaluation because really you need three months, at least, to get a good idea of this. Is this going to work for the next five years? And most of the time, we give it a week or give it a two week. Or someone comes on who's really excited about this one particular technology and you go off on that tangent. I think there's an interesting meta discussion about how do you select technologies. And we don't have time for that now, obviously. But it's definitely something that I want to have in the future. TARAS: Sounds good. I think that will be a good conversation for sure. CHARLES: I guess that is kind of the executive summary on NativeScript from our perspective. With us being three months in, I think, like you said, there's a lot there. Thank you for listening. If you or someone you know has something to say about building user interfaces that simply must be heard, please get in touch with us. We can be found on Twitter at @TheFrontside or over just plain old email at contact@frontside.io. Thanks and see you next time.
Темы: - Про конференцию AppiumConf - Сколько стоил билет. Как поехать на халяву? - Новости Appium и куда он идет - Стоит ли ехать в следующий раз - Про Appium для кофеварок и десктопа - Инсайды относительно поддержки Appium тестов в Selenoid Гости: - Сергей Пирогов - заводила подкаста - Ярослав Перенеровский - бог звука в подкасте - Иван Крутов - Разработчик Selenoid. 10 лет пилит годноту на Go и Java. - Евгения Гнатюк - работает в Польше, знает как поехать на конфу бесплатно Поддержите подкаст www.patreon.com/automation_remarks Присоединяйтесь к нашему Slack каналу http://qaguild-slack.herokuapp.com/ Читайте блог http://automation-remarks.com
В этом выпуске говорили о подходах и инструментах, которые применяются для тестирования мобильных приложений. Гости: - Сергей Пирогов - 0 без палочки в автоматизации мобильников - Ярослав Пернеровский - получил детскую травму после работы с Appium - Артем Никитин - обмазывался Robotium и Espresso и настраивает CI для Android/IOS - Алексей Панащенко - работает с Appium IOS/Android, делал CI и пытается бороться со скоростью IOS тестов - Евгения Гнатюк - работала с Appium Android/IOS +/- Cucumber. - Денис Яременко - работает с мобильниками почти с пеленок - Дмитрий Лемешко - знает, как писать нормальные тесты под Appium - Андрей Яременко - Appium+Cucumber Android/IOS, тот еще краб и нуб. Поддержите подкаст www.patreon.com/automation_remarks Присоединяйтесь к нашему Slack каналу qaguild-slack.herokuapp.com/ Читайте блог automation-remarks.com
Testing your mobile app is important! In this session, learn about UI testing and how to build UI tests, then run the UI tests on a variety of mobile devices in the cloud. Learn how you can go completely device free by using devices in the cloud for your development. Also, learn about using tools like Appium and Jenkins as part of your testing and QA process. We use PWA and native apps in this session to show the difference.
We tackle the testy topic of automated testing in the life of software projects. Kenneth & Len are joined by Joshua Lewis from nReality (formerly of the JCSE) about the ins and outs of automated testing. We tear through artificial boundaries to unpack the value of testing, as well as potential pitfalls. There are many different testing tools and styles available, and choosing the right approach can be difficult. We even learned about some new terms, and possibly what we've been calling "testing" should be called "checking", who knew? We learned that Kent Beck, the father of TDD, did in fact "rediscover" TDD from earlier authors who used the same principles with punch cards! As is common with talks on testing we explore the many techniques we're aware of, sharing lessons learned and try to settle on some heuristics that you could use in your projects. Which methods are the best? You'll have to listen! Follow Joshua online: - https://twitter.com/joshilewis - https://github.com/joshilewis - https://joshilewis.wordpress.com/ - http://www.nreality.com/ Here are some resources mentioned during the show: * JCSE at Wits - http://www.jcse.org.za/ * Context Driven Testing - http://c2.com/cgi/wiki?ContextDrivenTesting * Testing and Checking Redefined - http://www.satisfice.com/blog/archives/856 * Test Pyramid - http://martinfowler.com/bliki/TestPyramid.html * Why does Kent Beck refer to the "rediscovery" of TDD? - http://bit.ly/1StrUSY * Test Driven Development - http://www.extremeprogramming.org/rules/testfirst.html * Why I do TDD - https://joshilewis.wordpress.com/2015/11/25/why-i-do-tdd/ * DStv Digital Media - http://dstvdm.dstv.com/ * Selenium Browser Automation - http://www.seleniumhq.org/ * Appium - http://appium.io/ * Page Object Pattern - http://martinfowler.com/bliki/PageObject.html * Use "qa" CSS namespace - http://csswizardry.com/2015/03/more-transparent-ui-code-with-namespaces/ * Sunk cost fallacy - https://en.wikipedia.org/wiki/Sunk_costs#Loss_aversion_and_the_sunk_cost_fallacy * lend-to.me - http://lend-to.me * lend-to.me (on GitHub) - https://github.com/joshilewis/lending * lend-to.me eventsourcing experiment - https://github.com/joshilewis/lending/tree/experiment/eventsourcing * lend-to.me API - https://github.com/joshilewis/lending/wiki/API-Reference * Given When Then - http://martinfowler.com/bliki/GivenWhenThen.html * Continuous Integration - http://www.martinfowler.com/articles/continuousIntegration.html * Testing in Production - http://sdtimes.com/testing-in-production-risk-vs-reward/ * Ansible - https://www.ansible.com/ * Do you smoke test? - https://samsaffron.com/archive/2013/02/22/do-you-smoke-test * Stripe API (support test/live using different keys) - https://stripe.com/docs/api * Consumer-Driven Contracts - http://www.martinfowler.com/articles/consumerDrivenContracts.html * Swagger - http://swagger.io/ And finally our picks Kenneth: * pacto - https://github.com/thoughtworks/pacto Len: * miniKanren - Dan Friedman and William Byrd - https://www.youtube.com/watch?v=5Q9x16uIsKA Thanks for listening! Stay in touch: * Socialize - https://twitter.com/zadevchat & http://facebook.com/ZADevChat/ * Suggestions and feedback - https://github.com/zadevchat/ping * Subscribe and rate in iTunes - http://bit.ly/zadevchat-itunes
More Than Just Code podcast - iOS and Swift development, news and advice
This we discuss various implementations of Stack Views, UI Testing and Unwind Segues. An Apple Watch Easter Egg is debunked as well as the Stolen app. Picks: Desktop Neo, A simple tip to reduce App Store rejections and Testing in iOS. Episode 75 Show Notes: UIStackViews Sam Davies Introducing Stack Views Series (Swift) XCode 6: How To Debug The View Hierarchy In Your Storyboard Mysteries of Auto Layout, Part 1 TZStackView OAStackView You need to read this review Canada Mac Prices Oil price falls below $28 a barrel - less than cost of an actual barrel Calabash Appium Robotium Expresso Nimble Snapshots - Ash Furrow Eidolon code walkthrough unwind segues vs delegation in storyboards Apple Watch Easter Egg Stolen, which turned your Twitter profile into a trading card, is pulled from the App Store Tim Mitra - RoundaboutFM podcast Episode 75 Picks: Desktop Neo A simple tip to reduce App Store rejections Testing in iOS Series
Get your JS Remote Conf tickets! 02:20 - Burke Holland Introduction Twitter GitHub Blog Telerik 02:40 - TJ VanToll Introduction Twitter GitHub Blog Telerik 03:04 - NativeScript + Angular; The DOM @nativescript Sebastian Witalec: Building native mobile apps with Angular 2 0 and NativeScript @ AngularConnect 2015 JavaScript Jabber Episode #186: NativeScript with TJ VanToll and Burke Holland 07:04 - Getting Started/Setting Up a New Application NativeScript Getting Started Guide Plugins and npm modules plugins.telerik.com Power Features: Skill Reuse 10:34 - Code Reuse Data Models Components 17:00 - Platform Specific Customization 22:12 - Plugins (Cont’d) Telerik's Verified Plugin Marketplace Podfile 27:36 - Doing Things with Angular + NativeScript Animation ngAnimate TypeScript IDEs 34:14 - Testing github.com/NativeScript/NativeScript/tree/master/apps/tests Appium 37:08 - What’s coming down the pipeline? Documentation, Samples 39:19 - Comparing Angular + NativeScript to React Native The iPhreaks Show Episode #128: JavaScriptCore with Cesare Rocchi 42:31 - UI for NativeScript Picks Pebble Time Steel (Chuck) Fathead (Chuck) Apple Photos (TJ) Michigan State (TJ) Buy albums you love to support music artists (Burke)
Get your JS Remote Conf tickets! 02:20 - Burke Holland Introduction Twitter GitHub Blog Telerik 02:40 - TJ VanToll Introduction Twitter GitHub Blog Telerik 03:04 - NativeScript + Angular; The DOM @nativescript Sebastian Witalec: Building native mobile apps with Angular 2 0 and NativeScript @ AngularConnect 2015 JavaScript Jabber Episode #186: NativeScript with TJ VanToll and Burke Holland 07:04 - Getting Started/Setting Up a New Application NativeScript Getting Started Guide Plugins and npm modules plugins.telerik.com Power Features: Skill Reuse 10:34 - Code Reuse Data Models Components 17:00 - Platform Specific Customization 22:12 - Plugins (Cont’d) Telerik's Verified Plugin Marketplace Podfile 27:36 - Doing Things with Angular + NativeScript Animation ngAnimate TypeScript IDEs 34:14 - Testing github.com/NativeScript/NativeScript/tree/master/apps/tests Appium 37:08 - What’s coming down the pipeline? Documentation, Samples 39:19 - Comparing Angular + NativeScript to React Native The iPhreaks Show Episode #128: JavaScriptCore with Cesare Rocchi 42:31 - UI for NativeScript Picks Pebble Time Steel (Chuck) Fathead (Chuck) Apple Photos (TJ) Michigan State (TJ) Buy albums you love to support music artists (Burke)
Get your JS Remote Conf tickets! 02:20 - Burke Holland Introduction Twitter GitHub Blog Telerik 02:40 - TJ VanToll Introduction Twitter GitHub Blog Telerik 03:04 - NativeScript + Angular; The DOM @nativescript Sebastian Witalec: Building native mobile apps with Angular 2 0 and NativeScript @ AngularConnect 2015 JavaScript Jabber Episode #186: NativeScript with TJ VanToll and Burke Holland 07:04 - Getting Started/Setting Up a New Application NativeScript Getting Started Guide Plugins and npm modules plugins.telerik.com Power Features: Skill Reuse 10:34 - Code Reuse Data Models Components 17:00 - Platform Specific Customization 22:12 - Plugins (Cont’d) Telerik's Verified Plugin Marketplace Podfile 27:36 - Doing Things with Angular + NativeScript Animation ngAnimate TypeScript IDEs 34:14 - Testing github.com/NativeScript/NativeScript/tree/master/apps/tests Appium 37:08 - What’s coming down the pipeline? Documentation, Samples 39:19 - Comparing Angular + NativeScript to React Native The iPhreaks Show Episode #128: JavaScriptCore with Cesare Rocchi 42:31 - UI for NativeScript Picks Pebble Time Steel (Chuck) Fathead (Chuck) Apple Photos (TJ) Michigan State (TJ) Buy albums you love to support music artists (Burke)
© 2020-2025 Ivy Podcast Discovery LLC
