Discussions

Hey folks! I'm really excited to see you in today's ShiftSync webinar 'From Discovery to Automation - a deep dive into BDD'.I would love to hear your take on the following question (well, it's more like two questions in one...) :"According to you, what is the most valuable tool or practice in Behaviour-Driven Development and what makes it so important?”

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

AI is here and that is a clear fact.We are bombarded daily with content that is either fully or in parts generated by AI.But how good are we are spotting the “fake” content? I did a post a while ago asking how to spot text and was kind of impressed by the responses.Now… can you spot the image?  Give it a try

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?

Looking for some courses on security testing. Do you have any in mind that you can recommend?  ⁉ Would be interested in Web Security to start with and it can be free or paid.

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.

As QA professionals, we rely on a variety of tools to make our testing more efficient, effective, and organized. But there's always that one tool we turn to in almost every situation—the one that makes our job easier or ensures we deliver the highest quality product.Whether it's an automation framework, a bug-tracking system, or a handy utility for test data management, what’s the one tool you absolutely can’t live without? Why is it so essential in your workflow? Share your go-to tool and how it’s helped you achieve better testing results.

Every QA professional has faced a bug that stands out—a tricky issue that required extra effort, creativity, or collaboration to resolve. Whether it was an elusive edge case, a critical blocker, or a system behavior that just didn’t add up, these experiences often teach us valuable lessons.Share the story behind the toughest bug you've encountered! What made it so challenging? How did you eventually figure it out, and what approach or tool helped you resolve it? This is a great opportunity to learn from each other’s experiences and uncover creative problem-solving techniques in QA.

Hi everyone! 👋What do you think about being called a 'Software Developer in Testing' (SDIT)? Does that title describe your job accurately, or would you prefer something else? 

Test-Driven Development (TDD) and Behavior-Driven Development (BDD) are two popular approaches to software development that prioritize testing and quality assurance. TDD focuses on writing tests before writing codeBDD focuses on defining the behavior of the system before writing code. Which one do you use? Do you use either, or a third one?

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

Hi Team,Can you please help me how i can automate any desktop or window-based application using TSOCA commander ? 

I’m pushing myself to make more of an effort to keep up with the latest news and best practices related to software testing. Where do y’all go to get your news? (I already do Twitter lol and please don’t say Apple News- NO!)

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? 

When faced with testing large, complex tickets at the last minute, it’s easy to miss important edge cases, which can lead to undetected issues. How do you make sure you thoroughly cover all possible scenarios, including edge cases, given the limited time? What strategies or tools do you use to track these cases, and how do you prioritize the most critical ones to ensure comprehensive testing under pressure?

I’m currently facing significant challenges with our e-delivery process that seem to impact the reliability and speed of our software releases. Despite thorough testing and successful build completions, we often encounter issues during deployment that lead to delays and frustration among team members and stakeholders.Here are some specific challenges we're experiencing:Inconsistent Build Artifacts: Different environments sometimes deploy artifacts that don't match what was tested, causing discrepancies in behavior. Communication Gaps: There seems to be a disconnect between the development and QA teams regarding the status and readiness of builds for delivery. Deployment Failures: We often see unexpected failures during e-delivery that weren't caught during testing, which leads to rollbacks and increased downtime. Dependency Management: Handling external dependencies (like APIs and libraries) can be tricky, and changes in those can break our deployments unexpectedly.I would love to hear

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

I'm facing a unique challenge with automated testing of dynamic data in my test suite.We have a system where certain values, like user IDs, timestamps, or API response payloads, change with every execution. These values are unpredictable and can’t be hardcoded in our test scripts. I’ve tried using data-driven testing to handle these values, but the dynamic nature of the data is causing our tests to either fail or pass inconsistently.Here are the key challenges I’m dealing with:Handling unpredictable values (like timestamps) in assertions. Maintaining consistency across multiple test runs when the expected data is generated dynamically at runtime. Comparing API responses that contain dynamically generated values without false positives or negatives.Has anyone dealt with similar issues in their testing framework? What strategies or tools would you recommend to manage dynamic data and ensure stable test results?

What conferences are you attending this Year?Tell the community so that we may see each other there.