Forum Discussion

rameshberkhout's avatar
rameshberkhout
New Contributor
6 months ago

Data Sink step in ReadyAPI (v3.49.0) retains data from previous runs and does not append

Previously We had a build that created an excel file and filled it with data. Now, the last Data SInk step does not append. I made a new project to test this. Step 1: Delete the file Step 2: Data ...
Function Tests
Test Results
richie's avatar
richie
Community Hero
6 months ago
Hey rameshberkhout,

When you say "before" and "previously" it worked differently, can you be a bit more specific as to what has changed during the intervening time?

Just to be clear, i'm not criticising, but several people have recently posted about what appears to be regressions introduced in v3.49 of ReadyAPI!, so i'm curious whether this is the case for you also.

If it is due to you upgrading your ReadyAPI! instance, Smartbear will need to be made aware of the regression, would you please raise a ticket --> https://support.smartbear.com/readyapi/message/

If the changes aren't due to changing ReadyAPI! version, can you clarify what has changed?

Cheers,

Rich
  • rameshberkhout's avatar
    rameshberkhout
    New Contributor
    6 months ago

    Rich,

     

    There were no changes to our  solution. Before upgrading to version 3.49, the project worked as expected. Now, it seems that either data is retained/stored in a TestCase Run (without changing any preferences or saving the data in any other way), which makes the Data Sink not work as expected (it does not append to file, overwrites the top row and also keeps adding more data with each run, while the first step should start with a clean slate). I already made a ticket, I hope to hear from SmartBear soon. This only happens when you run the TestCase (all steps in order from TestCase/TestSuite level), if you execute the steps seperately, it works like expected.

    • richie's avatar
      richie
      Community Hero
      6 months ago

      Hey rameshberkhout 

       

      So it's the new version that's the cause of the issue?  Did you upgrade to v3.49 because you needed v3.49 (perhaps you needed v3.49 because it included a code change you needed)?

       

      If there was no specific reason you upgraded to v3.49 other than you were running an older version and felt it was time to upgrade - could you downgrade back to the previous version for now until the issue impacting your testing is resolved? 

       

      Cheers,

       

      Rich