-
Notifications
You must be signed in to change notification settings - Fork 34
master (0.4.0 milestone) --> 0.5.0 milestone #476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
chace86
wants to merge
93
commits into
0.5.0
Choose a base branch
from
master
base: 0.5.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…creasing class coverage of unit test
…eve better coverage
* Added a stacktrace of the initiation to help w/ debugging, as well as a method to fetch it * Added testing for it
* Unit tests for AppFatalException class * Added missing asserting * update unit tests from upstream * Inital testing * better unit tests for classes that user Group and Property constructors
- -none: To eliminate all warnings: JDK8+ - additionalparam: <=Maven 2.9 (removed as mvn 3+ used) - additionalJOption: => Maven 3.0 - doclint: maven-javadoc-plugin 3.0.0+
modifier is added.
modifier is added.
modifier is added.
modifier is added
- get() calls instance() internally - Added (some) javadocs - Edited a couple of missing javadocs
* Bump junit from 4.12 to 4.13.1 Bumps [junit](https://github.com/junit-team/junit4) from 4.12 to 4.13.1. - [Release notes](https://github.com/junit-team/junit4/releases) - [Changelog](https://github.com/junit-team/junit4/blob/main/doc/ReleaseNotes4.12.md) - [Commits](junit-team/junit4@r4.12...r4.13.1) Signed-off-by: dependabot[bot] <support@github.com> * Changed the distro for the build - rumored to fix this issue. Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Eric Everman <eeverman@gmail.com>
Co-authored-by: Eric Everman <eeverman@gmail.com>
Co-authored-by: Eric Everman <eeverman@gmail.com>
Co-authored-by: Eric Everman <eeverman@gmail.com>
Co-authored-by: Eric Everman <eeverman@gmail.com>
Co-authored-by: Eric Everman <eeverman@gmail.com>
Also update the pom to: * specify 1.8 as the source and target * Specify a Java version as 1.8 to 15 * Specify a Maven version 3.5 up to 4.0 Co-authored-by: Eric Everman <eeverman@gmail.com>
Co-authored-by: Eric Everman <eeverman@gmail.com>
…ild in IntelliJ Idea 2020.3+ (#496) Co-authored-by: Vicky Ronnen <vicky.ronnen@upcmail.nl>
…498) Also cleaned up some formatting that had gotten weird. Co-authored-by: Eric Everman <eeverman@gmail.com>
This reverts commit 943f6d2.
Readme updated for compatibility for Java 8 - 15
small text change
* upgrade andhow-core module to use JUnit 5 * rm unneeded inports from several classes (over eager IDE...) * Add pom dependencies to support JUnit 4 & 5 * Updated all of andhow-testing to JUnit 5 except the annotation related stuff. The test harness now has Junit 4 & 5 implementations. * Testing module almost ready - one failing module yet. * Fixed a few tests that were partially converted to J5 and thus failing * Completely rm JUnit 4 except for one base class that is intended for use by app dev's using JUnit 4 * Improved test coverage * Add tests for the getJndi method. Also clarified that jndi is completely cleared after each test and after the test class * Added tests for AndHowJunit4/5TestBase's. Co-authored-by: Eric Everman <eeverman@gmail.com>
update to new travis-ci.com badge location
* Moved the AndHowCompileProcessorTestBase to the test harness module * cleaned up junit related dependency declaration in pom files Co-authored-by: Eric Everman <eeverman@gmail.com>
) * Partial work * Completed code, though not tested * Added some testing * Just a little bit more testing * More testing... * More testing * More testing * Added a base class for testing loaders Tests for FixedValueLoader Added better docs and tests for the LngProp and DblProp * More testing for FixedValueLoader * Lots more tests around fixed values * Also moved tests that relate to the StdConfig into a StdConfigXXX named test * Better notes and examples in the multimodule-dataprocess test/example Co-authored-by: Eric Everman <eeverman@gmail.com>
* Testing improvements for StdConfig * Fix build error * Add forgotten test annotation * More tests, improved docs * Improved javadocs Co-authored-by: Eric Everman <eeverman@gmail.com>
* Initial work * Improved test example * Add Junit extension * Large update to JUnit 5 testing utils and examples * Fixed test naming to ensure tests are run * Fixed a few broken tests * cleanup * Move all methods that are supported parts of StdConfig to the AndHowConfiguration interface. A lot of those methods evolved in StdConfig or in BaseConfig and were never brought back to the interface. Now that the interface needs to be functional on its own, the method signitures need to move. * the getDefaultLoaderList() method was static and now is an instance method as part of this move. Its a minor, potentially breaking change, but it seems really unlikely to affect anyone. * turned off deployment of some non-distributable artifacts * Add mockito testing of the JUnit extensions Co-authored-by: Eric Everman <eeverman@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assuming master branch represents 0.4.0 milestone. Assuming 0.5.0 will follow 0.4.0 milestone, should we merge master into 0.5.0? Asking before I resolve merge conflicts.