Menu

#9 The count of "utAssert.xxx()" executed in the outputreporter is required.

Verified
nobody
None
Medium
[none]
2015-02-15
2014-06-16
ahhriver
No

Current behavior:
For the "utoutputreporter.pkb",
1. There is no total count of "utAssert.xxx()" executed in the testing package.
2. The format of section, package-based, done is not clear

eg:
exec utplsql.test ('myPackage');
In the output:
...
'SUCCESS: "myPackage"
...

Desired behavior:
In the output, we'd like to show:
...
- - - - - - - - SUCCESS: "myPackage (15 scenarioes executed)" - - - - - - - -
...

Proposed solution
The value of doing this:
When we add/remove "utAssert.xxx", we know the action have been put into the suite.

Discussion

  • Svyatoslav Chatchenko

    I agree that this valuable enhancement. I did similar changes in feature-requests-1 for testsuite overall output. It looks like this for success:

    SUITE SUCCESS: "TEST SUITE"
    SUITE STATS: 2 of 2 packages succeeded.
    SUITE STATS: 5 of 5 individual test cases succeeded.
    

    And like this for failure:

    SUITE FAILURE: "TEST SUITE"
    SUITE STATS: 1 of 2 packages succeeded.
    SUITE STATS: 4 of 5 individual test cases succeeded.
    

    As for package, I suggest output like this:

     SUCCESS: "Owner.PackageName" Run ID: X (Z from Z succeeded)
     FAILURE: "Owner.PackageName" Run ID: X (Y from Z succeeded)
    

    Where Z is the total number of asserts in the package.

     
  • Paul Walker

    Paul Walker - 2015-02-15
    • status: Open --> Verified
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.