Reporting
Feature |
utPLSQL |
ruby-plsql |
Build in report types |
3 build-in types: - screen output to client console - file output (needs to write to DB server) - html file output (needs to write to DB server) Outputs incomplete, console output noisy. |
4 build-in types - dotted - very dense, useful for developers - documentation - QA text reporting oriented - HTML - like documentation but in publishable form - JSON - for machine processing |
Extensibility / third party |
Can be extended - do it yourself |
Available open-source libraries for other output formatting (like CI JUnit formatters) |
Build in code coverage generation |
NO |
YES |
Supplies timing for tests |
NO |
YES |
Supplies count of tests executed |
not directly |
YES |
Full stack trace for exceptions |
NO |
YES |
Self-documenting tests / tests expressivness |
NO procedure_name_30_char_limit no place for test description description is placed inside single assertion "somewhere inside test code" |
YES tests and example blocks have a "full text descriptive names" |
Comments
Related