Added 12.2 Coverage

lwasylow · lwasylow · commit 4f83357cc912 · 2018-03-14T20:27:49.000Z
Update block to be called from dynamic sql to avoid a compilation issues.
Updated documentation
diff --git a/docs/userguide/coverage.md b/docs/userguide/coverage.md
@@ -29,7 +29,7 @@ If you have `execute` privilege on the code that are tested, but do not have `cr
 If you have `execute` privilege only on the unit tests, but do not have `execute` privilege on the code that is tested, the code will not be reported by coverage - as if it did not exist in the database.
 If the code that is testes is complied as NATIVE, the code coverage will not be reported as well.
 
-## Running unite tests with coverage
+## Running unit tests with coverage
 Using code coverage functionality is as easy as using any other [reporter](reporters.md) for utPLSQL project. All you need to do is run your tests from your preferred SQL tool and save the outcomes of reporter to a file.
 All you need to do, is pass the constructor of the reporter to your `ut.run`
 
@@ -40,6 +40,8 @@ begin
 end;
 /
 ```
+
+
 Executes all unit tests in current schema, gather information about code coverage and output the html text into DBMS_OUTPUT.
 The `ut_coverage_html_reporter` will produce a interactive HTML report. You may see a sample of code coverage for utPLSQL project [here](https://utplsql.github.io/utPLSQL-coverage-html/)
 
@@ -52,6 +54,20 @@ The report allow to navigate to every source and inspect line by line coverage.
 ![Coverage Details page](../images/coverage_html_details.png)
 
 
+#### Oracle 12.2 block coverage.
+In Oracle 12.2 new functionality was released which supports native [block coverage](https://docs.oracle.com/en/database/oracle/oracle-database/12.2/arpls/DBMS_PLSQL_CODE_COVERAGE.html#GUID-55A9E502-9EC2-4118-B292-DC79E6DC465E).
+This has been enabled in utPLSQL code coverage as a separate option. It can be invoked by passing a argument a_coverage_type with value 'block'. By default profiler option is enabled ('proftab').
+
+Example:
+```sql
+begin
+  ut.run(ut_coverage_html_reporter(),a_coverage_type => 'block');
+end;
+/
+```
+
+In this mode html reporter will show additionally number of lines that been partially covered and highlight them in orange. Number of blocks in code, blocks covered and missed.
+
 ## Coverage reporting options
 By default the database schema/schemes containing the tests that were executed during the run, are fully reported by coverage reporter.
 All valid unit tests are excluded from the report regardless if they were invoked or not. This way the coverage report is not affected by presence of tests and contains only the tested code.
diff --git a/source/core/coverage/ut_coverage_helper.pkb b/source/core/coverage/ut_coverage_helper.pkb
@@ -51,14 +51,14 @@ create or replace package body ut_coverage_helper is
   end;
 
   procedure coverage_start_internal(a_run_comment varchar2,a_coverage_type in varchar2)  is
-  --l_start_block varchar2(32767):= 'call dbms_plsql_code_coverage.start_coverage(run_comment => :a_run_comment)
-  --                               into :g_coverage_id';
+  l_start_block varchar2(32767):= 'call dbms_plsql_code_coverage.start_coverage(run_comment => :a_run_comment)
+                                   into :g_coverage_id';
   begin
     set_coverage_type(a_coverage_type);
     -- Make it dynamic to allow for block coverage.
     if get_coverage_type = 'block' then
-       --execute immediate l_start_block USING IN a_run_comment, OUT g_coverage_id;
-       g_coverage_id := dbms_plsql_code_coverage.start_coverage(run_comment => a_run_comment);
+       execute immediate l_start_block USING IN a_run_comment, OUT g_coverage_id;
+       --g_coverage_id := dbms_plsql_code_coverage.start_coverage(run_comment => a_run_comment);
     else
        dbms_profiler.start_profiler(run_comment => a_run_comment, run_number => g_coverage_id);
        coverage_pause();
@@ -105,11 +105,12 @@ create or replace package body ut_coverage_helper is
   end;
 
   procedure coverage_stop is
+  l_stop_block varchar2(100) := 'call dbms_plsql_code_coverage.stop_coverage()';
   begin
     if not g_develop_mode then
       g_is_started := false;
       if get_coverage_type = 'block' then
-         dbms_plsql_code_coverage.stop_coverage;
+         execute immediate l_stop_block;
       else
          dbms_profiler.stop_profiler();
       end if;
