From 20a8959e500f52086fb3ba1d1496549c11f9ac71 Mon Sep 17 00:00:00 2001 From: Serge Smertin Date: Mon, 4 Nov 2024 18:22:54 +0100 Subject: [PATCH] Release v0.4.0 * Added Volume Fixture ([#72](https://github.com/databrickslabs/pytester/issues/72)). This commit introduces a Managed Volume fixture, `make_volume`, to the Unity Catalog in the test suite, facilitating the creation and use of a random volume for testing purposes. The fixture, when called without arguments, generates a volume with a random name. Alternatively, specifying the `name` argument creates a volume with the given name, using the `MANAGED` volume type, and associating it with a randomly generated catalog and schema. This promotes test isolation and prevents unintended interference. Additionally, this PR resolves issue [#70](https://github.com/databrickslabs/pytester/issues/70) and includes unit and integration tests that have been manually verified to ensure the fixture's proper functioning. The commit also demonstrates a bug fix related to table retrieval in the `test_remove_after_property_table` test case. --- CHANGELOG.md | 5 +++++ src/databricks/labs/pytester/__about__.py | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e19593b..d68a6ed 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,10 @@ # Version changelog +## 0.4.0 + +* Added Volume Fixture ([#72](https://github.com/databrickslabs/pytester/issues/72)). This commit introduces a Managed Volume fixture, `make_volume`, to the Unity Catalog in the test suite, facilitating the creation and use of a random volume for testing purposes. The fixture, when called without arguments, generates a volume with a random name. Alternatively, specifying the `name` argument creates a volume with the given name, using the `MANAGED` volume type, and associating it with a randomly generated catalog and schema. This promotes test isolation and prevents unintended interference. Additionally, this PR resolves issue [#70](https://github.com/databrickslabs/pytester/issues/70) and includes unit and integration tests that have been manually verified to ensure the fixture's proper functioning. The commit also demonstrates a bug fix related to table retrieval in the `test_remove_after_property_table` test case. + + ## 0.3.1 * Updated databrickslabs/sandbox requirement to acceptance/v0.3.1 ([#64](https://github.com/databrickslabs/pytester/issues/64)). In this pull request, we are updating the requirement for the `databrickslabs/sandbox` package to version `acceptance/v0.3.1`. This update is necessary to resolve any conflicts and ensure compatibility with the latest version of the package. The update includes several bug fixes, dependency updates, and the addition of install instructions in the changelog. The package also includes new git-related libraries and modifications to the README to explain how to use the package with the `databricks labs sandbox` command. Additionally, there are dependency updates for `golang.org/x/crypto` in the `go-libs` and `runtime-packages` directories. Keeping dependencies up-to-date is important for taking advantage of new features and bug fixes, so it is recommended to merge this pull request and address any conflicts or issues that may arise. This update is generated by Dependabot, a tool used to keep dependencies up-to-date, and it will handle any conflicts as long as the pull request is not modified. The `databrickslabs/sandbox` package is used for building and testing the project. diff --git a/src/databricks/labs/pytester/__about__.py b/src/databricks/labs/pytester/__about__.py index 260c070..6a9beea 100644 --- a/src/databricks/labs/pytester/__about__.py +++ b/src/databricks/labs/pytester/__about__.py @@ -1 +1 @@ -__version__ = "0.3.1" +__version__ = "0.4.0"