| Name | rdbunit JSON |
| Version |
1.1.4
JSON |
| download |
| home_page | |
| Summary | RDBUnit is a unit testing framework for relational database queries. |
| upload_time | 2024-01-18 12:15:59 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | >=3.7 |
| license | Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. |
| keywords |
postgresql
sql
sqlite
mysql
unit testing
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# RDBUnit: Unit testing for relational database queries
[](https://github.com/dspinellis/rdbunit/actions/workflows/ci.yml)
**RDBUnit** is a unit testing framework for relational database queries.
It allows you to express in a simple way the setup prior to a query,
the query, and the expected results.
RDBUnit can test `SELECT` queries as well as queries that are used
for creating tables and views.
All types of queries can be either embedded into the test script, or
they can be included from an external file.
The tables for the input and the expected results can be created with
minimal ceremony: RDBUnit will automatically infer the types of the
tables' fields.
For complex relational OLAP queries *RDBUnit* can be combined particularly
effectively with the [simple-rolap](https://github.com/dspinellis/simple-rolap)
relational online analytical processing framework.
You can find a complete tutorial on using *RDBUnit* with *simple-rolap*
for mining Git repositories in a
[technical briefing](https://doi.org/10.5281/zenodo.7513793)
presented at the 2017 International Conference on Software Engineering.
You can cite this work as follows.
* Diomidis Spinellis. Unit Tests for SQL. _IEEE Software_, vol. 41, no. 1, pp. 31–34, Jan.-Feb. 2024. doi: [10.1109/MS.2023.3328788](https://doi.org/10.1109/MS.2023.3328788).
## Installation
### Using Pip
```sh
pip install rdbunit
```
### From source
* Clone this repository
```
git clone --depth=1 https://github.com/dspinellis/rdbunit.git
cd rdbunit
pipenv shell
pip install .
```
## Test specification
For every SQL query you want to test, create an *RDBUnit* file that
specifies the query's input, execution, and expected result.
### Simple example
The following example illustrates this concept.
```
BEGIN SETUP
sales:
month revenue
March 130
April 50
END
BEGIN SELECT
SELECT MAX(revenue) as max_revenue FROM sales;
END
BEGIN RESULT
max_revenue
130
END
```
### Input file details
The input and output and output are specified as table contents.
The input starts with a line containing the words `BEGIN SETUP`,
while the results start with a line containing the words
`BEGIN RESULTS`.
The input and output are specified by first giving a table's name,
followed by a colon.
The name may be prefixed by the name of a database where the table
is to reside, followed by a dot.
The next row contains the table's fields, separated by spaces.
Then comes the table's data, which is terminated by a blank line,
or by the word `END`.
More than one table can be specified in the setup.
In the results the table name is not specified, if the tested
query is a selection statement, rather than a table or view creation.
The setup-query-results sequence can be specified multiple times within
a test file.
### Setup example
```
BEGIN SETUP
contacts:
name registered value reg_date
John true 12 '2015-03-02'
Mary false 10 '2012-03-02'
END
```
### Results example (named table)
Named table results are used with `CREATE` queries.
```
BEGIN RESULT
leadership.nl_commits_leader_comments:
project_id n
1 3
END
```
### Results example (unnamed set)
Unnamed set results are used with `SELECT` queries.
```
BEGIN RESULT
name registered value reg_date a
John True 12 '2015-03-02' Null
END
```
The query to test is either specified inline with a `BEGIN SELECT` (for
selection queries) or `BEGIN CREATE` (for creation queries) statement,
or by including a file through the corresponding `INCLUDE SELECT` or
`INCLUDE CREATE` statement.
### Inline example
```
BEGIN SELECT
SELECT *, NULL AS a FROM contacts WHERE registered;
END
```
### External query example
```
INCLUDE CREATE nl_commits_leader_comments.sql
```
## Unit testing
To run the tests run *RDBUnit* piping its output to one of the supported
relational database systems (current *MySQL*, *PostgreSQL*, and *sqLite*).
A number of command-line flags allow you to tailor the operation of
*RDBUnit*.
When running, *RDBUnit* will report on its output something like
`ok 1 - recent_commit_projects.rdbu: test_stratsel.recent_commit_projects`
for each succeeding test case and
`not ok 1 - project_stars.rdbu: test_stratsel.project_stars` for each failing
test case.
A final line will list the number of succeeding and failing test cases.
By default *RDBUnit* creates and operates on temporary databases,
whose name is prefixed with the word `test_`.
By specifying the `--results` option (or the equivalent `-r` short option)
you can direct _rdbunit_ to display the table generated for each test.
This is useful for debugging test failures or for generating reference data
(after suitable manual verification).
### Execution example (SQLite)
```sh
$ rdbunit --database=sqlite recent_commit_projects.rdbu | sqlite3
ok 1 - recent_commit_projects.rdbu: test_stratsel.recent_commit_projects
```
### Execution example (MySQL)
```sh
$ rdbunit commits_comments.rdbu | mysql -u root -p -N
Enter password:
ok 1 - commits_comments.rdbu: test_leadership.nl_commits_leader_comments
ok 2 - commits_comments.rdbu: test_leadership.leader_commits_nl_comments
ok 3 - commits_comments.rdbu: test_leadership.commits_with_comments
1..3
```
### Execution example (PostgreSQL)
```sh
$ rdbunit --database=postgresql commits_comments.rdbu | psql -U ght -h 127.0.0.1 -t -q ghtorrent
ok 1 - commits_comments.rdbu: test_leadership.nl_commits_leader_comments
ok 2 - commits_comments.rdbu: test_leadership.leader_commits_nl_comments
ok 3 - commits_comments.rdbu: test_leadership.commits_with_comments
1..3
```
## Development
Contributions via GitHub pull requests are welcomed.
Each contribution passes through continuous integration,
which verifies the code's style (_pycodestyle_) and checks for errors
(_pylint_).
It also tests the input and output of _RDBunit_ and its operation on the
three supported relational database systems.
On a local host, after creating a virtual environment (`pipenv`),
entering it (`pipenv shell`), and
installing the required development dependencies (`pipenv install --dev`),
you can run the following commands.
* ``pycodestyle src/rdbunit/__main__.py`
* `pylint src/rdbunit/__main__.py`
* `tests/test-parts.sh`
* `tests/test-sqlite.sh`
Raw data
{
"_id": null,
"home_page": "",
"name": "rdbunit",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.7",
"maintainer_email": "",
"keywords": "PostgreSQL,SQL,SQLite,mySQL,unit testing",
"author": "",
"author_email": "Diomidis Spinellis <dds@aueb.gr>",
"download_url": "https://files.pythonhosted.org/packages/6c/5d/438c1b5d4f1dd4e4b2c256d1e32a2c9224b642d9ef79f65adeb4571ac7b5/rdbunit-1.1.4.tar.gz",
"platform": null,
"description": "# RDBUnit: Unit testing for relational database queries\n\n[](https://github.com/dspinellis/rdbunit/actions/workflows/ci.yml)\n\n\n**RDBUnit** is a unit testing framework for relational database queries.\nIt allows you to express in a simple way the setup prior to a query,\nthe query, and the expected results.\nRDBUnit can test `SELECT` queries as well as queries that are used\nfor creating tables and views.\nAll types of queries can be either embedded into the test script, or\nthey can be included from an external file.\nThe tables for the input and the expected results can be created with\nminimal ceremony: RDBUnit will automatically infer the types of the\ntables' fields.\n\nFor complex relational OLAP queries *RDBUnit* can be combined particularly\neffectively with the [simple-rolap](https://github.com/dspinellis/simple-rolap)\nrelational online analytical processing framework.\nYou can find a complete tutorial on using *RDBUnit* with *simple-rolap*\nfor mining Git repositories in a\n[technical briefing](https://doi.org/10.5281/zenodo.7513793)\npresented at the 2017 International Conference on Software Engineering.\n\nYou can cite this work as follows.\n\n* Diomidis Spinellis. Unit Tests for SQL. _IEEE Software_, vol. 41, no. 1, pp. 31\u201334, Jan.-Feb. 2024. doi: [10.1109/MS.2023.3328788](https://doi.org/10.1109/MS.2023.3328788).\n\n## Installation\n\n### Using Pip\n```sh\npip install rdbunit\n```\n\n### From source\n* Clone this repository\n```\ngit clone --depth=1 https://github.com/dspinellis/rdbunit.git\ncd rdbunit\npipenv shell\npip install .\n```\n\n## Test specification\nFor every SQL query you want to test, create an *RDBUnit* file that\nspecifies the query's input, execution, and expected result.\n\n### Simple example\nThe following example illustrates this concept.\n```\nBEGIN SETUP\nsales:\nmonth revenue\nMarch 130\nApril 50\nEND\n\nBEGIN SELECT\nSELECT MAX(revenue) as max_revenue FROM sales;\nEND\n\nBEGIN RESULT\nmax_revenue\n130\nEND\n```\n\n### Input file details\nThe input and output and output are specified as table contents.\nThe input starts with a line containing the words `BEGIN SETUP`,\nwhile the results start with a line containing the words\n`BEGIN RESULTS`.\nThe input and output are specified by first giving a table's name,\nfollowed by a colon.\nThe name may be prefixed by the name of a database where the table\nis to reside, followed by a dot.\nThe next row contains the table's fields, separated by spaces.\nThen comes the table's data, which is terminated by a blank line,\nor by the word `END`.\nMore than one table can be specified in the setup.\nIn the results the table name is not specified, if the tested\nquery is a selection statement, rather than a table or view creation.\nThe setup-query-results sequence can be specified multiple times within\na test file.\n\n### Setup example\n```\nBEGIN SETUP\ncontacts:\nname registered value reg_date\nJohn true 12 '2015-03-02'\nMary false 10 '2012-03-02'\nEND\n```\n\n### Results example (named table)\nNamed table results are used with `CREATE` queries.\n```\nBEGIN RESULT\nleadership.nl_commits_leader_comments:\nproject_id n\n1 3\nEND\n```\n\n### Results example (unnamed set)\nUnnamed set results are used with `SELECT` queries.\n```\nBEGIN RESULT\nname registered value reg_date a\nJohn True 12 '2015-03-02' Null\nEND\n```\n\nThe query to test is either specified inline with a `BEGIN SELECT` (for\nselection queries) or `BEGIN CREATE` (for creation queries) statement,\nor by including a file through the corresponding `INCLUDE SELECT` or\n`INCLUDE CREATE` statement.\n\n### Inline example\n```\nBEGIN SELECT\nSELECT *, NULL AS a FROM contacts WHERE registered;\nEND\n```\n\n### External query example\n```\nINCLUDE CREATE nl_commits_leader_comments.sql\n```\n\n## Unit testing\nTo run the tests run *RDBUnit* piping its output to one of the supported\nrelational database systems (current *MySQL*, *PostgreSQL*, and *sqLite*).\nA number of command-line flags allow you to tailor the operation of\n*RDBUnit*.\nWhen running, *RDBUnit* will report on its output something like\n`ok 1 - recent_commit_projects.rdbu: test_stratsel.recent_commit_projects`\nfor each succeeding test case and\n`not ok 1 - project_stars.rdbu: test_stratsel.project_stars` for each failing\ntest case.\nA final line will list the number of succeeding and failing test cases.\nBy default *RDBUnit* creates and operates on temporary databases,\nwhose name is prefixed with the word `test_`.\n\nBy specifying the `--results` option (or the equivalent `-r` short option)\nyou can direct _rdbunit_ to display the table generated for each test.\nThis is useful for debugging test failures or for generating reference data\n(after suitable manual verification).\n\n### Execution example (SQLite)\n```sh\n$ rdbunit --database=sqlite recent_commit_projects.rdbu | sqlite3\nok 1 - recent_commit_projects.rdbu: test_stratsel.recent_commit_projects\n```\n\n### Execution example (MySQL)\n```sh\n$ rdbunit commits_comments.rdbu | mysql -u root -p -N\nEnter password:\nok 1 - commits_comments.rdbu: test_leadership.nl_commits_leader_comments\nok 2 - commits_comments.rdbu: test_leadership.leader_commits_nl_comments\nok 3 - commits_comments.rdbu: test_leadership.commits_with_comments\n1..3\n```\n\n### Execution example (PostgreSQL)\n```sh\n$ rdbunit --database=postgresql commits_comments.rdbu | psql -U ght -h 127.0.0.1 -t -q ghtorrent\n ok 1 - commits_comments.rdbu: test_leadership.nl_commits_leader_comments\n\n ok 2 - commits_comments.rdbu: test_leadership.leader_commits_nl_comments\n\n ok 3 - commits_comments.rdbu: test_leadership.commits_with_comments\n\n 1..3\n```\n\n## Development\n\nContributions via GitHub pull requests are welcomed.\nEach contribution passes through continuous integration,\nwhich verifies the code's style (_pycodestyle_) and checks for errors\n(_pylint_).\nIt also tests the input and output of _RDBunit_ and its operation on the\nthree supported relational database systems.\nOn a local host, after creating a virtual environment (`pipenv`),\nentering it (`pipenv shell`), and\ninstalling the required development dependencies (`pipenv install --dev`),\nyou can run the following commands.\n\n* ``pycodestyle src/rdbunit/__main__.py`\n* `pylint src/rdbunit/__main__.py`\n* `tests/test-parts.sh`\n* `tests/test-sqlite.sh`\n",
"bugtrack_url": null,
"license": " Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. \"License\" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. \"Licensor\" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. \"Legal Entity\" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, \"control\" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. \"You\" (or \"Your\") shall mean an individual or Legal Entity exercising permissions granted by this License. \"Source\" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. \"Object\" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. \"Work\" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). \"Derivative Works\" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. \"Contribution\" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, \"submitted\" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as \"Not a Contribution.\" \"Contributor\" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a \"NOTICE\" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets \"[]\" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same \"printed page\" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.",
"summary": "RDBUnit is a unit testing framework for relational database queries.",
"version": "1.1.4",
"project_urls": {
"Bug Tracker": "https://github.com/dspinellis/rdbunit/issues",
"Documentation": "https://github.com/dspinellis/rdbunit",
"Homepage": "https://github.com/dspinellis/rdbunit",
"Repository": "https://github.com/dspinellis/rdbunit.git"
},
"split_keywords": [
"postgresql",
"sql",
"sqlite",
"mysql",
"unit testing"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "f195600753a37b9ad64783de89ff3ae76e492359e700e3ffa2d03b705530cb17",
"md5": "880b405e8aa304ac9519dbed578fe337",
"sha256": "df7c75671783d3ce57c12b1fdc256a0899dcb5720322d1f4284452a9ef97f443"
},
"downloads": -1,
"filename": "rdbunit-1.1.4-py3-none-any.whl",
"has_sig": false,
"md5_digest": "880b405e8aa304ac9519dbed578fe337",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.7",
"size": 16978,
"upload_time": "2024-01-18T12:15:57",
"upload_time_iso_8601": "2024-01-18T12:15:57.375755Z",
"url": "https://files.pythonhosted.org/packages/f1/95/600753a37b9ad64783de89ff3ae76e492359e700e3ffa2d03b705530cb17/rdbunit-1.1.4-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "6c5d438c1b5d4f1dd4e4b2c256d1e32a2c9224b642d9ef79f65adeb4571ac7b5",
"md5": "11a9072ef01e43a3c254b79f738bbd2b",
"sha256": "460fa7705633a647bce830c69f19767800e5ff854439bba7d451ee66da2c3cea"
},
"downloads": -1,
"filename": "rdbunit-1.1.4.tar.gz",
"has_sig": false,
"md5_digest": "11a9072ef01e43a3c254b79f738bbd2b",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.7",
"size": 16009,
"upload_time": "2024-01-18T12:15:59",
"upload_time_iso_8601": "2024-01-18T12:15:59.216448Z",
"url": "https://files.pythonhosted.org/packages/6c/5d/438c1b5d4f1dd4e4b2c256d1e32a2c9224b642d9ef79f65adeb4571ac7b5/rdbunit-1.1.4.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-01-18 12:15:59",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "dspinellis",
"github_project": "rdbunit",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "rdbunit"
}
