Want to share your experience & expertise at the upcoming Automation Guild '25?

•AI/ML in Testing/Automation: Increased use of AI - Want to incorporate AI into their workflows more effectively. •Playwright: Many respondents mentioned Playwright for e2e testing. •Automation Best Practices (no framework specific) •Test strategy, Test planning and estimation •Expanding the scope of testing: Want to expand their testing coverage to different facets of their organizations or different types of tests. •Stability and better tools: Improving stability in their processes and having access to better tools. •Performance Testing •Test Data Management •Mobile Testing/Automation •Basics, "revisited" - how to make sure you aren't missing foundational skills or items. •Accessibility testing •Cloud & DevOps: topics around testing of cloud based, data processing apps, Terraform testing, Observability •Desktop automation, embedded device automation •Test Leadership/Career Advice: Want to move into leadership and strategy roles. Some are looking to move into more architectural or strategic roles, taking on responsibilities that go beyond day-to-day testing tasks. •Identifying niches and growth opportunities: Learn more about areas where they can expand their expertise, potentially uncovering new niches or career growth opportunities. •API Testing/Contract Testing •Security testing: Topics like Proxy tracking cyber-attack self-executing penetration testing. •Advanced Testing Techniques •Learning New Technologies: There are mentions of "Learn new technologies and programming language quickly", "reskilling testers to adopt newer technologies", and "how to learn new technology".

•UI Automation Challenges: Many respondents mentioned issues related to UI automation, such as it taking too long, being unreliable, and the challenge of handling dynamic locator values. There's also mention of the flakiness of UI tests, especially in complex scenarios with multiple redirects. •Flaky tests: Unreliable test results, which consume valuable time to debug and stabilize. •Maintenance and Test Data Management: Maintenance of existing automation and tests was a recurring theme. This includes the challenge of keeping scripts up-to-date with changing application features and dealing with framework updates. Managing and maintaining test data for various scenarios was also a significant concern. •Integration and Mocking Challenges: Several respondents mentioned difficulties in mocking services in a distributed microservices environment, especially with tools like Wiremock. There were also mentions of challenges integrating various tools and services, such as Playwright with Azure Services and Appium with SauceLabs. •Mobile Automation: Starting with and scaling up mobile automation was a concern for many. This includes challenges with specific tools like Appium and the complexities of mobile app hybrid automation. •Learning and Upskilling: A lack of programming skills and the need to quickly learn new technologies and programming languages were frequently cited. This includes upskilling for specific tools like Cypress and understanding advanced coding concepts. •AI and Advanced Testing Techniques: Many respondents expressed interest or challenges in integrating AI into their test automation processes. This includes leveraging generative AI techniques, using AI for test case generation, and keeping up with cutting-edge AI-based testing technologies. •Organizational and Process Challenges: Getting buy-in from other team members and convincing stakeholders of the benefits of automation were significant concerns. Additionally, having a good process, balancing between manual and automated testing, and dealing with changing product roadmaps and unclear specifications were also mentioned. •Cloud and Infrastructure Challenges: Several respondents mentioned difficulties related to cloud environments. This includes running automation test suites on the cloud without manual intervention, dockerizing existing Selenium scripts, and challenges with specific cloud platforms like Azure. There's also mention of the need for solutions that can be hosted on internal networks and not just cloud-based. •Advanced Testing Scenarios: There were mentions of specific, advanced testing scenarios that respondents found challenging. This includes testing data science projects, mechatronics in vehicle autopilot, security testing, in-sprint automation, and testing integrations with tools like Adobe Analytics. The diversity of these challenges underscores the wide range of applications and domains in which automation testing is applied. •Team and Collaboration Challenges: Some respondents highlighted team dynamics and collaboration challenges. This includes getting buy-in from developers, dealing with developers' code that affects automation, training team members unfamiliar with coding, and the challenge of introducing automation into small Agile teams. There's also mention the difficulty in transitioning from testing a monolithic application to a microservice-based system.

•Genuine Content Over Vendor Promotion: Multiple respondents preferred genuine content, craftsmanship workshops, and practical sessions over vendor-specific content. They would appreciate less promotion and more real-world insights. •Practical Over Theoretical: There's a desire for more practical demonstrations and real-world examples rather than just theoretical knowledge. Attendees want actionable insights they can apply in their roles. •Presentation Quality: The charisma and presentation skills of the presenter matter. Even if the topic is interesting, its presentation can make a significant difference. Some attendees suggested guiding presenters on enhancing their presentation skills. •Access to Materials: Attendees would appreciate easy access to materials, supporting documents, and a connection to an active community. •Diverse Topics: While many respondents are interested in AI and its applications in testing, there's also a desire for a broader range of topics. Some attendees wished to move beyond just UI testing and delve into backend, performance, security, and other areas. •Vendor Presentations: While there's a general sentiment against too much vendor-driven content, some attendees expressed that if vendors provided deeper, more valuable sessions that connect their products to practical use cases, it would be more beneficial. •Real-World Challenges: Attendees are interested in discussions about real-world challenges in the testing domain, such as the evolution from QA to QE to DE, challenges in automation maturity, and the impact of rapidly evolving technology. •Interactive Workshops: Code-along workshops and interactive sessions were appreciated in previous events, and attendees would like to see more of them. •Limit AI Focus: While AI is a trending topic, some attendees expressed that they would like the event not to be overly focused on AI. They want a balanced approach that addresses current challenges faced by testers •Sponsorship Feedback: There's feedback about sponsors' presentations being too high-level and not adding value. Attendees would appreciate sponsors connecting their products to useful, longer sessions and providing practical insights.