Discussions

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?

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 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

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?

Functionality failures in cases where no apparent code or infrastructure changes were made can be tricky to diagnose. Common root causes include environmental drift, where configurations or dependencies in the environment subtly change over time, leading to inconsistencies. Data-related issues, such as corrupted or outdated data, can also break functionality without any direct code changes. External factors like third-party APIs, services, or network-related issues may alter their behavior, impacting the application. Timing or concurrency issues can surface unexpectedly, especially in high-load scenarios. Finally, hidden bugs or edge cases may not have been caught during testing but reveal themselves later due to changing conditions.

Automated testing is crucial for fast feedback, but there’s often a trade-off between speed and thorough test coverage. What strategies do you use to ensure that your automated tests deliver rapid feedback without sacrificing coverage? Share your approaches for balancing test execution time with maintaining comprehensive testing, especially in continuous integration environments.

AI and machine learning are transforming many areas of software development, including test automation. Has anyone here integrated AI or ML into their test automation process? How has it affected the effectiveness, speed, and accuracy of your tests? Share your experiences, including any benefits or challenges you've encountered along the way.

In fast-paced DevOps environments, frequent code changes can make thorough testing a challenge. What’s your approach to ensuring high-quality testing without slowing down the development pipeline? How do you balance speed with accuracy, and what strategies or tools do you use to maintain test coverage and effectiveness in such a dynamic setting?

Flaky tests, which produce inconsistent results, can disrupt the development process and reduce confidence in test automation. What is your approach to identifying and managing flaky tests? Do you have any proven strategies or best practices for making them more stable and reliable in your test suite? We'd love to hear your methods for addressing this common challenge.

Hi ShiftSync Community,I have one question related to the webinar for you:Name 3 AI features that software testers can already use today.One of you has the chance to win some nice swag provided by ShiftSync.  Best,Daniel

Exploratory testing is crucial for uncovering unexpected issues, but it can be hard to plan in a time-boxed environment like Agile. How do teams incorporate it effectively?

In a rapidly evolving tech landscape, automation strategies and tools must be adaptable to stay relevant. This question seeks to explore how QA professionals future-proof their automation efforts against emerging technologies and shifts in testing methodologies. It addresses the importance of building flexible frameworks, choosing scalable tools, and staying informed about industry trends. What proactive steps do you take to ensure that your automation processes and tools can seamlessly adapt to future changes, and how do you integrate forward-thinking practices into your overall testing strategy?

Where does return render( <UserProvider> etc go in a test.js jest file? Here is the UserContext.js mock data file```import React, { useState } from 'react';// Create a mock UserContext with default userId as nullconst UserContext = React.createContext({  userId: null,  setUserId: () => {}, // Mock function for tests});// Mock UserProvider to be used in testsconst UserProvider = ({ value, children }) => {  const [userId, setUserId] = useState(value?.userId || null);  // Always use the provided setUserId if available, otherwise use the internal state  const contextValue = {    userId,    setUserId: value?.setUserId || setUserId,  };  return (    <UserContext.Provider value={contextValue}>      {children}    </UserContext.Provider>  );};export { UserContext, UserProvider };``` So does the below go above or in the describes if above do I pass the renderComponentWithUserContext to the describe condition as a parameter and each test that uses it? Apologies for the tro

Hi I have taken up AS1 Assessment 3-time buts not cleared  it is saying that need to wait for 2  to 3 months can you please help me that I am want to take up the test now to Enable to take up the test to whom i have to contact 

Hi Team,I am unable to access the product forum getting access error. Kindly help me to resolve the same Thanks,Harish N

Hi Community,I have RTB libaries in a deeper structure. The RTBs have business parameters.When I pass down business parameters,to deeper levels the parameters arrive as NULL in some test plans.D you know whats amiss here?For example:I have a parameter “Role” and want to pass it on to a sub-RTB like this:Scenario A:I pass the parameter down as {PL[Role]}Issue: The parameter arrives as a NULL value Scenario B:I pass the parameter down as {PL[Role]}. On level 2 (RTB 2) I copy the parameter to a buffer variable and pass on the value as {B[Role]}This works.Regards    Florian

I was just wondering, how do you prepare for a CFP at a conference? Based on the size of a conference I am usually putting together 2 to 4 proposals, but sometimes I am uncertain on how to phrase an elevator pitch. Any tips, you could share? 🙂

 I would like to implement access restrictions for certain test cycles and defects (bugs) within  qTest Manager. The goal is to limit access to specific test cycles and bugs to designated users, ensuring that each team member only has visibility of relevant information pertaining to their responsibilities. Could you please provide guidance on how to configure user permissions to achieve this level of access control effectively?Thank you 

Suddenly getting this error, any idea what has happened× Failed to initiate Chrome DriverError: Command failed: npm i chromedriver --detect_chromedriver_version  --no-save --no-prune --prefer-offline --no-audit --progress=falsenpm ERR! Invalid comparator: npm:isolated-vm@4.7.2 If i run the commandnpm i chromedriver --detect_chromedriver_version  --no-save --no-prune --prefer-offline --no-audit --progress=falsein CMD it is OK.

Hello , I’m interested in automating the generation of reports immediately following the completion of a test cycle automated execution. Specifically, I would like to automatically generate a report as soon as a test cycle is concluded and have it sent to designated users via email. Could you please advise  on how to configure this automated reporting functionality within qTest?Thank you 

I work in an organisation where some domains we think are doing OK. They are CD, YBIYRI, product teams delivering to production in some instances multiple times a day.In other domains they have not really even started on that journey. They are projects not products and follow a more siloed, phased, document heavy way of working.We have a mandate to help these other domains on their journey to CD.We do however want to be sure we are safe to scale. We traditionally have only used trailing metrics (e.g. DORA) which tell us how we DID. We have a gut feel that as we scale we may need metrics that are more leading (e.g. measuring engineering signals like code complexity or, dare I say it, code coverage) which tell us how we ARE DOING.We think we are aware of the usual gotchas in measurement and so our measurement principles include things like: don't measure individuals but teams, don't set arbitrary targets, don't use metrics to judge across teams but to help each team have better evidence-

What is the recommended ratio of developers to testers in a software development team?A) 1:1 B) 3:1 C) 5:1 D) 7:1 E) A LOT :1

I work in an organisation where some domains we think are doing OK. They are CD, YBIYRI, product teams delivering to production in some instances multiple times a day.In other domains they have not really even started on that journey. They are projects not products and follow a more siloed, phased, document heavy way of working.We have a mandate to help these other domains on their journey to CD.We do however want to be sure we are safe to scale. We traditionally have only used trailing metrics (e.g. DORA) which tell us how we DID. We have a gut feel that as we scale we may need metrics that are more leading (e.g. measuring engineering signals like code complexity or, dare I say it, code coverage) which tell us how we ARE DOING.We think we are aware of the usual gotchas in measurement and so our measurement principles include things like: don't measure individuals but teams, don't set arbitrary targets, don't use metrics to judge across teams but to help each team have better evidence-