utPLSQL · jgebal · Jun 8, 2026 · Jun 7, 2026 · Jun 8, 2026
diff --git a/docs/compare_version2_to_3.md b/docs/compare_version2_to_3.md
@@ -37,7 +37,6 @@ There is a [migration tool](https://github.com/utPLSQL/utPLSQL-v2-v3-migration)
 | **Code Coverage Reporting**            |  No                    | Yes                    |
 | Html Coverage Report                   |  No                    | Yes                    |
 | Sonar XML Coverage Report              |  No                    | Yes                    |
-| Coveralls Json Coverage Report         |  No                    | Yes                    |
 | Framework Transaction Control          |  No                    | Yes - Annotations<sup>1</sup> | 
 | **Test Output**                        |                        |                        |
 | Real-time test execution progress reporting | No                | Yes                    |

diff --git a/docs/userguide/coverage.md b/docs/userguide/coverage.md
@@ -22,7 +22,6 @@ To obtain information about code coverage for unit tests, run utPLSQL with one o
 The following code coverage reporters are supplied with utPLSQL:
 
 * `ut_coverage_html_reporter` - generates a HTML coverage report providing summary and detailed information on code coverage. The HTML reporter is based on the open-source [simplecov-html](https://github.com/colszowka/simplecov-html) reporter for Ruby. It includes source code of the code that was covered (if the code is accessible for test user)  
-* `ut_coveralls_reporter` - generates a [Coveralls compatible JSON](https://coveralls.zendesk.com/hc/en-us/articles/201774865-API-Introduction) coverage report providing detailed information on code coverage with line numbers. This coverage report is designed to be consumed by cloud services like [Coveralls](https://coveralls.io)
 * `ut_coverage_sonar_reporter`  - generates a [Sonar Compatible XML](https://docs.sonarqube.org/latest/analysis/generic-test/) coverage report providing detailed information on code coverage with line numbers. This coverage report is designed to be consumed by services like [SonarQube](https://www.sonarqube.org/) and [SonarCloud](https://about.sonarcloud.io/)
 * `ut_coverage_cobertura_reporter`  - generates a basic Cobertura coverage (http://cobertura.sourceforge.net/xml/coverage-04.dtd) report providing detailed information on code coverage with line numbers. This coverage report is designed to be consumed by services like TFS and Jenkins. Check this link for an example of XML generated by Java: https://raw.githubusercontent.com/jenkinsci/cobertura-plugin/master/src/test/resources/hudson/plugins/cobertura/coverage-with-data.xml
 
@@ -310,17 +309,17 @@ Executes test `test_award_bonus` in schema `unit_test_schema`. Coverage will be
 
 ### Project based Coverage
 
-utPLSQL provides reporters that produce reports consumable by external tools like `Sonar`/`SonarCloud` & `Coveralls`.
+utPLSQL provides reporters that produce reports consumable by external tools like `Sonar`/`SonarCloud`.
 
-Services like Sonar, Coveralls and others perform analysis based on source code in project files.
+Services like Sonar and others perform analysis based on source code in project files.
 They are abstracted from database, schema names, packages, procedures and functions, and operate on a more generic concept of project source code.
 
 To be able to effectively use reporters dedicated for those tools, utPLSQL provides functionality for mapping database object names to project files.
 
 There are a few significant differences when running coverage on project files compared to running coverage on schema(s).
 
 - Coverage is only reported on objects that were successfully mapped to project files.
-- Project files (database objects) that were not executed at all are not reported as fully uncovered. It is up to the consumer (Sonar/Coveralls) to determine if project file should be considered as 0% coverage or just ignored.
+- Project files (database objects) that were not executed at all are not reported as fully uncovered. It is up to the consumer (Sonar) to determine if project file should be considered as 0% coverage or just ignored.
 
 In order to successfully use coverage on project files, those files must be mapped to database objects.
 

diff --git a/readme.md b/readme.md
@@ -19,7 +19,7 @@ utPLSQL is a unit testing framework for Oracle PL/SQL and SQL, following industr
 - Hierarchies of test suites configured with annotations
 - Automatic (configurable) transaction control
 - Built-in [coverage](docs/userguide/coverage.md) reporting
-- Integration with SonarQube, Coveralls, Jenkins and TeamCity via [reporters](docs/userguide/reporters.md)
+- Integration with SonarQube, Jenkins and TeamCity via [reporters](docs/userguide/reporters.md)
 - Plugin architecture for reporters and matchers
 - Flexible and simple test invocation
 - Multi-format reporting from the [command line client](https://github.com/utPLSQL/utPLSQL-cli)

diff --git a/source/create_grants.sql b/source/create_grants.sql
@@ -108,7 +108,6 @@ grant execute on &&ut3_owner..ut_tap_reporter to &ut3_user;
 --reporters - coverage
 grant execute on &&ut3_owner..ut_coverage_html_reporter to &ut3_user;
 grant execute on &&ut3_owner..ut_coverage_sonar_reporter to &ut3_user;
-grant execute on &&ut3_owner..ut_coveralls_reporter to &ut3_user;
 grant execute on &&ut3_owner..ut_coverage_cobertura_reporter to &ut3_user;
 --reporters - debug
 grant execute on &&ut3_owner..ut_debug_reporter to &ut3_user;

diff --git a/source/create_synonyms.sql b/source/create_synonyms.sql
@@ -123,7 +123,6 @@ create &action_type. synonym &ut3_user.ut_tap_reporter for &&ut3_owner..ut_tap_r
 --reporters - coverage
 create &action_type. synonym &ut3_user.ut_coverage_html_reporter for &&ut3_owner..ut_coverage_html_reporter;
 create &action_type. synonym &ut3_user.ut_coverage_sonar_reporter for &&ut3_owner..ut_coverage_sonar_reporter;
-create &action_type. synonym &ut3_user.ut_coveralls_reporter for &&ut3_owner..ut_coveralls_reporter;
 create &action_type. synonym &ut3_user.ut_coverage_cobertura_reporter for &&ut3_owner..ut_coverage_cobertura_reporter;
 --reporters - debug
 create &action_type. synonym &ut3_user.ut_debug_reporter for &&ut3_owner..ut_debug_reporter;

diff --git a/source/install.sql b/source/install.sql
@@ -355,8 +355,6 @@ prompt Installing DBMSPLSQL Tables objects into &&ut3_owner schema
 @@install_component.sql 'reporters/ut_coverage_html_reporter.tpb'
 @@install_component.sql 'reporters/ut_coverage_sonar_reporter.tps'
 @@install_component.sql 'reporters/ut_coverage_sonar_reporter.tpb'
-@@install_component.sql 'reporters/ut_coveralls_reporter.tps'
-@@install_component.sql 'reporters/ut_coveralls_reporter.tpb'
 @@install_component.sql 'reporters/ut_coverage_cobertura_reporter.tps'
 @@install_component.sql 'reporters/ut_coverage_cobertura_reporter.tpb'
 @@install_component.sql 'reporters/ut_realtime_reporter.tps'

diff --git a/source/reporters/ut_coveralls_reporter.tpb b/source/reporters/ut_coveralls_reporter.tpb
diff --git a/source/reporters/ut_coveralls_reporter.tps b/source/reporters/ut_coveralls_reporter.tps
diff --git a/source/uninstall_objects.sql b/source/uninstall_objects.sql
@@ -74,8 +74,6 @@ drop synonym be_within;
 
 drop synonym be_within_pct;
 
-drop type ut_coveralls_reporter force;
-
 drop type ut_coverage_sonar_reporter force;
 
 drop type ut_coverage_cobertura_reporter force;

diff --git a/test/install_ut3_user_tests.sql b/test/install_ut3_user_tests.sql
@@ -50,7 +50,6 @@ set define on
 @@ut3_user/reporters/test_coverage/test_extended_coverage.pks
 @@ut3_user/reporters/test_coverage/test_html_coverage_reporter.pks
 set define off
-@@ut3_user/reporters/test_coverage/test_coveralls_reporter.pks
 @@ut3_user/reporters/test_coverage/test_cov_cobertura_reporter.pks
 @@ut3_user/reporters/test_coverage/test_coverage_sonar_reporter.pks
 set define on
@@ -93,7 +92,6 @@ set define on
 @@ut3_user/reporters/test_coverage/test_extended_coverage.pkb
 @@ut3_user/reporters/test_coverage/test_html_coverage_reporter.pkb
 set define off
-@@ut3_user/reporters/test_coverage/test_coveralls_reporter.pkb
 @@ut3_user/reporters/test_coverage/test_cov_cobertura_reporter.pkb
 @@ut3_user/reporters/test_coverage/test_coverage_sonar_reporter.pkb
 set define on

diff --git a/test/run_tests.sh b/test/run_tests.sh
@@ -17,7 +17,6 @@ time utPLSQL-cli/bin/utplsql run UT3_TESTER_HELPER/ut3@//${CONNECTION_STR} -D \
 -f=ut_coverage_sonar_reporter     -o=coverage.xml \
 -f=ut_coverage_cobertura_reporter -o=cobertura.xml \
 -f=ut_coverage_html_reporter      -o=coverage.html \
--f=ut_coveralls_reporter          -o=coverage.json \
 -f=ut_sonar_test_reporter         -o=test_results.xml \
 -f=ut_junit_reporter              -o=junit_test_results.xml \
 -f=ut_tfs_junit_reporter          -o=tfs_test_results.xml \

diff --git a/test/ut3_user/api/test_ut_runner.pkb b/test/ut3_user/api/test_ut_runner.pkb
@@ -386,7 +386,6 @@ end;';
       select 'UT3_DEVELOP.UT_DEBUG_REPORTER', 'Y' from dual union all
       select 'UT3_DEVELOP.UT_COVERAGE_HTML_REPORTER', 'Y' from dual union all
       select 'UT3_DEVELOP.UT_COVERAGE_SONAR_REPORTER', 'Y' from dual union all
-      select 'UT3_DEVELOP.UT_COVERALLS_REPORTER', 'Y' from dual union all
       select 'UT3_DEVELOP.UT_DOCUMENTATION_REPORTER', 'Y' from dual union all
       select 'UT3_DEVELOP.UT_JUNIT_REPORTER', 'Y' from dual union all
       select 'UT3_DEVELOP.UT_REALTIME_REPORTER', 'Y' from dual union all

diff --git a/test/ut3_user/reporters/test_coverage/test_coveralls_reporter.pkb b/test/ut3_user/reporters/test_coverage/test_coveralls_reporter.pkb
diff --git a/test/ut3_user/reporters/test_coverage/test_coveralls_reporter.pks b/test/ut3_user/reporters/test_coverage/test_coveralls_reporter.pks