Conversation
- Introduced a new Database Profiler to track and log database operations for MongoDB, MySQL, PostgreSQL, SQLite, and Redis. - Updated `qase.config.json` to include a `profilers` array for enabling the database profiler. - Added comprehensive tests for each database type to ensure functionality. - Updated changelog to reflect the new version and changes. This release enhances the ability to profile database operations, providing detailed insights into query performance and execution metrics.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
qase.config.jsonto include aprofilersarray for enabling the database profiler.This release enhances the ability to profile database operations, providing detailed insights into query performance and execution metrics.
Note
Adds a database profiler that captures queries for SQLite, PostgreSQL, MySQL, MongoDB, and Redis, integrates it with reporters, extends step modeling/formatting, and updates docs, examples, tests, and versioning.
DatabaseProfilerandDatabaseProfilerSingletoninqase-python-commons/src/qase/commons/profilers/db.pywith hooks forsqlalchemy,psycopg2,pymysql,sqlite3,pymongo, andredis.QaseCoreReporter.setup_profilers()to enable/disable with"profilers": ["db"].StepDbQueryDatato includedatabase_type,execution_time,rows_affected, andconnection_infoinmodels/step.py.StepType.DB_QUERYhandling inApiV2Client._prepare_step()to format action and input data for DB steps.docs/DATABASE_PROFILERS.mddescribing configuration, supported libraries, collected data, and examples.examples/pytest/qase.config.jsonto include"profilers": ["db"].examples/pytest/requirements.txt.SQLite,PostgreSQL,MySQL,MongoDB, andRedisprofilers underexamples/pytest/tests/.qase-python-commonsto4.1.3and add changelog entry noting DB profiler support.Written by Cursor Bugbot for commit bcc2b94. This will update automatically on new commits. Configure here.