<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Databricks regression test suite in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/104751#M41866</link>
    <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Regression testing after code changes can be automated easily. Once you’ve created test cases with Pytest or Great Expectations, you can set up a CI/CD pipeline using tools like Jenkins or GitHub Actions. For a non-prod setup, Docker is great for replicating the environment consistently.&lt;/P&gt;&lt;P&gt;If you're looking for more details, this blog might help: &lt;A href="https://labdeck.com/regression-testing-and-stat-studio-regression-testing-software/" target="_new" rel="noopener"&gt;&lt;SPAN&gt;Regression&lt;/SPAN&gt;&lt;SPAN&gt; Testing&lt;/SPAN&gt;&lt;SPAN&gt; and&lt;/SPAN&gt;&lt;SPAN&gt; Stat&lt;/SPAN&gt;&lt;SPAN&gt; Studio&lt;/SPAN&gt;&lt;/A&gt;. It explains tools and processes for smoother regression testing.&lt;/P&gt;&lt;P&gt;Hope this helps! Let me know if you have any specific questions.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 08 Jan 2025 17:26:06 GMT</pubDate>
    <dc:creator>grkseo7</dc:creator>
    <dc:date>2025-01-08T17:26:06Z</dc:date>
    <item>
      <title>Databricks regression test suite</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/4647#M1320</link>
      <description>&lt;P&gt;Hi, I am new to Databricks and setting up the non-prod environment. I am wanted to know, IS there any way by which I can run a regression suite so that existing setup should not break in case of any feature addition and also how can I make available prod datas in non-prod? Shallow copy?&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2023 11:10:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/4647#M1320</guid>
      <dc:creator>_deepak_</dc:creator>
      <dc:date>2023-05-09T11:10:25Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks regression test suite</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/4648#M1321</link>
      <description>&lt;P&gt;@deepak prasad​&amp;nbsp;:&lt;/P&gt;&lt;P&gt;Yes, you can run regression tests to ensure that your changes do not break existing functionality. Databricks supports a number of testing frameworks like PyTest, which can be used to automate regression testing. You can write test cases that cover different scenarios and use cases of your application and run them automatically after each code change.&lt;/P&gt;&lt;P&gt;To make production data available in non-production, you can use a number of techniques such as database replication, backup and restore, or data cloning. One approach could be to take regular backups of your production databases and restore them in non-production environments. You can also use data masking and obfuscation techniques to protect sensitive data in non-production environments. Another approach is to use a data virtualization platform that can create a virtualized copy of the production data on demand, without actually copying the data. This can help reduce the storage requirements in non-production environments.&lt;/P&gt;</description>
      <pubDate>Sat, 13 May 2023 15:38:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/4648#M1321</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-13T15:38:50Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks regression test suite</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/4649#M1322</link>
      <description>&lt;P&gt;Hi @Suteja Kanuri​&amp;nbsp;, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can create the testcases using any framework may be pytest or great_expectation, But how to run regression after any code changes. Is there any blog or documentation for the non-prod setup or regression running? Can you please share some references for this? &lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2023 04:58:45 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/4649#M1322</guid>
      <dc:creator>_deepak_</dc:creator>
      <dc:date>2023-05-15T04:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks regression test suite</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/4650#M1323</link>
      <description>&lt;P&gt;@deepak prasad​&amp;nbsp;:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here you go&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;A href="https://docs.greatexpectations.io/docs/" alt="https://docs.greatexpectations.io/docs/" target="_blank"&gt;https://docs.greatexpectations.io/docs/&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;You can search here - &lt;A href="https://www.databricks.com/blog?_gl=1*9iwzny*_gcl_aw*R0NMLjE2ODE5ODAxNTUuQ2owS0NRand4WU9pQmhDOUFSSXNBTmlFSWZhOEMwRGZPMmxKZ0FmWTl5UEJ6VHBFeFdmX2pMbHhVQ0stNkdkR2NyYjVPUkZqa08tb0hjUWFBdmI5RUFMd193Y0I.*_gcl_au*MTU3ODE0NTUxMC4xNjgxOTAxNzUy*_ga*MTA0MDgzNDQyMy4xNjgwNzc3Nzg3*_ga_PQSEQ3RZQC*MTY4NjMwMjIzNS4xODUuMS4xNjg2MzAzMjIzLjYwLjAuMA..&amp;amp;_ga=2.12253808.553552737.1685951115-1040834423.1680777787" alt="https://www.databricks.com/blog?_gl=1*9iwzny*_gcl_aw*R0NMLjE2ODE5ODAxNTUuQ2owS0NRand4WU9pQmhDOUFSSXNBTmlFSWZhOEMwRGZPMmxKZ0FmWTl5UEJ6VHBFeFdmX2pMbHhVQ0stNkdkR2NyYjVPUkZqa08tb0hjUWFBdmI5RUFMd193Y0I.*_gcl_au*MTU3ODE0NTUxMC4xNjgxOTAxNzUy*_ga*MTA0MDgzNDQyMy4xNjgwNzc3Nzg3*_ga_PQSEQ3RZQC*MTY4NjMwMjIzNS4xODUuMS4xNjg2MzAzMjIzLjYwLjAuMA..&amp;amp;_ga=2.12253808.553552737.1685951115-1040834423.1680777787" target="_blank"&gt;https://www.databricks.com/blog&lt;/A&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 09:38:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/4650#M1323</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-06-09T09:38:17Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks regression test suite</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/104751#M41866</link>
      <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Regression testing after code changes can be automated easily. Once you’ve created test cases with Pytest or Great Expectations, you can set up a CI/CD pipeline using tools like Jenkins or GitHub Actions. For a non-prod setup, Docker is great for replicating the environment consistently.&lt;/P&gt;&lt;P&gt;If you're looking for more details, this blog might help: &lt;A href="https://labdeck.com/regression-testing-and-stat-studio-regression-testing-software/" target="_new" rel="noopener"&gt;&lt;SPAN&gt;Regression&lt;/SPAN&gt;&lt;SPAN&gt; Testing&lt;/SPAN&gt;&lt;SPAN&gt; and&lt;/SPAN&gt;&lt;SPAN&gt; Stat&lt;/SPAN&gt;&lt;SPAN&gt; Studio&lt;/SPAN&gt;&lt;/A&gt;. It explains tools and processes for smoother regression testing.&lt;/P&gt;&lt;P&gt;Hope this helps! Let me know if you have any specific questions.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 08 Jan 2025 17:26:06 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-regression-test-suite/m-p/104751#M41866</guid>
      <dc:creator>grkseo7</dc:creator>
      <dc:date>2025-01-08T17:26:06Z</dc:date>
    </item>
  </channel>
</rss>

