Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,6 @@ before_script:
- if [[ ! $TRAVIS_TAG ]]; then bash .travis/install.sh; fi
- if [[ ! $TRAVIS_TAG ]]; then bash .travis/install_utplsql_release.sh; fi
- if [[ ! $TRAVIS_TAG ]]; then bash .travis/run_examples.sh; fi
- if [[ ! $TRAVIS_TAG ]]; then bash .travis/run_old_tests.sh; fi

script:
- if [[ ! $TRAVIS_TAG ]]; then bash test/install_and_run_tests.sh; fi
Expand Down
10 changes: 0 additions & 10 deletions .travis/run_old_tests.sh

This file was deleted.

11 changes: 2 additions & 9 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,9 +138,7 @@ Whenever a new version of utPLSQL or a new version of utPLSQL-cli is available,

## Running unit tests

Currently we use two forms of unit tests in our CI build:
- sql scripts as unit tests in the `old_tests` directory
- utPLSQL v3 unit tests in the `test` directory
utPLSQL v3 unit tests are located in the `test` directory

Before you push any changes and create a pull request to the utPLSQL project repository, make sure that all of the tests are executing successfully in your local environment.

Expand All @@ -150,18 +148,13 @@ Every new functionality needs to be documented by unit tests that cover both hap
> We do our best to keep utPLSQL covered with unit tests.
> Lack of sufficient unit testing is a perfect reason for PR to be rejected.

To suite of legacy unit tests execute:
```bash
development/env.sh
old_tests/runAll.sh
```
To run a full suite of unit tests execute:
```bash
development/env.sh
test/install_and_run_tests.sh
```

You can review the results of tests as well as see information about code coverage in `./old_tests/coverage.html, ./coverage.html` files.
You can review the results of tests as well as see information about code coverage in `./coverage.html` file.


## Modules
Expand Down
File renamed without changes.
File renamed without changes.
396 changes: 0 additions & 396 deletions old_tests/RunAll.sql

This file was deleted.

4 changes: 0 additions & 4 deletions old_tests/helpers/department.tps

This file was deleted.

4 changes: 0 additions & 4 deletions old_tests/helpers/department1.tps

This file was deleted.

25 changes: 0 additions & 25 deletions old_tests/helpers/html_coverage_test.pck

This file was deleted.

71 changes: 0 additions & 71 deletions old_tests/helpers/test_package_1.pck

This file was deleted.

69 changes: 0 additions & 69 deletions old_tests/helpers/test_package_2.pck

This file was deleted.

80 changes: 0 additions & 80 deletions old_tests/helpers/test_package_3.pck

This file was deleted.

67 changes: 0 additions & 67 deletions old_tests/helpers/test_reporters.pkb

This file was deleted.

Loading