Release v0.2.2 (#49)

* Use watchdog timeout to catalog properties
([#48](#48)). This pull
request introduces a new `RemoveAfter` property for catalogs, which
allows for marking them for skipping by the watchdog. This change
addresses the current implementation gap, which does not explicitly
indicate when catalogs are being used. The new property will specify the
time from which objects can be purged. A corresponding fixture
`watchdog_remove_after` has been added to the list of available
fixtures, and the `make_catalog` fixture has been updated to include
this new property. Additionally, a timeout mechanism for catalogs has
been implemented, which improves the system's efficiency and safety by
marking catalogs as in use. A test for the `make_catalog` function has
been included to ensure that the `RemoveAfter` entry is correctly added
to the catalog properties. However, the specific call parameters for the
`catalogs.create` method cannot be accurately determined in the test.
* use tags instead of name suffix for queries
([#47](#47)). This
release introduces updates to the testing library for Databricks,
enhancing the naming conventions for queries to improve readability and
comprehension. The previous implementation used name suffixes, which
have been replaced with watchdog query tags. The `watchdog_purge_suffix`
fixture has been renamed to `watchdog_remove_after`, and the new
`make_query` fixture has been added to the documentation. In addition,
the `make_query` and `create` functions now accept an optional `tags`
argument, and the query name is generated with a unique identifier. If
`tags` are provided, the `RemoveAfter` tag is added. The
`original_query_tag` is no longer hardcoded in the `create` function and
has been removed. These changes improve the overall user experience and
maintainability of the project.

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Version changelog
 
+## 0.2.2
+
+* Use watchdog timeout to catalog properties ([#48](https://github.com/databrickslabs/pytester/issues/48)). This pull request introduces a new `RemoveAfter` property for catalogs, which allows for marking them for skipping by the watchdog. This change addresses the current implementation gap, which does not explicitly indicate when catalogs are being used. The new property will specify the time from which objects can be purged. A corresponding fixture `watchdog_remove_after` has been added to the list of available fixtures, and the `make_catalog` fixture has been updated to include this new property. Additionally, a timeout mechanism for catalogs has been implemented, which improves the system's efficiency and safety by marking catalogs as in use. A test for the `make_catalog` function has been included to ensure that the `RemoveAfter` entry is correctly added to the catalog properties. However, the specific call parameters for the `catalogs.create` method cannot be accurately determined in the test.
+* use tags instead of name suffix for queries ([#47](https://github.com/databrickslabs/pytester/issues/47)). This release introduces updates to the testing library for Databricks, enhancing the naming conventions for queries to improve readability and comprehension. The previous implementation used name suffixes, which have been replaced with watchdog query tags. The `watchdog_purge_suffix` fixture has been renamed to `watchdog_remove_after`, and the new `make_query` fixture has been added to the documentation. In addition, the `make_query` and `create` functions now accept an optional `tags` argument, and the query name is generated with a unique identifier. If `tags` are provided, the `RemoveAfter` tag is added. The `original_query_tag` is no longer hardcoded in the `create` function and has been removed. These changes improve the overall user experience and maintainability of the project.
+
+
 ## 0.2.1
 
 * Moved remaining UCX integration tests and fixtures ([#45](https://github.com/databrickslabs/pytester/issues/45)). In this release, we have made significant changes to the UCX integration tests and fixtures, as indicated by multiple commit messages. Firstly, we have moved remaining UCX integration tests and fixtures, introducing a new PyTest fixture called `Installation` in the README.md file, providing instructions on how to add `databricks-labs-pytester` as a test-time dependency when using `hatch` as the build system. Additionally, we have added the `make_feature_table` fixture, which creates a Databricks feature table and cleans it up after the test, taking optional parameters for customization. We have also modified the `mypy` configuration in the `pyproject.toml` file to allow untyped imports during the type-checking process. In the `compute.py` file, we have updated the `make_job` fixture to return a function that creates a `databricks.sdk.service.jobs.Job` instance, and modified the `create` function to return the `databricks.sdk.service.jobs.Job` instance directly. We have also added a new fixture called `make_feature_table` in the plugin file, which simulates the lifecycle of a feature table in the machine learning service, with functions to generate a unique name and create/remove the feature table. In the `test_catalog.py` file, we have made changes to clean up the file and ensure proper logging of test events and errors. Overall, these changes aim to refactor, expand functionality, and improve user-friendliness for the adopters of the project, ensuring proper logging and debugging capabilities.

src/databricks/labs/pytester/__about__.py

@@ -1 +1 @@
-__version__ = "0.2.1"
+__version__ = "0.2.2"