{"id":244,"date":"2008-05-31T08:07:11","date_gmt":"2008-05-31T07:07:11","guid":{"rendered":"http:\/\/bar-solutions.com\/wordpress\/?p=244"},"modified":"2008-05-31T09:27:19","modified_gmt":"2008-05-31T08:27:19","slug":"testing-rulegen-using-codetester","status":"publish","type":"post","link":"https:\/\/blog.bar-solutions.com\/?p=244","title":{"rendered":"Testing Rulegen using Codetester"},"content":{"rendered":"

When I was confronted with the possibilities of Rulegen<\/a> it made me wonder: How can these rules\"codetest-logo\"<\/a> be \"RuleGen_Logo\"<\/a>tested. I have some experience using CodeTester<\/a> but as the name says, it\u2019s a code tester where rulegen<\/a> builds rules in the database that can actually only be tested using SQL statements (insert, update, delete).<\/p>\n

<\/p>\n

When I still want to use CodeTester<\/a> to perform the actual testing I need to encapsulate the insert, update and delete statements in simple procedures. I don\u2019t want to have all the values for the record as parameters, but I figured I can create a record based on the table layout in which I can put all my values. That way I can populate this record in the pre-execution code of the test and then have the insert (or update or delete) be called in the test itself. I have build my test set around a simple table and a simple rule to be evaluated. <\/p>\n

The rule to be enforced is: We only allow a single PRESIDENT in the table at a certain time. <\/p>\n

Consider the following table: <\/p>\n

I built this rule in the RuleGen<\/a> Front-End: <\/p>\n

Details of rule ONEPRESIDENT <\/p>\n\n\n\n\n\n\n
Rule:<\/td>\nONEPRESIDENT<\/td>\n<\/tr>\n
Description (short):<\/td>\nJust one president allowed in the entire table…<\/td>\n<\/tr>\n
Documentation:<\/td>\nWe don\u2019t want to have more than one president in the emp table. We can have less than one president, but no more than that. This means we have to check when inserting or updating rows but not when deleting them.<\/td>\n<\/tr>\n
Involved columns:<\/td>\nDEMO.EMP.JOB <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Transition Effect Queries for Rule ONEPRESIDENT <\/p>\n\n\n\n\n\n\n\n
Description:<\/td>\nJust one president allowed in the entire table…<\/td>\n<\/tr>\n
Violation case:<\/td>\n1<\/td>\n<\/tr>\n
Insert TE-query:<\/td>\nselect distinct \u2018x\u2019 as NO_PARAMS
  from inserted_rows
where job = \u2018PRESIDENT\u2019<\/td>\n<\/tr>\n
Update TE-query:<\/td>\nselect distinct \u2018x\u2019 as NO_PARAMS
  from updated_rows
where new_job=\u2019PRESIDENT\u2019
   and old_job<>\u2019PRESIDENT<\/td>\n<\/tr>\n
Delete TE-query:<\/td>\nselect distinct \u2018x\u2019 as NO_PARAMS
  from deleted_rows
where 0=1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Constraint Validation Query for Rule ONEPRESIDENT<\/p>\n\n\n\n\n\n
Description:<\/td>\nJust one president allowed in the entire table…<\/td>\n<\/tr>\n
Violation case:<\/td>\n1<\/td>\n<\/tr>\n
Constraint validation query:<\/td>\nselect \u2018At most one PRESIDENT allowed (found \u2018||to_char(num_presidents)||\u2019).\u2019 as msg
  from (select count(*) as num_presidents
          from emp
         where job=\u2019PRESIDENT\u2019)
  where num_presidents > 1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

I need to create a package which holds a record based on this table:
TYPE EMP_rt IS RECORD(
    EMPNO EMP.EMPNO%type,
    ENAME EMP.ENAME%type,
    JOB EMP.JOB%type,
    MGR EMP.MGR%type,
    HIREDATE EMP.HIREDATE%type,
    SAL EMP.SAL%type,
    COMM EMP.COMM%type,
    DEPTNO EMP.DEPTNO%type
  ); <\/p>\n

And I need to create some procedures to perform the DML for me:
  PROCEDURE ins;
  PROCEDURE upd;
  PROCEDURE del; <\/p>\n

And the implementation of these procedures:
PROCEDURE ins
IS
BEGIN
  — insert the values in the rec record into the table
  INSERT INTO EMP (
                EMPNO,
                ENAME,
                JOB,
                MGR,
                HIREDATE,
                SAL,
                COMM,
                DEPTNO
               ) VALUES (
                rec.EMPNO,
                rec.ENAME,
                rec.JOB,
                rec.MGR,
                rec.HIREDATE,
                rec.SAL,
                rec.COMM,
                rec.DEPTNO
              );
END ins; <\/p>\n

PROCEDURE upd
IS
BEGIN
  — update the values in the table with the values in the rec record
  — based on the primary key
  UPDATE EMP
     SET
         EMPNO = rec.EMPNO,
         ENAME = rec.ENAME,
         JOB = rec.JOB,
         MGR = rec.MGR,
         HIREDATE = rec.HIREDATE,
         SAL = rec.SAL,
         COMM = rec.COMM,
         DEPTNO = rec.DEPTNO
   WHERE
         EMPNO = rec.EMPNO
   ;
END upd; <\/p>\n

PROCEDURE del
IS
BEGIN
  — remove a record from the table
  — based on the primary key
  DELETE FROM EMP
   WHERE
         EMPNO = rec.EMPNO
  ;
END del; <\/p>\n

Now I can create a couple of tests in CodeTester<\/a> (click the link to see the pre-execution code to be added in CodeTester<\/a>): <\/p>\n