8000 Merge pull request #1022 from utPLSQL/release/v3.1.9 · utPLSQL/utPLSQL@c8dae86 · GitHub
[go: up one dir, main page]
Skip to content

Commit c8dae86

Browse files
jgebaljgebal
authored
Merge pull request #1022 from utPLSQL/release/v3.1.9
Release/v3.1.9
2 parents df471a3 + e1b8ee6 commit c8dae86

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+1565
-515
lines changed

‎.gitattributes

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,3 +9,8 @@ tests export-ignore
99
development export-ignore
1010
node_modules export-ignore
1111
^docs/* linguist-documentation
12+
*.pkb linguist-language=PLSQL
13+
*.pks linguist-language=PLSQL
14+
*.sql linguist-language=PLSQL
15+
*.tpb linguist-language=PLSQL
16+
*.tps linguist-language=PLSQL

‎.travis.yml

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,11 @@ addons:
55
apt:
66
packages:
77
- unzip
8-
# Java9 Required for Sonar and SQLCL
9-
- oracle-java9-installer
10-
- oracle-java9-set-default
8+
# Java9+ Required for Sonar and SQLCL
9+
- openjdk-9-jre-headless
1110
sonarcloud:
1211
organization: utplsql
13-
token:
14-
secure: ${SONAR_TOKEN}
12+
token: ${SONAR_TOKEN}
1513

1614
services:
1715
- docker
@@ -47,7 +45,7 @@ env:
4745
#utPLSQL released version directory
4846
- UTPLSQL_DIR="utPLSQL_latest_release"
4947
- SELFTESTING_BRANCH=${TRAVIS_BRANCH}
50-
- UTPLSQL_CLI_VERSION="3.1.6"
48+
- UTPLSQL_CLI_VERSION="3.1.8"
5149
# Maven
5250
- MAVEN_HOME=/usr/local/maven
5351
- MAVEN_CFG=$HOME/.m2

‎VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
v3.1.8
1+
v3.1.9

‎docs/about/authors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
![version](https://img.shields.io/badge/version-v3.1.8.3188-blue.svg)
1+
![version](https://img.shields.io/badge/version-v3.1.9.3268-blue.svg)
22

33
### utPLSQL v3 Major Contributors
44

‎docs/about/license.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
![version](https://img.shields.io/badge/version-v3.1.8.3188-blue.svg)
1+
![version](https://img.shields.io/badge/version-v3.1.9.3268-blue.svg)
22

33
# Version Information
44

‎docs/about/project-details.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
![version](https://img.shields.io/badge/version-v3.1.8.3188-blue.svg)
1+
![version](https://img.shields.io/badge/version-v3.1.9.3268-blue.svg)
22

33
# utPLSQL Project Details
44

‎docs/about/support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
![version](https://img.shields.io/badge/version-v3.1.8.3188-blue.svg)
1+
![version](https://img.shields.io/badge/version-v3.1.9.3268-blue.svg)
22

33
# How to get support
44

‎docs/compare_version2_to_3.md

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
For version 3 has been a complete rewrite of the framework, the way it can be used is different to
2+
the previous versions, but also more in line with other modern unit-testing frameworks like JUnit and RSpec.
3+
4+
There is a [migration tool](https://github.com/utPLSQL/utPLSQL-v2-v3-migration) that can help you to migrate your existing utPLSQL v2 tests to the v3 capabilities.
5+
6+
# Feature comparison
7+
8+
| Feature | Version 2 | Version 3 |
9+
| -------------------------------------- | ---------------------- | ---------------------- |
10+
| Easy to install | Yes | Yes |
11+
| Documentation | Yes | Yes |
12+
| License | GPL v2 | Apache 2.0 |
13+
| **Tests Creation** | | |
14+
| Declarative test configuration | No | Yes - Annotations<sup>1</sup>|
15+
| Tests as Packages | Yes | Yes |
16+
| Multiple Tests in a single Package | Yes | Yes |
17+
| Optional Setup/Teardown | No | Yes |
18+
| Different Setup/Teardown <br/> For Each Test in a Single Package| No | Yes - Annotations<sup>1</sup> |
19+
| Suite Definition Storage | Tables | Package - Annotations<sup>1</sup> |
20+
| Multiple Suites | Yes | Yes |
21+
| Suites can contain Suites | No | Yes |
22+
| Automatic Test detection | No | Yes - Annotations<sup>1</sup>|
23+
| Unconstrained naming of Test packages | No - prefixes | Yes - name not relevant|
24+
| Require Prefix on Test procedures | No - prefixes | Yes - name not relevant|
25+
| Auto Compilation of Tests | Yes | No (Let us know if you use this) |
26+
| Assertion Library | 30 assertions<sup>2</sup> | 26 matchers (13 + 13 negated) |
27+
| Extendable assertions | No | Yes - custom matchers |
28+
| PLSQL Record Assertions | generated code through **utRecEq** Package | [possible on Oracle 12c+](https://oracle-base.com/articles/12c/using-the-table-operator-with-locally-defined-types-in-plsql-12cr1) using [cursor matchers](userguide/expectations.md#comparing-cursors)|
29+
| Test Skeleton Generation | Yes | No (Let us know if you use this) |
30+
| **Test Execution<sup>3</sup>** | | |
31+
| Single Test Package Execution | Yes | Yes |
32+
| Single Test Procedure Execution | No | Yes |
33+
| Test Suite Execution | Yes | Yes |
34+
| Subset of Suite Execution | No | Yes |
35+
| Multiple Suite Execution | No | Yes |
36+
| Organizing Suites into hierarchies | No | Yes |
37+
| **Code Coverage Reporting** | No | Yes |
38+
| Html Coverage Report | No | Yes |
39+
| Sonar XML Coverage Report | No | Yes |
40+
| Coveralls Json Coverage Report | No | Yes |
41+
| Framework Transaction Control | No | Yes - Annotations<sup>1</sup> |
42+
| **Test Output** | | |
43+
| Real-time test execution progress reporting | No | Yes |
44+
| Multiple Output Reporters can be used during test execution | No| Yes |
45+
| DBMS_OUTPUT | Yes | Yes (clean formatting) |
46+
| File | Yes (to db server only)| Yes (on client side) |
47+
| Stored in Table | Yes | No (can be added as custom reporter) |
48+
| XUnit format support | No | Yes |
49+
| HTML Format | Yes | No |
50+
| Custom Output reporter | Yes-needs configuration| Yes - no config needed |
51+
52+
<sup>1</sup> Annotations are specially formatted comments in your package specification. This enables *declarative* test configuration that is coupled with the source code. See Documentation for more details.
53+
54+
<sup>2</sup> **utAssert2** package - Contains 59 Assertions - 2 Not implemented = 57, 28 are duplicated only change on outcome_in parameter 57-28 = 29, **utPipe** package - Contains 1 Assertion 29 + 1 = 30
55+
56+
<sup>3</sup> Test execution comparison is in a single call so the results are combined. We know it was always possible to group in any way with multiple calls. But that may not be desired under a CI system where you want a single JUnit XML Output.

‎docs/index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
![version](https://img.shields.io/badge/version-v3.1.8.3188-blue.svg)
1+
![version](https://img.shields.io/badge/version-v3.1.9.3268-blue.svg)
22

33
# Introduction to utPLSQL
44

@@ -25,6 +25,7 @@ The framework follows industry standards and best patterns of modern Unit Testin
2525
- [License](about/license.md)
2626
- [Support](about/support.md)
2727
- [Authors](about/authors.md)
28+
- [Version 2 to Version 3 Comparison](compare_version2_to_3.md)
2829

2930
# Demo project
3031

‎docs/userguide/advanced_data_comparison.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
![version](https://img.shields.io/badge/version-v3.1.8.3188-blue.svg)
1+
![version](https://img.shields.io/badge/version-v3.1.9.3268-blue.svg)
22

33
# Advanced data comparison
44

0 commit comments

Comments
 (0)
0