wtPLSQL
diff --git a/‎docs/demo/Table-Test.md
Lines changed: 48 additions & 188 deletions b/‎docs/demo/Table-Test.md
Lines changed: 48 additions & 188 deletions
diff --git a/‎docs/demo/Trigger-Test.md
Lines changed: 15 additions & 27 deletions b/‎docs/demo/Trigger-Test.md
Lines changed: 15 additions & 27 deletions
@@ -1,208 +1,85 @@
 [Demos and Examples](README.md)
 
-# Test a Trigger
+# Test Table Constraints
 
 ---
 
-## Triggers
-There are many kinds of triggers.  All of them use PL/SQL to define actions taken when the the trigger is activated.
+The syntax diagram in Oracle's "Database SQL Language Reference" (11.2) gives the list of [constraints](https://docs.oracle.com/cd/E11882_01/server.112/e41084/clauses002.htm#CJAEDFIB) this way:
 
-The "Database PL/SQL Language Reference" (11.2) [groups triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#BABBJHHG) this way:
-* Simple DML Trigger
-* Compound DML Trigger
-* Instead of DML Trigger
-* System Trigger
+* Not Null
+* Unique (Key)
+* Primary Key
+* References (Foreign Key)
+* Check
 
-[Simple DML Triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#BABBJHHG):
-* before delete
-* before insert
-* before update
-* after delete
-* after insert
-* after update
+Typical unit testing (or white box testing) does not include the testing of constraints.  In large part, these constraints are assumed to work without testing.  Confirmation of continued function of these constraints is a reason to test them.
 
-[Compound DML Triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#BABDFIFA):
-* before delete statement
-* before insert statement
-* before update statement
-* before each row deleted
-* before each row inserted
-* before each row updated
-* instead of each row deleted
-* instead of each row inserted
-* instead of each row updated
-* after each row deleted
-* after each row inserted
-* after each row updated
-* after delete statement
-* after insert statement
-* after update statement
+## Table with Constraints
 
-[Instead of DML Triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#CIHEIGBE):
-* instead of delete
-* instead of insert
-* instead of update
-
-[System Triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#BABHEFGE):
-* before alter statement
-* before analyze statement
-* before associate statistics statement
-* before audit statement
-* before comment statement
-* before create statement
-* before database shutdown
-* before disassociate statistics statement
-* before drop statement
-* before grant statement
-* before noaudit statement
-* before rename statement
-* before revoke statement
-* before truncate statement
-* before user logoff
-* instead of alter statement
-* instead of analyze statement
-* instead of associate statistics statement
-* instead of audit statement
-* instead of comment statement
-* instead of create statement
-* instead of disassociate statistics statement
-* instead of drop statement
-* instead of grant statement
-* instead of noaudit statement
-* instead of rename statement
-* instead of revoke statement
-* instead of truncate statement
-* after alter statement
-* after analyze statement
-* after associate statistics statement
-* after audit statement
-* after comment statement
-* after create statement
-* after database startup
-* after db role change
-* after disassociate statistics statement
-* after drop statement
-* after grant statement
-* after noaudit statement
-* after rename statement
-* after revoke statement
-* after servererror
-* after truncate statement
-* after user logon
-* after user suspend
-
-For brevity, an example is provided for only one of these triggers.
-
-## Table with Insert Trigger
-
-Before a trigger an be created, a table must be created.  The table will have a surrogate key, a natural key, and audit data.
+A table with constraints is needed for testing.  This table has several constraints
 
 Run this:
 
 ```
-create sequence trigger_test_seq;
-
-create table trigger_test_tab
-  (id           number        constraint trigger_test_tab_nn1 not null
-  ,name         varchar2(30)  constraint trigger_test_tab_nn2 not null
-  ,created_dtm  date          constraint trigger_test_tab_nn3 not null
-  ,constraint trigger_test_tab_pk primary key (id)
-  ,constraint trigger_test_tab_uk1 unique (name)
+create table table_test_tab
+  (id     number        constraint table_test_tab_nn1 not null
+  ,name   varchar2(10)  constraint table_test_tab_nn2 not null
+  ,constraint table_test_tab_pk primary key (id)
+  ,constraint table_test_tab_uk1 unique (name)
+  ,constraint table_test_tab_ck1 check (name = upper(name))
   );
 ```
 
-The trigger to be tested does 2 things
-1) Populate the surrogate key, if needed.
-2) Overwrite the audit data.
-
-Run this:
-
-```
-create or replace trigger trigger_test_bir
-  before insert on trigger_test_tab
-  for each row
-begin
-  if :new.id is null
-  then
-     :new.id := trigger_test_seq.nextval;
-  end if;
-  :new.created_dtm := sysdate;
-end;
-/
-```
+For brevity, the check constraint will be the only constraint tested.
 
-## Create a Simple Test Runner
+## Test Runner
 
-All test runners are written as a PL/SQL package. A simple package is created first.  A DBOUT is also identified.
+Create a simple test runner.
 
 Run this:
 
 ```
-create or replace package trigger_test_pkg authid definer
+create or replace package table_test_pkg authid definer
 as
    procedure wtplsql_run;
-end trigger_test_pkg;
+end table_test_pkg;
 /
 ```
 
-And run this:
-
-```
-create or replace package body trigger_test_pkg
-as
-   --% WTPLSQL SET DBOUT "TRIGGER_TEST_BIR:TRIGGER" %--
-   procedure wtplsql_run
-   as
-   begin
-      null;
-   end wtplsql_run;
-end trigger_test_pkg;
-/
-```
-
-## Add a Trigger Test Case
-
-The trigger being tested is a table DML trigger. Testing of a table trigger like this requires a modification of the data in the table.  The consequences of leaving this modified data after the test must be considered.  In this test, the data modification will not be preserved. 
+The constraint being tested ensures the name is in upper case.  Testing of the constraint requires a modification of the data in the table.  The consequences of leaving this modified data after the test must be considered.  In this test, the data modification will not be preserved.
 
 This test case will only test a happy path.
 
 Run this:
 
 ```
-create or replace package body trigger_test_pkg
+create or replace package body table_test_pkg
 as
    procedure t_happy_path_1
    is
-      l_rec        trigger_test_tab%ROWTYPE;
+      l_rec  table_test_tab%ROWTYPE; 
    begin
-      wt_assert.g_testcase := 'Constructor Happy Path 1';
-      -- This uncommitted DML will ROLLBACK if an exception is raised.
-      insert into trigger_test_tab (name) values ('Test1')
-         returning id into l_rec.id;
-      wt_assert.isnotnull (
-         msg_in        => 'l_rec.id',
-         check_this_in => l_rec.id);
-      select * into l_rec from trigger_test_tab where id = l_rec.id;
+      wt_assert.g_testcase := 'Happy Path 1';
+      wt_assert.raises (
+         msg_in         => 'Successful Insert',
+         check_call_in  => 'insert into table_test_tab (id, name) values (1, ''TEST1'')',
+         against_exc_in => '');
+      select * into l_rec from table_test_tab where id = 1;
       wt_assert.eq (
-         msg_in          => 'l_rec.name',
+         msg_in          => 'Confirm l_rec.name',
          check_this_in   => l_rec.name,
-         against_this_in => 'Test1');
-      wt_assert.isnotnull (
-         msg_in          => 'l_rec.created_dtm',
-         check_this_in   => l_rec.created_dtm);
+         against_this_in => 'TEST1');
       rollback;
    end t_happy_path_1;
-   --% WTPLSQL SET DBOUT "TRIGGER_TEST_BIR:TRIGGER" %--
-   procedure wtplsql_run
-   is
+   procedure wtplsql_run is
    begin
       t_happy_path_1;
    end wtplsql_run;
-end trigger_test_pkg;
+end table_test_pkg;
 /
 ```
 
-Check the results of the 
+## Check the results
 
 Run this:
 
@@ -219,42 +96,25 @@ end;
 And Get This:
 
 ```
-    wtPLSQL 1.1.0 - Run ID 58: 23-Jun-2018 12:04:20 PM
+    wtPLSQL 1.1.0 - Run ID 70: 23-Jun-2018 07:30:47 PM
 
-  Test Results for WTP_DEMO.TRIGGER_TEST_PKG
-       Total Test Cases:        1       Total Assertions:        3
+  Test Results for WTP_DEMO.TABLE_TEST_PKG
+       Total Test Cases:        1       Total Assertions:        2
   Minimum Interval msec:        0      Failed Assertions:        0
-  Average Interval msec:       76       Error Assertions:        0
-  Maximum Interval msec:      228             Test Yield:   100.00%
-   Total Run Time (sec):      0.2
+  Average Interval msec:      443       Error Assertions:        0
+  Maximum Interval msec:      886             Test Yield:   100.00%
+   Total Run Time (sec):      0.9
 
-  Code Coverage for TRIGGER WTP_DEMO.TRIGGER_TEST_BIR
-          Ignored Lines:        0   Total Profiled Lines:        5
-         Excluded Lines:        0   Total Executed Lines:        4
-  Minimum LineExec usec:        1     Not Executed Lines:        0
-  Average LineExec usec:      137          Unknown Lines:        1
-  Maximum LineExec usec:      326          Code Coverage:   100.00%
-  Trigger Source Offset:        3
-
- - WTP_DEMO.TRIGGER_TEST_PKG Test Result Details (Test Run ID 58)
+ - WTP_DEMO.TABLE_TEST_PKG Test Result Details (Test Run ID 70)
 -----------------------------------------------------------
- ---- Test Case: Constructor Happy Path 1
- PASS  228ms l_rec.id. ISNOTNULL - Expected NOT NULL and got "15"
- PASS    0ms l_rec.name. EQ - Expected "Test1" and got "Test1"
- PASS    0ms l_rec.created_dtm. ISNOTNULL - Expected NOT NULL and got "23-JUN-2018 12:04:20"
-
- - WTP_DEMO.TRIGGER_TEST_BIR TRIGGER Code Coverage Details (Test Run ID 58)
-Source               TotTime MinTime   MaxTime     
-  Line Stat Occurs    (usec)  (usec)    (usec) Text
------- ---- ------ --------- ------- --------- ------------
-     4 UNKN      0        11      11        11 begin
-     5 EXEC      1       216     216       216   if :new.id is null
-     7 EXEC      1       326     326       326      :new.id := trigger_test_seq.nextval;
-     9 EXEC      1         4       1         3   :new.created_dtm := sysdate;
-    10 EXEC      1         2       2         2 end;
+ ---- Test Case: Happy Path 1
+ PASS  886ms Successful Insert. RAISES/THROWS - No exception was expected. Exception raised was "". Exception raised by: "insert into table_test_tab (id, name) values (1, 'TEST1')".
+ PASS    0ms Confirm l_rec.name. EQ - Expected "TEST1" and got "TEST1"
 ```
 
-This is report level 30, the most detailed level of reporting.  Starting from the top, we find the test runner executed 1 test case and 3 assertions.  All tests passed for a 100% yield.  The code coverage for the trigger shows 5 profiles, 4 executed, and a code coverage of 100%.  Notice the trigger offset of 3 which aligns the source code with the profiled lines.
+This is report level 30, the most detailed level of reporting.  Starting from the top, we find the test runner executed 1 test case and 2 assertions.  All tests passed for a 100% yield.  There is no code coverage for the constraints.
+
+This is not a complete test.  More test cases are needed to confirm other constraints and sad path .
 
 ---
 [Demos and Examples](README.md)
@@ -5,7 +5,7 @@
 ---
 
 ## Triggers
-There are many kinds of triggers.  All of them use PL/SQL to define actions taken when the the trigger is activated.
+There are many kinds of triggers.  All of them use PL/SQL to define actions taken when the trigger is activated.
 
 The "Database PL/SQL Language Reference" (11.2) [groups triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#BABBJHHG) this way:
 * Simple DML Trigger
@@ -15,11 +15,11 @@ The "Database PL/SQL Language Reference" (11.2) [groups triggers](https://docs.o
 
 [Simple DML Triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#BABBJHHG):
 
- Before | After
---------|-------------
- Delete | Delete
- Insert | Insert
- Update | Update
+ Before        | After
+---------------|--------------
+ Before Delete | After Delete
+ Before Insert | After Insert
+ Before Update | After Update
 
 [Compound DML Triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#BABDFIFA):
 
@@ -33,9 +33,12 @@ The "Database PL/SQL Language Reference" (11.2) [groups triggers](https://docs.o
  Update Statement  |                   | Update Statement
 
 [Instead of DML Triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#CIHEIGBE):
-* instead of delete
-* instead of insert
-* instead of update
+
+ Instead of        |
+-------------------|
+ Instead of Delete |
+ Instead of Insert |
+ Instead of Update |
 
 [System Triggers](https://docs.oracle.com/cd/E11882_01/appdev.112/e25519/create_trigger.htm#BABHEFGE):
 
@@ -114,23 +117,6 @@ end trigger_test_pkg;
 /
 ```
 
-And run this:
-
-```
-create or replace package body trigger_test_pkg
-as
-   --% WTPLSQL SET DBOUT "TRIGGER_TEST_BIR:TRIGGER" %--
-   procedure wtplsql_run
-   as
-   begin
-      null;
-   end wtplsql_run;
-end trigger_test_pkg;
-/
-```
-
-## Add a Trigger Test Case
-
 The trigger being tested is a table DML trigger. Testing of a table trigger like this requires a modification of the data in the table.  The consequences of leaving this modified data after the test must be considered.  In this test, the data modification will not be preserved. 
 
 This test case will only test a happy path.
@@ -171,7 +157,7 @@ end trigger_test_pkg;
 /
 ```
 
-Check the results of the 
+## Check the results
 
 Run this:
 
@@ -225,5 +211,7 @@ Source               TotTime MinTime   MaxTime
 
 This is report level 30, the most detailed level of reporting.  Starting from the top, we find the test runner executed 1 test case and 3 assertions.  All tests passed for a 100% yield.  The code coverage for the trigger shows 5 profiles, 4 executed, and a code coverage of 100%.  Notice the trigger offset of 3 which aligns the source code with the profiled lines.
 
+This is not a complete test.  More test cases are needed to confirm various values are handled correctly when inserted.
+
 ---
 [Demos and Examples](README.md)