Details

      Description

      The audit log provided in test scenario should be more userfriendly and understandable.
      I doubt a business analyst could understand it.

      Example of the current log :

      OBJECT ASSERTED value:com.sopra.evolan.erules.scenario.scenario1.bean.Client@1f factId: 1
      OBJECT ASSERTED value:com.sopra.evolan.erules.scenario.scenario1.bean.Request@1435263 factId: 2
      FIRING rule: [ELI_COMPTE_CHEQ_1] activationId:ELI_COMPTE_CHEQ_1 [2, 1] declarations: Req1=com.sopra.evolan.erules.scenario.scenario1.bean.Request@1435263(2); Cli1=com.sopra.evolan.erules.scenario.scenario1.bean.Client@1f(1)
      OBJECT ASSERTED value:com.sopra.evolan.erules.scenario.scenario1.bean.Account@1f factId: 3
      etc.

      For instance instead of the complete class name "com.sopra.evolan.erules.scenario.scenario1.bean.Request" why not display the result of a method toString() ?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                michaelneale Michael Neale
                Reporter:
                hestin Hestin Gilles
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: