Skip to content

Conversation

viniciusam
Copy link
Member

No description provided.

antusus and others added 30 commits November 20, 2017 21:02
Can be null, in which case ut/PLSQL need to scan all the sources for the correct annotation
It seems to make the coverage fails, since there no good example of sane default value. Removing until there is a use case for it
Improved readability
 - Parametrized Name, OutputFile, Console * Removed default values for connections and use the same as the Java API * Added fully maven test in order to accomplish maven testing - The only drawback is that we have the parameter connection inside the pom test. * Updated the Readme of project
First approach to increase the functionality of the maven plugin
Retrieve the Framework version with the API utility Upgrade documentation to remove parameter version
jgarec and others added 29 commits July 16, 2018 08:59
* Adds 2 new parameters : sourcesOwner / testsOwner * Adds 1 new project sample (owner-param-project) * Refactor travis build (run tests with ut3 user) * Improve documentation
* IT : Add 1 new integration test project * FEATURE : Sources / tests / paths / reporters are now optional * FIX : Fixes owner-param project * FIX : Fixes wrong base dir for sources and tests scripts
Fixes #21 : all parameters are now optional
* Directory or includes are now optional (when the other one is set) * Add new tests * Fix a bug where files paths where relative to the plugin and not the tested project * Fix previous tests
-B (batchmode) and -l <filename> (output to file) removes coloration -Dstyle.color=never removes coloration Note: style.color seems to require at least maven 3.5.3
Sets the console output on by default if no output option specified.
Code linting, README update and build tasks
@viniciusam viniciusam closed this Oct 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

6 participants