Discussions

Please do share your biggest challenge or difficulty when it comes to automation testing. It could be anything—tool limitations, script maintenance, lack of resources, learning curve, or any specific issue you face. Your input will help us understand common pain points and work towards better solutions for automation testing.

Hello.I was thinking of making a side project and would require your input.What’s the one Cypress plugin (or testing tool feature) you wish existed yesterday? 🤔🚀If you could add any missing functionality to Cypress, Playwright, Selenium, or any other test automation framework, what would it be?Maybe a:✅ Smarter element locator strategy 🔍✅ AI-powered flakiness analyzer 🤖✅ Better test reporting & visualization 📊✅ Seamless integration with CI/CD pipelines ⚡Let’s crowdsource ideas! What’s the biggest gap in your testing stack that a plugin or library could solve? 

It is challenging to evaluate the results of GenAI applications because there are no expected results, only results from an acceptable range.  For summarization GenAI use cases, what are the most common evaluation metrics?

People always make trends posts about 2024 2025 etc and they all have the same trends on them. AI Automation Performance etc …So my questions towards you is what are you seeing right now as a trend? What’s popped up more often?For me it would be A11Y - Accessibility testing, I see more and more people investing into it, many posts of it online. It might just be due to me not having much experience in it compared to other things.What are you spotting? 

Hi folks,I’m focusing on tools and I want to ask the community this:Where do you learn about new tools?I use a lot of different sources which I plan to share, but I’d like to know where you learn about tools. Sharing sources with new learners is going to open their options for what tools to play with, which can only be a good thing. So reply with where you find tools and why you use that source.And, as always, we are grateful for your contribution 

As test suites grow, maintaining automated tests and handling script breakages can become challenging, especially with frequent application updates. I've read about AI-based tools that automate test maintenance and implement self-healing capabilities, which adapt scripts to changes in the UI or functionality.Could you share your experiences using these AI-driven solutions for automating test maintenance? Specifically, I'm curious about:How effective they’ve been in reducing manual intervention for script fixes Any free tools or open-source alternatives you've tried and their limitations How these tools integrate with existing automation frameworksI’d love to hear about any success stories or challenges you’ve faced while using them!

How do you setup up a test automation project? Do you have a template that you use? Do you google each time you want to start. Do you reach for the documentation? I am curios what is your approach. Also, here is a link to a new resource I found on the topic that might help organize the test project creation, especially if you are just starting out  

You're testing a payment gateway API responsible for handling financial transactions. Its primary function is to ensure that funds are transferred only when the account balance of the user is sufficient. In the test cycle, the following scenario was observed.Two simultaneous requests from two different devices for the same transaction-drawing money, for example, ₹10,000-an API processes both requests, deducting ₹20,000 from the account while it holds only ₹15,000.

What do you believe is the most significant factor contributing to faster and higher-quality software releases? Please select the option that you consider most important.

Are you a tester looking for tools to boost your productivity? Look no further! I’ve curated a YouTube playlist: Chrome Extensions for Testers 🎥. It’s packed with tips on extensions that will transform your workflow, from debugging to performance testing and beyond. ✅ What you'll discover:🔹 Top Chrome extensions for testing efficiency🔹 Step-by-step tutorials for setup and use🔹 Hidden gems to streamline your QA processWhether you're a manual tester or a test automation pro, these tools will help you save time and improve your results.💡 Check out the playlist and supercharge your testing skills today!👉 https://www.youtube.com/watch?v=0bri0j9_ztM&list=PLNQq42pqd-rwLSWHlXbq2AvcPiAJjNiEh  Let’s make testing smarter, not harder. If you find these tools useful, drop a comment or share your favorite extensions!#SoftwareTesting #ChromeExtensions #QualityAssurance #YouTubeLearning #ProductivityTools #TestingTips

Task: Add automated tests to your project's CI pipeline and ensure they run automatically with each code change.  Capture a screenshot of your CI tool running automated tests. 

Task: Explore strategies for managing test data effectively in a DevOps environment. Implement one such strategy in your project.  Capture: A screenshot or description of your test data management approach. 

We are building a stand-alone web and mobile application that, when finished, will require one of our order modules to have as one of its features an editable PDF. Since the third-party PDF editor we could find already supports a strong ability to edit-the specifics being Adobe Acrobat-we are challenged with how we will ensure that changes the user saves will be written into our application database rather than into the third-party editor system.Our development team is facing an impasse in the effort to implement this functionality. Do you have suggested approaches or tools allowing PDF editing with direct data saving to our database? Thank you in advance for any suggestions or best practices you could share.

Which test automation tool has the most weekly downloads according to npmtrends? A) Cypress B) Playwright C) Puppeteer

Automation often faces challenges with non-deterministic tests, where external factors like network latency, third-party services, or data inconsistencies cause varying results. These flakiness issues can undermine test reliability and make debugging difficult.What approaches do you use to stabilize such tests? Are there any patterns or strategies you recommend to reduce flakiness and improve overall reliability?

I’m curious to know what’s the one QA tool that has saved you the most time during your testing process? Whether it’s for test automation, bug tracking, performance testing, or something else, I’d love to hear what tool you can’t live without and why it stands out to you.

In the world of testing, oh what a sight,There are development methodologies left and right!Waterfall, Agile, DevOps, and more,Each with its own unique score. Waterfall's like a river, flowing down,Each phase completed before the next comes 'round.Design, coding, testing, all in a row,In the end, a product that's good to go. Agile's more like a jungle, wild and free,With sprints and stand-ups, and lots of team camaraderie.Iterations and feedback, they all do their part,To create a product that's work of art. DevOps is like a machine, moving fast,Continuous integration, deployment, and testing that lasts.Automation's the key, with pipelines in play,To deliver software every single day. But which one's the best, you may ask,Well, that depends on the testing task.Each has its own strengths and flaws,So pick the one that suits your cause. In the world of testing, there's no one size fits all,So experiment and find the right call.And when you've found the right way to test,Your product will

When testing large stories with limited time, efficiency becomes crucial. What tools or techniques do you rely on to streamline the testing process? How do these tools help you prioritize critical paths, automate repetitive tasks, and manage test coverage quickly? Additionally, what methods do you use to ensure that testing is thorough despite the time constraints?

 In this video, Kshitij Nigan (happy) , a Senior Product Security Engineer at Tricentis with 11 years of experience, discusses the power of DevSecOps in software development. He highlights its cultural impact, emphasizing security as a shared responsibility. @nigamelastic also covers key practices like vulnerability detection, compliance, and proactive security. This video is a must-watch for those interested in integrating security into the development process. 

 Are you ready to supercharge your coding journey? @IOan brought a great opportunity.  From Ioan:  I am excited to share a fantastic opportunity for the Shiftsync community to enhance their skills and master the art of GitHub through a series of FREE courses.These courses are designed to empower you with the knowledge and expertise needed to make the most out of GitHub for your projects.  Unlock the Power of GitHub with These Free Courses:1. GitHub Essentials for Beginners:Dive into the basics of GitHub with this beginner-friendly course. Learn how to create repositories, manage branches, and collaborate effectively with other developers. Perfect for those new to version control or looking to solidify their understanding.2. Mastering Pull Requests and Code Reviews:Pull requests are at the heart of collaboration on GitHub. This course will guide you through the ins and outs of creating pull requests, handling code reviews, and ensuring your contributions align with best practices. Take

Hey ShiftSyncers,Quick one: Anyone doing Advent of Code by Eric Wastl? For those who might be unfamiliar, Advent of Code is an annual coding event that involves solving a series of programming puzzles throughout December, each becoming progressively more challenging. For those already diving into the Advent of Code, I wish you the best of luck! Feel free to keep us posted on your progress, share interesting puzzles, or ask for help if needed. 

After a successful sanity test in the acceptance environment, it's puzzling when code breaks despite no new deployments or changes being made. This situation can be caused by several underlying factors. Potential causes may include environmental inconsistencies, such as differences in configuration settings, server performance issues, or data discrepancies between test runs. External dependencies like third-party services or APIs might also introduce changes that were not accounted for during testing. Additionally, timing-related or concurrency issues may not surface during initial tests but cause functionality to fail under different conditions. Identifying the root cause requires a thorough investigation into both the test environment and any external factors that could impact the system's behavior.

In real-world testing scenarios, it’s common to encounter projects where documentation is incomplete or requirements are unclear, yet the need for thorough testing remains critical. This situation can pose significant challenges for testers, who must rely on limited information to ensure the application meets both functional and business needs. In this discussion, we invite QA professionals to share their approaches for handling such situations. Techniques may include collaborating with stakeholders for clarification, using exploratory testing to uncover edge cases, developing assumptions to create test cases, and leveraging past experience or domain knowledge. The goal is to explore how testers can maintain test quality, reduce ambiguity, and ensure coverage when formal requirements are lacking.

  What testing tools are in your current tech stack?Are there any that are a specific requirement for your job? 

We recently deployed a feature that passed all tests in our Acceptance environment (functional tests, regression, smoke tests), but after deployment to Production, we encountered issues such as broken functionality, unexpected errors, and performance slowdowns.Here’s the setup:Acceptance and Production environments are as close to identical as possible (same configurations, database versions, and server setups). Automated and manual tests ran successfully in Acceptance. The feature in question interacts with both third-party APIs and a legacy system.However, after deployment to Production, users are facing:API timeouts and failed calls to third-party services. Slower performance in certain areas of the application. Data inconsistencies when interacting with the legacy system.Has anyone experienced a similar issue where everything works fine in Acceptance, but things fall apart in Production? What are some potential causes or overlooked areas that could explain this discrepancy?I’m part