
Sign up to save your podcasts
Or


In this episode of the Test Guild Automation podcast, I have a conversation with Dalton, a self-taught SWIFT developer, about the SWIFT driver for the Appium framework and general UI testing. Dalton currently works at a company that deals with multi-platform UI automation and has developed a SWIFT package to interact with the Appium server. The discussion includes the advantages of using Browser Stack App Live for cloud-based mobile testing, eliminating the need for maintaining a personal device cloud.
Dalton shares his journey into SWIFT development, the reasons behind creating the SWIFT driver, and how it functions within the Appium framework. We touch upon the differences between using native frameworks vs. multi-platform setups and address common concerns around Appium's speed compared to native frameworks. Dalton explains that the SWIFT package is quite minimal, focusing on essential functions like clicking and sending keystrokes, with an invitation for contributions to enhance its functionality.
Dalton also talks about using both emulators and real devices for testing, preferring real devices due to the RAM-heavy nature of parallelizing emulators. The conversation covers why Dalton prefers and utilizes SWIFT, citing its concurrency capabilities and language features. Dalton shares insights on the open source contribution process, highlighting the welcoming nature of the Appium community. He mentions some challenges faced, particularly the initial lack of documentation and variations in naming conventions compared to other drivers.
Dalton describes his transition from using Safari to Chrome for web testing, attributing better support to Chrome's more successful integration. He emphasizes the educational benefits of contributing to open-source projects, including enhancing one's skills and understanding different coding structures. To onboard testers, Dalton advises starting with understanding SWIFT and setting up test client server communication. He shares that UI testing provides comprehensive coverage, ensuring the functionality aligns with user perspectives.
Dalton reveals that they currently use GitHub runners and actions in their code pipeline, testing new builds with automated suites to identify issues before release. He attributes the benefits of UI tests to catching bugs early in the development cycle and providing safety nets against faulty releases. Dalton wraps up by inviting listeners to try the SWIFT Appium and underscores the significance of UI testing in understanding user interactions and ensuring robust application functionality.
By ChristopherIn this episode of the Test Guild Automation podcast, I have a conversation with Dalton, a self-taught SWIFT developer, about the SWIFT driver for the Appium framework and general UI testing. Dalton currently works at a company that deals with multi-platform UI automation and has developed a SWIFT package to interact with the Appium server. The discussion includes the advantages of using Browser Stack App Live for cloud-based mobile testing, eliminating the need for maintaining a personal device cloud.
Dalton shares his journey into SWIFT development, the reasons behind creating the SWIFT driver, and how it functions within the Appium framework. We touch upon the differences between using native frameworks vs. multi-platform setups and address common concerns around Appium's speed compared to native frameworks. Dalton explains that the SWIFT package is quite minimal, focusing on essential functions like clicking and sending keystrokes, with an invitation for contributions to enhance its functionality.
Dalton also talks about using both emulators and real devices for testing, preferring real devices due to the RAM-heavy nature of parallelizing emulators. The conversation covers why Dalton prefers and utilizes SWIFT, citing its concurrency capabilities and language features. Dalton shares insights on the open source contribution process, highlighting the welcoming nature of the Appium community. He mentions some challenges faced, particularly the initial lack of documentation and variations in naming conventions compared to other drivers.
Dalton describes his transition from using Safari to Chrome for web testing, attributing better support to Chrome's more successful integration. He emphasizes the educational benefits of contributing to open-source projects, including enhancing one's skills and understanding different coding structures. To onboard testers, Dalton advises starting with understanding SWIFT and setting up test client server communication. He shares that UI testing provides comprehensive coverage, ensuring the functionality aligns with user perspectives.
Dalton reveals that they currently use GitHub runners and actions in their code pipeline, testing new builds with automated suites to identify issues before release. He attributes the benefits of UI tests to catching bugs early in the development cycle and providing safety nets against faulty releases. Dalton wraps up by inviting listeners to try the SWIFT Appium and underscores the significance of UI testing in understanding user interactions and ensuring robust application functionality.